Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Currently, the qa.d.o snapshot can occur in the middle of testing, causing qa.staging.drupal.org 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.
Comment | File | Size | Author |
---|---|---|---|
#4 | qa.staging.sql_edits.v2.patch | 1.93 KB | jthorson |
#3 | qa.staging.sql_edits.patch | 688 bytes | jthorson |
qa.staging_sanitization.patch | 1.32 KB | jthorson |
Comments
Comment #1
jthorson CreditAttribution: jthorson commentedTagged with d.o D7, since we need a sane staging environment to be able to test the PIFT D7 port.
Comment #2
drummCommitted & pushed.
Comment #3
jthorson CreditAttribution: jthorson commentedA couple more tweaks ... disabling client re-confirmation (which is currently broken as per #1552476: Get qa.staging.devdrupal.org 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.
Comment #4
jthorson CreditAttribution: jthorson commentedSome additional tweaks; simplifying one query, and adding a missed pifr_log update.
Comment #5
sdboyer CreditAttribution: sdboyer commentedCommushed.