Give access to testing server logs

Having access to the testing servers log could have saved a lot of time in debugging a MySQL 5.0 specific key size limitation #599086: Testbot futzing (please ignore this issue). This issue was created for the sole purpose of finding out why the test bot would only return "Failed: Failed to install HEAD."

The apache error log would have sufficed here to catch the following :

PDOException: SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 3072 bytes

If I had seen that somewhere in the test bot results it would have me a LOT of time ;)

Let me suggest a work around. Each test server could provide its apache error logs to the developers. These could be flushed hourly or daily to keep them small. It's up to the developer to get the logs from the testing server which failed to install HEAD (the id of the server can be found on the results page). A link to the logs could be added there too maybe. The developer can then dig through the logs and find what happened.

Ideally the server should return the error logs of a particular patch to improve the message displayed on testing.drupal.org. The current message is "Failed: Failed to install HEAD." which does not give any clue as to what caused the failure.