Currently, the qa.d.o snapshot can occur in the middle of testing, causing to think it has active tests on the testbots.

However, staging doesn't actually manage the production testbots, so we need to muck with the database to turn off the tests, disable production testbots, and enable the development testbots.

The attached patch should do the trick.

Members fund testing for the Drupal project. Drupal Association Learn more


jthorson’s picture

Tagged with d.o D7, since we need a sane staging environment to be able to test the PIFT D7 port.

drumm’s picture

Status: Active » Fixed

Committed & pushed.

jthorson’s picture

Status: Fixed » Needs review
688 bytes

A couple more tweaks ... disabling client re-confirmation (which is currently broken as per #1552476: Get online, and gets in the way of testing), and enabling git7site and pift-drupal_7 sites by default so we don't have to every time we want to test.

jthorson’s picture

Some additional tweaks; simplifying one query, and adding a missed pifr_log update.

sdboyer’s picture

Status: Needs review » Fixed


Automatically closed -- issue fixed for 2 weeks with no activity.

Project: infrastructure » Testbots
Component: » Miscellaneous