Spend 30 minutes to help get testing.drupal.org running

http://testing.drupal.org - which will automatically run every patch for Drupal 7 through over 7100 (and counting) assertions needs one final push of manual testing before we can get it running at full capacity and reducing the workload of those of us who contribute regularly to Drupal core.

Over the past few weeks, Jimmy Berry (boombatower), Chad Phillips (hunmonk) and amazon (Kieran Lal) have been working hard on the final steps required to bring the testing platform up to date and have it ready to handle an increased capacity for patch testing. It's currently applying patches to a clean install of Drupal HEAD, running all tests, and reporting back the results to Drupal.org

The final stage is to get the platform marking patches to 'Code needs work' when they don't apply. There are currently over 400 patches needing review against Drupal 7, and clearing the queue of old stale patches is essential to getting this down to a manageable level.

Before we can do that, we need humans to verify the results of the automated tests to ensure they're accurate. Even if you've never reviewed a core patch before, you can help with this.

Step one: check out Drupal HEAD from cvs - http://drupal.org/node/320 has instructions

Step two: pick a link from http://groups.drupal.org/node/16209 - passing patches are at the top, failing patches are at the bottom. Failing patches are easier to test.

Step three. If you've picked a 'failing' patch, look at the reason why it failed. If it 'Failed to apply' then run these steps.
cd drupal7
wget http://drupal.org/the/link/to/the.patch
patch -p0 < the.patch

If you get a message about 'failed hunks' or the patch otherwise fails to apply,you can then update the groups.drupal.org wiki to confirm this.

For more information on testing and applying patches see http://drupal.org/patch - to test patches which pass, you'll need a working install of Drupal 7, which takes a little longer to set up, but not too much.