I'm seeing a test failure in a documentation-only patch from this issue:
#1003958: Correct _node_save_revision documentation to not refer to passing $node by reference, since it does not
This patch:
http://drupal.org/files/issues/1003958-6-remove-reference-reference-in-_...
This test result (at least at the moment):
http://qa.drupal.org/pifr/test/117724
I think test failures get erased when the test is re-run, so here's the failure information (as usual, not well formatted):
Non-pass
Test name Pass Fail Exception
Upload upgrade path (UploadUpgradePathTestCase) [Upgrade path] 14 2 1
Message Group Filename Line Function Status
No pending updates at the end of the update process. Other upgrade.test 273 UpgradePathTestCase->performUpgrade()
The upgrade was completed successfully. Other upgrade.upload.test 33 UploadUpgradePathTestCase->testUploadUpgrade()
PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'drupaltestbotmysql.simpletest651792field_config' doesn't exist: SELECT fc.* FROM {field_config} fc WHERE (fc.active = :db_condition_placeholder_0) AND (fc.storage_active = :db_condition_placeholder_1) ; Array ( [:db_condition_placeholder_0] => 1 [:db_condition_placeholder_1] => 1 ) in field_read_fields() (line 545 of /var/lib/drupaltestbot/sites/default/files/checkout/modules/field/field.crud.inc). Uncaught exception database.inc 2039 PDOStatement->execute()
| Comment | File | Size | Author |
|---|---|---|---|
| #28 | 1010136-28.patch | 3.16 KB | Stevel |
Comments
Comment #1
jhodgdonBy the way I put this in simpletest.module component because rfay thought it was a test bot failure (base table not found).
Comment #2
rfaysubscribe
Comment #3
Stevel commentedrfay, do you have access to the error.log in the simpletest of the simpletest run? I have some similar errors showing up locally (both {field_config} and {blocked_ips} show up frequently as non-existant). In my error.log I see the following message:
[02-Jan-2011 10:37:20] PHP Fatal error: Maximum function nesting level of '100' reached, aborting! in /home/stevel/drupal/d7/includes/database/database.inc on line 309
My stack trace shows a ping-pong game between drupalGet and checkForMetaRefresh in DWTC.
The attached patch converts drupalGet / checkForMetaRefresh from a recursive to an iterative method.
Comment #4
Stevel commentedchange title to better reflect the bug. I think this happens when a batch operation takes "too much" time, or at least "too many" meta refreshes are followed before the batch operation is finished.
Comment #5
jhodgdonwebchick commented on another issue:
Things that inexplicably break testbot are "major".
Comment #6
catchThis only occurs if you have xdebug enabled, and an issue to warn about that setting was marked won't fix before, so I disagree it's a bug report, it's more an environment issue that it'd be good to protect against, moving to task.
Comment #7
quicksketchWith our new policy at http://drupal.org/node/1201874, even major "tasks" are now preventing new features to Drupal core. This issue doesn't inherently break testbot, it's environmentally based.
Comment #8
Anonymous (not verified) commented#3: 1010136-iterative-drupalget.patch queued for re-testing.
Comment #10
star-szrTagging for reroll.
Comment #11
shameemkm commentedRerolled Patch attached
Comment #12
realityloop commented#11: 1010136-iterative-drupalget-reroll.patch queued for re-testing.
Comment #13
tim.plunkett#11: 1010136-iterative-drupalget-reroll.patch queued for re-testing.
Comment #15
Stevel commentedAnother reroll of this patch...
Comment #16
Stevel commentedPatch updated with new verbose structure, to match the current verbose-output in drupalGet.
Comment #17
star-szrThanks @Stevel, updating tags.
Comment #18
ceardach commentedRemoved "Needs reroll" because for some reason the tag wasn't actually removed as #17 had tried to do.
Comment #19
jhedstromComment #20
rpayanmComment #22
rpayanmComment #24
rpayanmComment #26
Stevel commentedRerolled the patch again.
Comment #27
Stevel commentedRemoved the references to the deprecated String:: functions.
Comment #28
Stevel commentedAnd now for good...
Comment #47
smustgrave commentedThank you for creating this issue to improve Drupal.
We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.
Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.
Thanks!
Comment #48
smustgrave commentedWanted to bump 1 more time, since simpletest is going is this still an issue?