Features - 7.x-1.0-rc1 | Drupal Quality Assurance

Latest changes

So Long and Thanks for all the Tests

1 week 1 day ago

Support

In case of troubles

check the FAQ. Please make sure you've tried the test locally.
search known testbot issues and then create a new issue if yours isn't there already. Please give a link to the test.

Test client logs

No clients to display.

Features - 7.x-1.0-rc1

Test status

Status	Result
Last received	Wed, 03/21/2012 - 16:53:37
Last requested	Wed, 03/21/2012 - 16:54:03
Last tested	Wed, 03/21/2012 - 16:54:33
Test count	2

Environment status

MySQL	fail
Code review	fail

Overall Result	fail

Branch information

Identifier	7.x-1.0-rc1
Project	Features
Link	Project information

Event logView entire log

ID	Message	Timestamp
3331494	Result retrieved by project client.	3 years 48 weeks ago
3331489	Result retrieved by project client.	3 years 48 weeks ago
3331484	Result received from test client #.	3 years 48 weeks ago
3331479	Result received from test client #654.	3 years 48 weeks ago
3331474	Requested by test client #654.	3 years 48 weeks ago
3331469	Requested by test client #.	3 years 48 weeks ago
3331464	Test request received.	3 years 48 weeks ago

SummaryFAILED: [[Coder]]: [Code review] 31 minor(s), 11 critical(s), and 132 normal(s); [[SimpleTest]]: [MySQL] 0 pass(es), 3 fail(s), and 0 exception(s).

Details

MySQL
Code review

MySQL

Setup environment
Detect an invalid patch URL
Detect invalid repository information
Detect invalid patch format
Detect a non-applicable patch
Detect invalid PHP syntax
Detect a Drupal installation failure
Detect a test run failure
Detect a failing test
Review the test failures below then if necessary run them locally until the problem has been fixed.
Complete test suite with all tests passing

0 pass(es), 3 fail(s), and 0 exception(s)

Non-pass

Test name

Pass

Fail

Exception

Component tests (FeaturesUserTestCase) [Features]

Message	Group	Filename	Line	Function
The test did not complete due to a fatal error.	Completion check	features.test	44	FeaturesUserTestCase->test()
Enabled modules: field, filter, image, taxonomy, views, features, features_test	Other	features.test	32	FeaturesUserTestCase->setUp()
Call to undefined function features_rebuild()	PHP Fatal error	features.test	35	Unknown

All

Test name

Pass

Fail

Exception

Component tests (FeaturesUserTestCase) [Features]

Message	Group	Filename	Line	Function
The test did not complete due to a fatal error.	Completion check	features.test	44	FeaturesUserTestCase->test()
Enabled modules: field, filter, image, taxonomy, views, features, features_test	Other	features.test	32	FeaturesUserTestCase->setUp()
Call to undefined function features_rebuild()	PHP Fatal error	features.test	35	Unknown

Review log

Code review

Setup environment
Detect an invalid patch URL
Detect invalid repository information
Detect invalid patch format
Detect a non-applicable patch
Detect invalid PHP syntax
Detect a review run failure
Detect coder flags
Ensure that your code follows the Drupal standard and passes a coder review.
Complete coder review with all passed

31 minor(s), 11 critical(s), and 132 normal(s)

Non-pass

Test name Minor Critical Normal

features.admin.inc 7 8 18

