Posted by pillarsdotnet on March 15, 2011 at 5:17pm
I noticed that issues with queued patches were not being updated with test results, so naturally, I visited qa.drupal.org to see what was the problem.
Not only is the statistics page (still) returning a 500 server error, but the most recent "News" item is over a year old.
I tried the Login or register to post comments links, but still no joy. My username and password are already in use, but do not correspond to a valid account. So either I've been banned (why?) or the login process is also broken.
Further investigation reveals that queued tests are repeatedly failing to checkout the drupal repository.
How about it, people? How hard would it be to update the status page when there is obvious brokenness?
Comments
Good points
Good points - I made the status page be the front page and updated the "mission" with current information. Looking forward to your involvement! Thanks for the good ideas.
Still can't log in
Excellent work on the homepage change, by the way.
And the login page now gives a slightly more helpful message. It says that my username "has not been activated or is blocked"
So is there somewhere special I should go to apply for an account on qa.drupal.org, or to review the status of my (presumably submitted) application?
Side issue: I hate the groups.drupal.org captcha form. If drupal.org can live without it, why can't groups.drupal.org?
You really only need a login
You really only need a login if you're going to manage a testbot. If you have a testbot to manage or any other reason to have an account (like retesting branches or such) I'll be happy to approve your account. I just don't know of any other reasons to log in.