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

CommentFileSizeAuthor
#3 Drupal_core_Drupal.org_-_2015-11-18_13.30.28.png66.81 KBDavid_Rothstein

Comments

Mixologic created an issue. See original summary.

yesct’s picture

yesct commented
Issue summary: View changes

(just putting in the summary template)

David_Rothstein’s picture

David_Rothstein commented
StatusFileSize
new Drupal_core_Drupal.org_-_2015-11-18_13.30.28.png66.81 KB

I just enabled it now at https://www.drupal.org/node/3060/qa so I guess we'll see how it goes:

Drupal 7 core testing enabled

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.)

joelpittet’s picture

joelpittet
he/him
Primary language English
Location Vancouver
commented

Noticed 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.x

Just a passing thought

catch’s picture

catch
he/him
Primary language English
commented

5.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.

drumm’s picture

drumm
he/him
Location NY, US
commented
Status: Active » Fixed

Looks like this is good. I'll be disabling legacy testing for core on Monday if someone doesn't beat me to it.

Status: Fixed » Closed (fixed)

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