Corresponding node references - 7.x-4.1

Test status
StatusResult
Last receivedWed, 01/04/2012 - 23:52:38
Last requestedWed, 01/04/2012 - 23:53:03
Last testedWed, 01/04/2012 - 23:53:27
Test count2
Environment status
MySQLpass
Code reviewfail
Overall Resultpass
Branch information
Identifier7.x-4.1
ProjectCorresponding node references
LinkProject information
SummaryPASSED: [[Coder]]: [Code review] 0 minor(s), 1 critical(s), and 72 normal(s); [[SimpleTest]]: [MySQL] 0 pass(es).
Details

MySQL

  1. Setup environment
  2. Detect an invalid patch URL
  3. Detect invalid repository information
  4. Detect invalid patch format
  5. Detect a non-applicable patch
  6. Detect invalid PHP syntax
  7. Detect a Drupal installation failure
  8. Detect a test run failure
  9. Detect a failing test
  10. Complete test suite with all tests passing

Code review

  1. Setup environment
  2. Detect an invalid patch URL
  3. Detect invalid repository information
  4. Detect invalid patch format
  5. Detect a non-applicable patch
  6. Detect invalid PHP syntax
  7. Detect a review run failure
  8. Detect coder flags
    Ensure that your code follows the Drupal standard and passes a coder review.
  9. Complete coder review with all passed
0 minor(s), 1 critical(s), and 72 normal(s)

Non-pass

Test nameMinorCriticalNormal
Expandcorresponding_node_references.crud.inc0053
MessageGroupFilenameLineFunctionStatus
Function documentation should be less than 80 characters per line.Othercorresponding_node_references.crud.inc4N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc10N/A
Function documentation should be less than 80 characters per line.Othercorresponding_node_references.crud.inc10N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc10N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc11N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc11N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc12N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc12N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc13N/A
Function documentation should be less than 80 characters per line.Othercorresponding_node_references.crud.inc13N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc13N/A
Separate comments from comment syntax by a space.Othercorresponding_node_references.crud.inc24N/A
Separate comments from comment syntax by a space.Othercorresponding_node_references.crud.inc25N/A
Separate comments from comment syntax by a space.Othercorresponding_node_references.crud.inc35N/A
Use Drupal's format_date(), not PHP's default date().Othercorresponding_node_references.crud.inc49N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc63N/A
Function documentation should be less than 80 characters per line.Othercorresponding_node_references.crud.inc63N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc63N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc64N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc64N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc65N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc65N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc66N/A
Function documentation should be less than 80 characters per line.Othercorresponding_node_references.crud.inc66N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc66N/A
Function documentation should be less than 80 characters per line.Othercorresponding_node_references.crud.inc67N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc67N/A
Function documentation should be less than 80 characters per line.Othercorresponding_node_references.crud.inc68N/A
Use Drupal's format_date(), not PHP's default date().Othercorresponding_node_references.crud.inc71N/A
Separate comments from comment syntax by a space.Othercorresponding_node_references.crud.inc72N/A
Separate comments from comment syntax by a space.Othercorresponding_node_references.crud.inc114N/A
Use Drupal's format_date(), not PHP's default date().Othercorresponding_node_references.crud.inc122N/A
Separate comments from comment syntax by a space.Othercorresponding_node_references.crud.inc141N/A
Separate comments from comment syntax by a space.Othercorresponding_node_references.crud.inc154N/A
Separate comments from comment syntax by a space.Othercorresponding_node_references.crud.inc155N/A
Separate comments from comment syntax by a space.Othercorresponding_node_references.crud.inc168N/A
Separate comments from comment syntax by a space.Othercorresponding_node_references.crud.inc180N/A
Use Drupal's format_date(), not PHP's default date().Othercorresponding_node_references.crud.inc184N/A
Use the matching Drupal theme functions, not raw HTML.Othercorresponding_node_references.crud.inc191N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc215N/A
Function documentation should be less than 80 characters per line.Othercorresponding_node_references.crud.inc215N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc215N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc216N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc216N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc217N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc217N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc218N/A
Function documentation should be less than 80 characters per line.Othercorresponding_node_references.crud.inc218N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc218N/A
Use Drupal's format_date(), not PHP's default date().Othercorresponding_node_references.crud.inc233N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc247N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc247N/A
Use Drupal's format_date(), not PHP's default date().Othercorresponding_node_references.crud.inc249N/A
Expandcorresponding_node_references.module0119
MessageGroupFilenameLineFunctionStatus
Function documentation should be less than 80 characters per line.Othercorresponding_node_references.module4N/A
Administrative menu items should have a description.Othercorresponding_node_references.module12N/A
Administrative menu items should have a description.Othercorresponding_node_references.module20N/A
Administrative menu items should have a description.Othercorresponding_node_references.module28N/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.Othercorresponding_node_references.module102N/A
Separate comments from comment syntax by a space.Othercorresponding_node_references.module107N/A
Separate comments from comment syntax by a space.Othercorresponding_node_references.module108N/A
Use Drupal's format_date(), not PHP's default date().Othercorresponding_node_references.module127N/A
Use Drupal's format_date(), not PHP's default date().Othercorresponding_node_references.module165N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.module180N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.module180N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.module181N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.module181N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.module182N/A
Function documentation should be less than 80 characters per line.Othercorresponding_node_references.module182N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.module182N/A
Function summaries should be one line only. (Drupal Docs)Othercorresponding_node_references.module210N/A
Function summaries should be one line only. (Drupal Docs)Othercorresponding_node_references.module266N/A
Use Drupal's format_date(), not PHP's default date().Othercorresponding_node_references.module269N/A
Function summaries should be one line only. (Drupal Docs)Othercorresponding_node_references.module277N/A