Message	Group	Filename	Line	Function
@file block missing (Drupal Docs)	Other	features.admin.inc	-1	N/A
Function documentation should be less than 80 characters per line.	Other	features.admin.inc	4	N/A
Potential problem: FAPI elements '#title' and '#description' only accept filtered text, be sure to use check_plain(), filter_xss() or similar to ensure your $variable is fully sanitized.	Other	features.admin.inc	120	N/A
Potential problem: FAPI elements '#title' and '#description' only accept filtered text, be sure to use check_plain(), filter_xss() or similar to ensure your $variable is fully sanitized.	Other	features.admin.inc	131	N/A
Use "elseif" in place of "else if"	Other	features.admin.inc	165	N/A
Potential problem: form_set_error() and form_error() only accept filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)	Other	features.admin.inc	177	N/A
Use "elseif" in place of "else if"	Other	features.admin.inc	199	N/A
in most cases, replace the string function with the drupal_ equivalent string functions	Other	features.admin.inc	253	N/A
missing space after comma	Other	features.admin.inc	262	N/A
Use "elseif" in place of "else if"	Other	features.admin.inc	290	N/A
There should be no trailing spaces	Other	features.admin.inc	335	N/A
There should be no trailing spaces	Other	features.admin.inc	349	N/A
in most cases, replace the string function with the drupal_ equivalent string functions	Other	features.admin.inc	361	N/A
Potential problem: FAPI elements '#title' and '#description' only accept filtered text, be sure to use check_plain(), filter_xss() or similar to ensure your $variable is fully sanitized.	Other	features.admin.inc	367	N/A
Potential problem: FAPI elements '#title' and '#description' only accept filtered text, be sure to use check_plain(), filter_xss() or similar to ensure your $variable is fully sanitized.	Other	features.admin.inc	423	N/A
Potential problem: FAPI elements '#title' and '#description' only accept filtered text, be sure to use check_plain(), filter_xss() or similar to ensure your $variable is fully sanitized.	Other	features.admin.inc	424	N/A
Use "elseif" in place of "else if"	Other	features.admin.inc	432	N/A
The $text argument to l() should be enclosed within t() so that it is translatable.	Other	features.admin.inc	433	N/A
There should be no trailing spaces	Other	features.admin.inc	526	N/A
There should be no trailing spaces	Other	features.admin.inc	552	N/A
Use "elseif" in place of "else if"	Other	features.admin.inc	557	N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)	Other	features.admin.inc	595	N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)	Other	features.admin.inc	611	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.admin.inc	756	N/A
Function documentation should be less than 80 characters per line.	Other	features.admin.inc	762	N/A
If you define a @param or @return, you should document it as well.	Other	features.admin.inc	764	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	features.admin.inc	764	N/A
There should be no trailing spaces	Other	features.admin.inc	781	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.admin.inc	817	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.admin.inc	831	N/A
Separate comments from comment syntax by a space.	Other	features.admin.inc	868	N/A
Control statements should have one space between the control keyword and opening parenthesis	Other	features.admin.inc	870	N/A
Separate comments from comment syntax by a space.	Other	features.admin.inc	874	N/A

features.api.php 1 0 13

Message	Group	Filename	Line	Function
@file block missing (Drupal Docs)	Other	features.api.php	-1	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.api.php	4	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.api.php	64	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.api.php	121	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.api.php	140	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.api.php	174	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.api.php	195	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.api.php	221	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.api.php	238	N/A
Format should be `* Implementation of hook_foo().`	Other	features.api.php	283	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.api.php	300	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.api.php	311	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.api.php	348	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.api.php	358	N/A

features.drush.inc 2 0 14

Message	Group	Filename	Line	Function
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	features.drush.inc	11	N/A
@see references should be separated by "," followed by a single space and with no trailing punctuation	Other	features.drush.inc	11	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	features.drush.inc	152	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	features.drush.inc	169	N/A
use a space between the closing parenthesis and the open bracket	Other	features.drush.inc	204	N/A
Use PHP's master function, not an alias. (List of PHP aliases)	Other	features.drush.inc	239	N/A
Use PHP's master function, not an alias. (List of PHP aliases)	Other	features.drush.inc	303	N/A
Use PHP's master function, not an alias. (List of PHP aliases)	Other	features.drush.inc	329	N/A
Use PHP's master function, not an alias. (List of PHP aliases)	Other	features.drush.inc	353	N/A
Use PHP's master function, not an alias. (List of PHP aliases)	Other	features.drush.inc	355	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.drush.inc	434	N/A
Use "elseif" in place of "else if"	Other	features.drush.inc	455	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.drush.inc	474	N/A
If you define a @param or @return, you should document it as well.	Other	features.drush.inc	501	N/A
Use "elseif" in place of "else if"	Other	features.drush.inc	590	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.drush.inc	605	N/A

features.export.inc 3 1 31

