Make tests pass on 6.2.x.

Issue fork webform-3500571

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

liam morland created an issue. See original summary.

liam morland’s picture

Tests are now passing on 6.2.x on Drupal 10.3.12, but only with one failing test commented-out. To-do list:

  1. Re-enable the removed test and get it to pass.
  2. Get tests to pass on Drupal 10.4

  • liam morland committed 013ca6da on 6.2.x
    Issue #3500571: Fix coding standards issue
    
    Fixes issue introduced in...

liam morland’s picture

Status: Active » Needs work
liam morland’s picture

I have disabled some tests. There are still test failures. These may be caused by running the tests on more recent versions of Drupal 10.

damienmckenna made their first commit to this issue’s fork.

damienmckenna’s picture

Status: Needs work » Needs review

I added a missing test dependency and changed the tests to run concurrently, that allowed them to finish in ~18 minutes instead of timing out after ~30 minutes. The tests are now green.

liam morland’s picture

Parent issue: » #3489891: Fix tests in 6.2.x

After committing some small changes, test are currently passing on 6.2.x, however one test assertion is still disabled. The merge request now re-enables that assertion, so the merge request fails. Adding the dependency on jquery_ui_controlgroup did not fix it. I think this should be fixed first then the version of Drupal that tests are run in should be advanced.

liam morland’s picture

Status: Needs review » Needs work
damienmckenna’s picture

The dependency issue showed up when I ran all of the tests locally, maybe it was a dependency of another dependency so it was my fault it failed locally.

The fact that it's failing at 189 tests and not finishing them all suggests it's not running the tests concurrently per the _PHPUNIT_CONCURRENT setting - does the issue fork need to be updated?

liam morland’s picture

They are running concurrently, but take almost the full half-hour so they could sometimes run over. It's also failing on the test assertion that is re-enabled by this merge request. See the previous test run for that failure.

damienmckenna’s picture

Ok, I see that now.

Is there normally such a variation in how long the tests take to run? When I added the _PHPUNIT_CONCURRENT line initially the tests ran in <20 minutes, now it's hitting twice that and timing out.

liam morland’s picture

When you added that, there was a whole test file that had been deleted because it was failing. That is now back in.

damienmckenna’s picture

WebformVariantOverrideTest passes locally but fails on gitlabci. Hrm..

damienmckenna’s picture

damienmckenna’s picture

My suggestion is that for now release this as-is with the test line commented out and then work on the one failing test separately, just to be able to move on.

liam morland’s picture

Yes, that is the current state of things. Tests pass on 6.2.x but only because one test assertion is commented-out. The merge request in this issue re-enables it.

  • liam morland committed 9e1cdaf2 on 6.2.x
    fix: #3500571 Test on Drupal 10.6.3 and comment-out failing tests
    
liam morland’s picture

I have commented-out several more tests. Tests are now passing on Drupal 10.6.3. The tests should be fixed-up so that they can be run again.