Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
DrupalCI has been available for testing of D7 for a while now. We are going to be disabling the old QA Pift/Pifr bots soon.
Proposed resolution
Testing needs to be enabled for core so that we can verify it's doing what we need it to.
Remaining tasks
User interface changes
API changes
Data model changes
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | Drupal_core_Drupal.org_-_2015-11-18_13.30.28.png | 66.81 KB | David_Rothstein |
Comments
Comment #2
yesct commented(just putting in the summary template)
Comment #3
David_Rothstein commentedI just enabled it now at https://www.drupal.org/node/3060/qa so I guess we'll see how it goes:
By the way, why are the options at the bottom not available for Drupal 7? (It's not a blocker for turning the old testbots off since they weren't available in the old system either, but I am just wondering - I would probably want to set most if not all of those to "Branch on commit" for Drupal 7.)
Comment #4
joelpittetNoticed in the screenshot 8.1 is before 8.0. That would actually be nice to do that ordering all the time. Like
-> 8.1.x, 8.0.x, 7.x, 6.xJust a passing thought
Comment #5
catch5.3 is all pass.
5.4 has test failures, that is likely the first full Drupal 7 test run on 5.4. #2620104: PHP 5.4 test failures opened.
5.5/5.6 there are DrupalCI errors, didn't try to look at that yet.
None of this should block switching.
Comment #6
drummLooks like this is good. I'll be disabling legacy testing for core on Monday if someone doesn't beat me to it.