Drupal Quality Assurance

A patch at Installer: Configure site text cleanup was committed which broke HEAD for a few hours tonight. The fix has been committed, and testing bot turned back on. If your patch got a "Failed: Failed to install HEAD." status assigned to it on Sunday evening, try marking the issue back to "needs review" so testing bot can have another crack at it.

UPDATE: a patch was committed to Drupal HEAD which resolved this issue. Testing has been enabled again.

The testing bot is currently disabled due to apparent false negatives in some path module tests.

Test slave #16 was recently pulled off the master server list, but it was done so in a way that caused data corruption. I attempted to correct the problem, but I made a mistake and reset 2,132 tests (trigger happy). Please be aware of this if you see oddities in the activity log or test results.

UPDATE: I was able to restore the results through a few interesting mysql queries. :)

Until http://drupal.org/node/445950 is resolved.

edit: now fixed (partial commit)

The bot is currently disabled due to locale test failures. Form more information please see the following issues.

• locale test is failing
• Review locale module's simple tests

Edit by webchick 2009-Feb-24 @ 12:00pm EST: Locale tests fixed, testing bot back on!

The bot needs to retrieve files for review from drupal.org. Since the drupal.org servers are being upgraded to Drupal 6, among other things, the bot will be disabled until the upgrade is complete.

An endless loop in a test is keeping the testing bot off-line. SimpleTest needs to be patched in order to set a timeout, hopefully something like 30 minutes.

Thanks,

boombatower

For the past two days patches have been ignored by testbot due to an issue with the key sent to confirm access to add patches to the queue. In some course of events this key changed and thus the testbot denied patches.

This issue has been fixed and the testbed is now active. All patches that still meet the criteria are resent after 72 hours. Any patches that were denied will be resent via that method.

Thanks,

boombatower

The testbed has been disabled since yesterday and has just been re-enabled.

The Node revisions test fails if admin has a personal timezone offset patch was committed to Drupal 7 core in order to correct the problem created by Move node links into $node->content.

The duplicate testing issue that occurs rarely was remedied by increasing the memory limit on the testing servers and applying a preventative patch, just to be extra sure.

Thank you for your patience,

boombatower

There were reports of false failures (http://drupal.org/node/345866, http://drupal.org/node/346285) of the testing bot.

Details of the failing test are remove $op from hook_block().

The testbed will be offline for a couple of days until we can bring it back online. If you want to help with the testbed we need help with the following:

1) System administrators who can help administer almost a dozen servers that have been loaned for testing.
2) Documentation help to document how the testbed infrastructure works.
3) Donate a server or Virtual Machine so we have more testing slaves available.

Contact me if you are able to help.

Cheers,
Kieran