Drupal QA

The testbot is now running pifr 2.x! The system has many new features and has been completely redesigned with the future of Drupal quality assurance in mind. More information on the new features and the roadmap for qa.drupal.org to come.

Please bear with us as we get the new system functioning on drupal.org and qa.drupal.org.

http://drupal.org/node/472820 is causing one test to fail in HEAD.

I switched of the testing bot - tests were coming back with either 21 or 30 exceptions. tracker was committed without tracker.install - but looks like that was added back, and still some failures.

Update:
http://drupal.org/node/444344#comment-1989712 fixes it.

If you got a single failure on your patch from client #39 (today only, in the past 5 hours), re-test your patch. That bot was likely returning that failure in error and has been disabled until it can be debugged.

There are an awful lot of log entries in the queue right now that say:

Result received from slave #29 (Failed: 11418 passes, 3 fails, 0 exceptions).

The failures are in "Enable/disable modules" - for example, http://testing.drupal.org/pifr/file/1/10943

The last patch committed was the CCK in core patch, though it showed a clean bill of health from testing bot. I don't have time atm to look, so I've shut off testing in the meantime.

Help? :)

The time limit code in bootstrap.inc for simpletest appears to have been the culprit. See http://drupal.org/node/554106#comment-1945966.

Dries committed a patch to Drupal that might require some patching of PIFR. boombatower is studying the impact. In meantime, none of the patches in queue for testing against Drupal HEAD are being tested. The current backlog is 251 patches.

Edit (DamZ): apparently it was not the case. Testing is now enabled again.

The bot is currently down until all test clients have been updated for Rename admin/site-building to admin/structure which required a patch to pifr.

EDIT: Disabled #32 since I do not have ssh access to it and updated #29.

EDIT: Looks like someone update #32.

Due to a bug in PHP 5.2.9, which testing slaves #22 was running, Drupal core test suite reports failures. If your issue was marked with failures related to the "Site-wide contact form" then please mark it for re-testing.

Created page to keep track of these issues at: http://testing.drupal.org/incompatible-software-version.

Just as a heads-up, we are currently trying to test a more manageable way to roll out new testing slaves via a virtual machine instance and inside Amazon EC2 instances. However, we are still having problems debugging, and as a result, the test bot is intermittently reporting failures to the issue queue (esp. be leery of "Failed to install HEAD.")

If your patch is mistakenly marked code needs work, we apologize. Please mark it back to "needs review" and request a re-test from the link in the test status. We hope to have these problems ironed out shortly.

If you have Linux experience, we would love you to to drop by #drupal-infrastructure to help us get things running smoothly again. :)

Here are two set's of instructions for setting up the client's on Debian :
http://testing.drupal.org/node/44, without using the set-up script
http://testing.drupal.org/node/45 Debian Lenny

Here's instructions for getting Centos set-up:
http://testing.drupal.org/PIFR2-Centos-installation-instructions

How to get Postgress client set-up on Debian:
http://groups.drupal.org/node/23617#comment-81971

Once your client is installed, we need to get you an account on the version 2 master server.