Test runner no longer running patches.

Comments

joseph.olstad created an issue. See original summary.

joseph.olstad’s picture

joseph.olstad’s picture

I think the problem started here:
#2968630-2: Send phpversion to the composer command

joseph.olstad’s picture

different patch, different issue, same error
#2759197-64: [D7] Improve WebTestCase performance by 50%

rooby’s picture

joseph.olstad’s picture

hestenet’s picture

Thanks for the heads up - we're taking a look at this on the DA side (mixologic is out this week).

joseph.olstad’s picture

this is blocking more and more issues, here's a few more, there's others too.

joseph.olstad’s picture

Title: Composer command failed » D7 test runner not working since may 4th 2018 'Composer command failed'
joseph.olstad’s picture

Why are we using composer for D7 ? I don't use composer for any of my D7 projects.

  • c249ad7 committed on 2970950-skip-phpversion-for-d7core
    Issue #2970950: adds a check to ensure we only send the phpversion for...

  • c249ad7 committed on 7.x-3.x
    Issue #2970950: adds a check to ensure we only send the phpversion for...
joseph.olstad’s picture

I just re-triggered a bunch of tests to see if this helps, same issue:

[D7] Enable error logging to log a backtrace string
Issue changes:
- Status: Needs review
+ Status: Needs work
The last submitted patch, 18: 2777955-18.patch [1], failed testing. View
results

Add last 'changed' property to user entity
Issue changes:
- Status: Needs review
+ Status: Needs work
The last submitted patch, 20: drupal-user-changed-property-1835754-19.patch
[1], failed testing. View results [2]

valid_email_address() should be easily overridable
Issue changes:
- Status: Needs review
+ Status: Needs work
The last submitted patch, 8: hook_valid_email_address_alter-2966195-8.patch
[1], failed testing. View results [2]

[D7] Improve WebTestCase performance by 50%
#71 -- 16 May 2018 at 01:17 UTC : System Message
https://www.drupal.org/project/drupal/issues/2759197#comment-12616006
The last submitted patch, 63: 2759197-simpletest-perf-63.patch [1], failed
testing. View results [2]

Mixologic’s picture

The testbots have been using composer to build out the d7 sites because some d7 modules actually do have composer requirements and the only way to test those is by using composer.

This was a bug only for d7 core testing, because we dont actually use any composer for that because it only needed to be a git clone, so it was erroneously creating an additional composer install step. I've added a check and it should no longer do this.

In any case, testing isn't really blocking progress here. The truth is that there isn't really anybody actively maintaining D7. David Rothstein, I believe, is stepping down from his committer role now that he's working for Automattic (https://www.linkedin.com/in/david-mark-rothstein), Stefan.r hasnt made a commit since the community issue with crell happened, and Fabian hasnt made a commit in a year and a half.

So once these tests are green and RTBC, whats truly blocking progress is that there isnt anybody actively maintaining drupal 7 as a committer.

I mention this mostly to help explain why a bug like this gets such a low priority.

Mixologic’s picture

I think you may have jumped the gun.

This is one that I retested after I had deployed the changes to drupal.org, and it appears to be running successfully:

https://dispatcher.drupalci.org/job/drupal_d7/77595/console

joseph.olstad’s picture

ok I requeued those, we shall see this time

joseph.olstad’s picture

FabianX is actively maintaining D7 and there are others.

joseph.olstad’s picture

FabianX recently flagged 5 issues for pending Drupal 7 commit

Many people have pushed hard to get php 7.2 compatibility working, this testrunner issue is blocking progress.

joseph.olstad’s picture

I reran the testbot,

still broken

01:17:59 Composer Command Failed

exact same error as before.

Mixologic’s picture

No, you reran those issues before I pushed the change, just like I said in #16

joseph.olstad’s picture

Status: Needs work » Fixed

Thanks Mixologic, looks like the issue is resolved.

Status: Fixed » Closed (fixed)

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