Problem/Motivation

Should we skip the test and keep this open as a critical issue to un-skip it?

@catch in #3361121-29: [random test failure] InstallerExistingConfig[SyncDirectory]MultilingualTest::testConfigSync

These have started failing randomly but very frequently. Let's skip both of them, then re-enable after fixing.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Issue fork drupal-3362306

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

Spokje created an issue. See original summary.

spokje’s picture

Status: Active » Needs review
lauriii’s picture

Status: Needs review » Needs work

Moving to NW because there's feedback on the MR

spokje’s picture

Status: Needs work » Needs review

@andypost, left a comment on your comment in the MR (comment-ception there...)

Hope it makes sense, as we've discovered before (#3361121-21: [random test failure] InstallerExistingConfig[SyncDirectory]MultilingualTest::testConfigSync), I'm not the greatest at explanations ;)

andypost’s picture

Status: Needs review » Reviewed & tested by the community

I think it's ok to disable it while further debug happening

  • catch committed 60131619 on 11.x
    Issue #3362306 by Spokje: Skip InstallerExistingConfig[SyncDirectory]...

  • catch committed 92d408fc on 10.1.x
    Issue #3362306 by Spokje: Skip InstallerExistingConfig[SyncDirectory]...
catch’s picture

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

Committed/pushed to 11.x and 10.1.x, thanks!

afaik this isn't failing randomly in 10.0.x, so leaving unskipped there.

spokje’s picture

afaik this isn't failing randomly in 10.0.x, so leaving unskipped there.

Correct, this _seems_ to be SF6.3 (and maybe some other stuff) related, whilst 10.0.x is still on SF6.2.

Status: Fixed » Closed (fixed)

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