The test bot from testing.dupal.org has fundamentally changed the way that core development happens in Drupal 7. By automatically testing every single patch, and ensuring that Drupal continues to install properly and pass all automated tests, we can ensure that Drupal 7 remains the most stable development release to date, and can save our patch reviewers tons of time that would otherwise be spent manually verifying that patches do not break existing functionality.
However, the test bot urgently needs your help!
The test bot relies on donated servers that have been set up with the installation script. These servers are then added to the network and used to run tests on patches.
However, we have issues with various servers periodically "crapping out," for lack of a better description. Sometimes they just need a reboot, or a re-install of Drupal. With a bit of debugging, it seems some issues may be related to filesystem settings and other low level things. But we need help from those who are comfortable with Linux in debugging those issues, as well as tuning the test servers for maximum efficiency (MySQL in memory, PHP caching, etc: the usual).
In addition, we are also trying to deploy the next generation of the testing system and require help debugging issues with new test clients and setting up the clients themselves.
Also, since the second generation testing framework will require more bandwidth in order to test contributed modules, more servers will be needed to handle the load. Any donations of "decent" servers would be great.
So, to summarize:
- If you fancy yourself comfortable with Linux, please help lend your debugging and performance tuning skills.
- If you have a spare server that can run an entire battery of tests in a reasonable period of time, please donate it to the cause.
If you can help, please use the testing.drupal.org contact form or comment here, and we'll get you hooked up.