Drupal Quality Assurance

There are currently a few issues that have been identified in Drupal core as causing problems with testing, but not yet committed. As such the testing bot has been automatically disabled until the following issues are resolved:

• Testing is broken
• Some file/image tests are failing

Please help test and review the above issues.

Seems there are some issues with the recent changes to the environment configuration, that are causing patches to not queue properly. As such the bot has been disabled for the time being.

Related issue: http://drupal.org/node/703120

In addition it seems there is a test failure in Drupal core.

UPDATE: Flushed the bad data and waiting on core test failures to be fixed. Please see #32 if you are interested in the failing tests. (by boombatower @ 02/08/10 2:00 pm CST)

UPDATE: Drupal HEAD passes, clients #32 and #33 are up and running and with help seems we've squashed the bug responsible for this (rather fun edge-case). (by boombatower @ 02/09/10 3:00 pm CST)

There are currently a few issues that have been resolved, but not yet deployed. As such you may run into a few WSOD on specific pages and notice that results are not reported back to drupal.org. We are sorry for the inconvenience.

The fixes will be deployed tomorrow morning.

UPDATE: Deployed pifr/pift 2.2 to remedy the problem. (by boombatower @ 01/28/10 2:00 pm CST)

Currently the clients are down, awaiting code update.

PIFR issues:

• Update module page path for core patch
• Update install profile from 'default' to 'standard'

and corresponding core issues:

• The Modules page needs to be easier to find
• Write clear install profile descriptions

We have been getting results on multiple instances of a consistent single failure (and 7 exceptions) in Drupal HEAD's FileFieldValidateTestCase. Until it can be resolved, automated testing has been disabled. Please help us investigate why, how, and in what conditions this test is failing.

Update: Thanks to Damien (DamZ) the issues should now be resolved and testing has been re-enabled.

[Update]: It is now working again.

We just shut down patch testing temporarily. We were adding the capability to start testing contributed modules and this introduced a bug.

We realize that some patches were set to "needs work". We apologize for this. If you would like to help, we need help with the following:

1. More developers to help review and maintain the Project Issue File Test modules.
2. Developers with system administration skills who can help test our testing servers and clients.

If you are able to help, please contact us.

The two major testing clients #32 and #33 failed their regular confirmation tests of Drupal 7 core, so testing of all patches is disabled. Though both reported failures, they have conflicting results. Testing will be back online as soon as the issue is tracked down and the testing clients have re-validated.

UPDATE: Everything seems happy again. (by boombatower @ 12/16/09 18:30 GMT)
UPDATE: Both clients failed again. (by deekayen @ 12/18/09 08:52:00 EST)

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.