Message	Group	Filename	Line	Function
@file block missing (Drupal Docs)	Other	features.export.inc	-1	N/A
If you define a @param or @return, you should document it as well.	Other	features.export.inc	4	N/A
If you define a @param or @return, you should document it as well.	Other	features.export.inc	5	N/A
If you define a @param or @return, you should document it as well.	Other	features.export.inc	6	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.export.inc	31	N/A
If you define a @param or @return, you should document it as well.	Other	features.export.inc	35	N/A
If you define a @param or @return, you should document it as well.	Other	features.export.inc	37	N/A
If you define a @param or @return, you should document it as well.	Other	features.export.inc	41	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	features.export.inc	41	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.export.inc	95	N/A
If you define a @param or @return, you should document it as well.	Other	features.export.inc	215	N/A
If you define a @param or @return, you should document it as well.	Other	features.export.inc	217	N/A
If you define a @param or @return, you should document it as well.	Other	features.export.inc	219	N/A
If you define a @param or @return, you should document it as well.	Other	features.export.inc	223	N/A
Use "elseif" in place of "else if"	Other	features.export.inc	297	N/A
Function documentation should be less than 80 characters per line.	Other	features.export.inc	368	N/A
Use "elseif" in place of "else if"	Other	features.export.inc	401	N/A
in most cases, replace the string function with the drupal_ equivalent string functions	Other	features.export.inc	430	N/A
in most cases, replace the string function with the drupal_ equivalent string functions	Other	features.export.inc	437	N/A
in most cases, replace the string function with the drupal_ equivalent string functions	Other	features.export.inc	443	N/A
Use "elseif" in place of "else if"	Other	features.export.inc	464	N/A
Use "elseif" in place of "else if"	Other	features.export.inc	477	N/A
Use "elseif" in place of "else if"	Other	features.export.inc	480	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.export.inc	503	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.export.inc	535	N/A
Using eval() or drupal_eval() in your module's code could have a security risk if the PHP input provided to the function contains malicious code. (Drupal Docs)	Other	features.export.inc	617	N/A
Use "elseif" in place of "else if"	Other	features.export.inc	781	N/A
Use "elseif" in place of "else if"	Other	features.export.inc	798	N/A
Use "elseif" in place of "else if"	Other	features.export.inc	802	N/A
Function documentation should be less than 80 characters per line.	Other	features.export.inc	869	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.export.inc	869	N/A
Function documentation should be less than 80 characters per line.	Other	features.export.inc	870	N/A
Function documentation should be less than 80 characters per line.	Other	features.export.inc	873	N/A
If you define a @param or @return, you should document it as well.	Other	features.export.inc	877	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	features.export.inc	877	N/A

features.install 0 0 1

Message	Group	Filename	Line	Function	Status
Function summaries should be one line only. (Drupal Docs)	Other	features.install	52	N/A

features.module 2 1 21

Message	Group	Filename	Line	Function
Function summaries should be one line only. (Drupal Docs)	Other	features.module	31	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.module	38	N/A
Function documentation should be less than 80 characters per line.	Other	features.module	39	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.module	46	N/A
Function documentation should be less than 80 characters per line.	Other	features.module	53	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.module	53	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.module	59	N/A
Use uppercase for PHP constants, e.g. NULL, TRUE, FALSE	Other	features.module	188	N/A
Use uppercase for PHP constants, e.g. NULL, TRUE, FALSE	Other	features.module	192	N/A
Use uppercase for PHP constants, e.g. NULL, TRUE, FALSE	Other	features.module	201	N/A
Format should be `* Implementation of hook_foo().`	Other	features.module	240	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.module	300	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.module	330	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	features.module	403	N/A
If you define a @param or @return, you should document it as well.	Other	features.module	410	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	features.module	410	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.module	481	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.module	521	N/A
Control statements should have one space between the control keyword and opening parenthesis	Other	features.module	555	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.module	656	N/A
Use "elseif" in place of "else if"	Other	features.module	671	N/A
Use "elseif" in place of "else if"	Other	features.module	722	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.module	738	N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure to use check_plain(), filter_xss() or similar to ensure your $variable is fully sanitized.	Other	features.module	883	N/A

includes/features.block.inc 1 0 1

Message	Group	Filename	Line	Function	Status
@file block missing (Drupal Docs)	Other	features.block.inc	-1	N/A
in most cases, replace the string function with the drupal_ equivalent string functions	Other	features.block.inc	24	N/A

includes/features.context.inc 0 0 2

Message	Group	Filename	Line	Function	Status
@file block missing (Drupal Docs)	Other	features.context.inc	-1	N/A
If you define a @param or @return, you should document it as well.	Other	features.context.inc	47	N/A

includes/features.ctools.inc 12 1 8

