Problem/Motivation

In #3350972: [random test failure] Drupal\Tests\layout_builder\FunctionalJavascript\LayoutBuilderUiTest::testReloadWithNoSections() @nod_ introduced a "fix" for problems with the correct opening of an off-canvas dialog which potentially could fix all JS random test failures for tests using the drupal.dialog.off_canvas somehow.

The basic test is:

  1. Unskip all $this->markTestSkipped(); in \Drupal\Tests\layout_builder\FunctionalJavascript\ContextualLinksTest.
  2. Run _only_ now unskipped \Drupal\Tests\layout_builder\FunctionalJavascript\ContextualLinksTest a lot of times (usually we go for 1500x) as-is.
  3. Run _only_ now unskipped \Drupal\Tests\layout_builder\FunctionalJavascript\ContextualLinksTest a lot of times (usually we go for 1500x) _without_ the changes in #3350972: [random test failure] Drupal\Tests\layout_builder\FunctionalJavascript\LayoutBuilderUiTest::testReloadWithNoSections().
  4. If 2., passes and 3. doesn't, we can safely turn the test back on again.

Per @xjm in #3353085-4: [meta] Determine impact of [#3350972] fix in off-canvas.js on currently disabled FunctionalJavascript tests we now need to go for a 5000-8000 times run for both patches.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Comments

Spokje created an issue. See original summary.

spokje’s picture

spokje’s picture

StatusFileSize
new670 bytes
spokje’s picture

Status: Active » Needs review
spokje’s picture

StatusFileSize
new2.85 KB
new3.34 KB

Right...

So we have a skipped assertion in a skipped test...

Let's see what happens if we un-skip them at the same time.

spokje’s picture

Title: [random test failure] Try to un-skip and fix ContextualLinksTest::testContextualLinks() in context of [#3353085] » [random test failure] Try to un-skip and fix ContextualLinksTest in context of [#3353085]
Issue summary: View changes
StatusFileSize
new1.08 KB

smustgrave’s picture

Status: Needs review » Reviewed & tested by the community
Issue tags: +Needs Review Queue Initiative

Condition in the issue summary appears to have been met.

spokje’s picture

Issue summary: View changes

spokje’s picture

Assigned: Unassigned » spokje
Status: Reviewed & tested by the community » Needs work
spokje’s picture

Assigned: spokje » Unassigned
Status: Needs work » Reviewed & tested by the community

Both should_fail and non_fail patch run 5 times. That's 7500 individual tests per patch.

Back to RTBC.

xjm’s picture

Added additional test jobs and waiting on those for commit.

xjm’s picture

Fixing attribution.

  • catch committed 3e7279b0 on 10.1.x
    Issue #3353092 by Spokje: [random test failure] Try to un-skip and fix...

  • catch committed 2ac23c8f on 10.0.x
    Issue #3353092 by Spokje: [random test failure] Try to un-skip and fix...

  • catch committed c4ed1535 on 9.5.x
    Issue #3353092 by Spokje: [random test failure] Try to un-skip and fix...
catch’s picture

Version: 10.1.x-dev » 9.5.x-dev
Status: Reviewed & tested by the community » Fixed

Committed/pushed to 10.1.x, thanks! Since this is the last of the current round to be re-enabled I've also cherry-picked back to 10.0.x and 9.5.x. Next to cherry-pick back the other patches.

Status: Fixed » Closed (fixed)

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