All

Test nameMinorCriticalNormal
Expandcorresponding_node_references.crud.inc0053
MessageGroupFilenameLineFunctionStatus
Function documentation should be less than 80 characters per line.Othercorresponding_node_references.crud.inc4N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc10N/A
Function documentation should be less than 80 characters per line.Othercorresponding_node_references.crud.inc10N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc10N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc11N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc11N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc12N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc12N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc13N/A
Function documentation should be less than 80 characters per line.Othercorresponding_node_references.crud.inc13N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc13N/A
Separate comments from comment syntax by a space.Othercorresponding_node_references.crud.inc24N/A
Separate comments from comment syntax by a space.Othercorresponding_node_references.crud.inc25N/A
Separate comments from comment syntax by a space.Othercorresponding_node_references.crud.inc35N/A
Use Drupal's format_date(), not PHP's default date().Othercorresponding_node_references.crud.inc49N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc63N/A
Function documentation should be less than 80 characters per line.Othercorresponding_node_references.crud.inc63N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc63N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc64N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc64N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc65N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc65N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc66N/A
Function documentation should be less than 80 characters per line.Othercorresponding_node_references.crud.inc66N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc66N/A
Function documentation should be less than 80 characters per line.Othercorresponding_node_references.crud.inc67N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc67N/A
Function documentation should be less than 80 characters per line.Othercorresponding_node_references.crud.inc68N/A
Use Drupal's format_date(), not PHP's default date().Othercorresponding_node_references.crud.inc71N/A
Separate comments from comment syntax by a space.Othercorresponding_node_references.crud.inc72N/A
Separate comments from comment syntax by a space.Othercorresponding_node_references.crud.inc114N/A
Use Drupal's format_date(), not PHP's default date().Othercorresponding_node_references.crud.inc122N/A
Separate comments from comment syntax by a space.Othercorresponding_node_references.crud.inc141N/A
Separate comments from comment syntax by a space.Othercorresponding_node_references.crud.inc154N/A
Separate comments from comment syntax by a space.Othercorresponding_node_references.crud.inc155N/A
Separate comments from comment syntax by a space.Othercorresponding_node_references.crud.inc168N/A
Separate comments from comment syntax by a space.Othercorresponding_node_references.crud.inc180N/A
Use Drupal's format_date(), not PHP's default date().Othercorresponding_node_references.crud.inc184N/A
Use the matching Drupal theme functions, not raw HTML.Othercorresponding_node_references.crud.inc191N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc215N/A
Function documentation should be less than 80 characters per line.Othercorresponding_node_references.crud.inc215N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc215N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc216N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc216N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc217N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc217N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc218N/A
Function documentation should be less than 80 characters per line.Othercorresponding_node_references.crud.inc218N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc218N/A
Use Drupal's format_date(), not PHP's default date().Othercorresponding_node_references.crud.inc233N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.crud.inc247N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.crud.inc247N/A
Use Drupal's format_date(), not PHP's default date().Othercorresponding_node_references.crud.inc249N/A
Leafcorresponding_node_references.install000
Expandcorresponding_node_references.module0119
MessageGroupFilenameLineFunctionStatus
Function documentation should be less than 80 characters per line.Othercorresponding_node_references.module4N/A
Administrative menu items should have a description.Othercorresponding_node_references.module12N/A
Administrative menu items should have a description.Othercorresponding_node_references.module20N/A
Administrative menu items should have a description.Othercorresponding_node_references.module28N/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.Othercorresponding_node_references.module102N/A
Separate comments from comment syntax by a space.Othercorresponding_node_references.module107N/A
Separate comments from comment syntax by a space.Othercorresponding_node_references.module108N/A
Use Drupal's format_date(), not PHP's default date().Othercorresponding_node_references.module127N/A
Use Drupal's format_date(), not PHP's default date().Othercorresponding_node_references.module165N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.module180N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.module180N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.module181N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.module181N/A
If you define a @param or @return, you should document it as well.Othercorresponding_node_references.module182N/A
Function documentation should be less than 80 characters per line.Othercorresponding_node_references.module182N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othercorresponding_node_references.module182N/A
Function summaries should be one line only. (Drupal Docs)Othercorresponding_node_references.module210N/A
Function summaries should be one line only. (Drupal Docs)Othercorresponding_node_references.module266N/A
Use Drupal's format_date(), not PHP's default date().Othercorresponding_node_references.module269N/A
Function summaries should be one line only. (Drupal Docs)Othercorresponding_node_references.module277N/A