Problem/Motivation

Vanished is the 7.x test results from the Drupal project
https://www.drupal.org/node/3060/qa

Recent commits resulted in noticing total vanishing.

Steps to reproduce

Committed changes a few days ago to 7.x (Dries added a provisional maintainer @poker10)

Proposed resolution

TBD

Remaining tasks

TBD

User interface changes

TBD

API changes

TBD

Data model changes

TBD

Comments

joseph.olstad created an issue. See original summary.

mcdruid’s picture

D7 tests were working okay on 2nd September - example: https://www.drupal.org/pift-ci-job/2466746

...but by 3rd September they were failing: https://www.drupal.org/pift-ci-job/2467463

AFAICS the main difference in the build files are:

     assemble_codebase:
-      checkout_core_d7:
+      checkout_core:
-      gather_dependencies_d7:
+      composer.core_install:
+        options: 'install --prefer-dist --no-suggest --no-interaction --no-progress'
+        halt-on-fail: true
+      gather_dependencies:
-      run_tests_d7:
-        testgroups: '--all'
+      run_tests.standard:
         types: 'Simpletest,PHPUnit-Unit,PHPUnit-Kernel,PHPUnit-Functional'
+        testgroups: '--all'

...and a couple of other things relating to composer.

So it looks like a lot of the D7-specific versions of the steps have gone... I'm not sure whether that's because of the absence of the D7 configs for core as @joseph.olstad pointed out in the IS?

I'll attach a successful and failing build file in case they're any use.

joseph.olstad’s picture

@mcdruid nice sleuthing, those build differences appear to be linked to the loss of the automated testing.

joseph.olstad’s picture

@mcdruid do you have an idea where those build files come from?

Ok I see that's a diff between the yml files from the failure vs the last success, the maintainer of the testing system should be able to unwind this mistake.

mcdruid’s picture

I'm not certain how all the pieces fit together but AFAICS the integration between d.o and the dispatcher is this: https://www.drupal.org/project/project_issue_file_test and it's there that the "legacy" build options are set up for D7 tests.

No recent code changes in that project, so I suspect the thing that's broken testing is a config change relating to the 7.x branch which is why we're not seeing the usual options for it at https://www.drupal.org/node/3060/qa

I may be completely wrong about all of that!

Either way it doesn't look to me like the problem is fixable by anyone without more access and a much better understanding of the drupalci system than I have!

joseph.olstad’s picture

Status: Active » Fixed

not sure who fixed this (probably the same person that broke it) but I just noticed it's fixed.

mcdruid’s picture

Yup @mixologic, @hestenet and @drumm all worked on getting this fixed. Thanks!

The problem was something to do with a housekeeping edit to the 7.x-dev release node having broken some of the special logic applied to D7 tests.

Status: Fixed » Closed (fixed)

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