Message	Group	Filename	Line	Function
@file block missing (Drupal Docs)	Other	features.ctools.inc	-1	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.ctools.inc	5	N/A
Function documentation should be less than 80 characters per line.	Other	features.ctools.inc	6	N/A
Use an indent of 2 spaces, with no tabs	Other	features.ctools.inc	9	N/A
Using eval() or drupal_eval() in your module's code could have a security risk if the PHP input provided to the function contains malicious code. (Drupal Docs)	Other	features.ctools.inc	26	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.ctools.inc	48	N/A
Format should be `* Implementation of hook_foo().`	Other	features.ctools.inc	86	N/A
'Implementation' should be at the start of the sentence and begin with a capitialized letter	Other	features.ctools.inc	86	N/A
Function documentation should be less than 80 characters per line.	Other	features.ctools.inc	88	N/A
Format should be `* Implementation of hook_foo().`	Other	features.ctools.inc	102	N/A
'Implementation' should be at the start of the sentence and begin with a capitialized letter	Other	features.ctools.inc	102	N/A
Function documentation should be less than 80 characters per line.	Other	features.ctools.inc	102	N/A
Format should be `* Implementation of hook_foo().`	Other	features.ctools.inc	122	N/A
'Implementation' should be at the start of the sentence and begin with a capitialized letter	Other	features.ctools.inc	122	N/A
Format should be `* Implementation of hook_foo().`	Other	features.ctools.inc	154	N/A
'Implementation' should be at the start of the sentence and begin with a capitialized letter	Other	features.ctools.inc	154	N/A
Function documentation should be less than 80 characters per line.	Other	features.ctools.inc	154	N/A
Format should be `* Implementation of hook_foo().`	Other	features.ctools.inc	184	N/A
'Implementation' should be at the start of the sentence and begin with a capitialized letter	Other	features.ctools.inc	184	N/A
There should be no trailing spaces	Other	features.ctools.inc	239	N/A
Use "elseif" in place of "else if"	Other	features.ctools.inc	240	N/A

includes/features.features.inc 0 0 2

Message	Group	Filename	Line	Function	Status
@file block missing (Drupal Docs)	Other	features.features.inc	-1	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.features.inc	54	N/A

includes/features.field.inc 1 0 3

Message	Group	Filename	Line	Function
@file block missing (Drupal Docs)	Other	features.field.inc	-1	N/A
Format should be `* Implementation of hook_foo().`	Other	features.field.inc	155	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.field.inc	155	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.field.inc	187	N/A

includes/features.filter.inc 0 0 1

Message	Group	Filename	Line	Function	Status
@file block missing (Drupal Docs)	Other	features.filter.inc	-1	N/A

includes/features.image.inc 0 0 2

Message	Group	Filename	Line	Function	Status
@file block missing (Drupal Docs)	Other	features.image.inc	-1	N/A
Use "elseif" in place of "else if"	Other	features.image.inc	94	N/A

includes/features.menu.inc 0 0 3

Message	Group	Filename	Line	Function
@file block missing (Drupal Docs)	Other	features.menu.inc	-1	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.menu.inc	31	N/A
global variables should start with a single underscore followed by the module and another underscore	Other	features.menu.inc	134	N/A

includes/features.node.inc 0 0 2

Message	Group	Filename	Line	Function	Status
@file block missing (Drupal Docs)	Other	features.node.inc	-1	N/A
If you define a @param or @return, you should document it as well.	Other	features.node.inc	97	N/A

includes/features.taxonomy.inc 0 0 1

Message	Group	Filename	Line	Function	Status
@file block missing (Drupal Docs)	Other	features.taxonomy.inc	-1	N/A

includes/features.user.inc 2 0 3

Message	Group	Filename	Line	Function
@file block missing (Drupal Docs)	Other	features.user.inc	-1	N/A
There should be no trailing spaces	Other	features.user.inc	67	N/A
There should be no trailing spaces	Other	features.user.inc	72	N/A
Function summaries should be one line only. (Drupal Docs)	Other	features.user.inc	110	N/A
Control statements should have one space between the control keyword and opening parenthesis	Other	features.user.inc	157	N/A

tests/features.test 0 0 1

Message	Group	Filename	Line	Function	Status
@file block missing (Drupal Docs)	Other	features.test	-1	N/A

tests/features_test.features.filter.inc 0 0 1

Message	Group	Filename	Line	Function	Status
Use the matching Drupal theme functions, not raw HTML.	Other	features_test.features.filter.inc	30	N/A

tests/features_test.module 0 0 1

Message	Group	Filename	Line	Function	Status
@file block missing (Drupal Docs)	Other	features_test.module	-1	N/A

theme/features-admin-components.tpl.php 0 0 1

Message	Group	Filename	Line	Function	Status
@file block missing (Drupal Docs)	Other	features-admin-components.tpl.php	-1	N/A

theme/theme.inc 0 0 2

Message	Group	Filename	Line	Function	Status
@file block missing (Drupal Docs)	Other	theme.inc	-1	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	theme.inc	166	N/A

All