Problem/Motivation

This is already skipped in main and is now failing consistently in 11.x

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Issue fork drupal-3614142

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:

About issue forks

Comments

catch created an issue. See original summary.

catch’s picture

catch
he/him
Primary language English
commented
Status: Active » Needs review

catch opened merge request !16492

catch’s picture

catch
he/him
Primary language English
commented
Title: Skip SettingsTrayBlockFormTest methods on 11.x » Skip SettingsTrayBlockFormTest::testBlocks() on 11.x
godotislate’s picture

godotislate
he/him
commented
Status: Needs review » Reviewed & tested by the community

Change is very straightforward and 11.x tests are failing 100%. Let's do this!

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

Hm MR is to merge to main? So its not already skipped in main? Should this be merged to main and going down to 11.x?

  • longwave committed 3ae7587f on 11.x 
    test: #3614142 Skip SettingsTrayBlockFormTest::testBlocks() on 11.x

By...

  • longwave committed 23c059a2 on main 
    test: #3614142 Skip SettingsTrayBlockFormTest::testBlocks() on 11.x

By...
longwave’s picture

longwave
he/him
Primary language English
Location UK
commented
Version: main » 11.x-dev
Status: Reviewed & tested by the community » Fixed

Yeah this wasn't skipped in main that I could see, but let's skip in both, settings tray is going away anyway and it gets little usage.

Committed and pushed 23c059a23fe to main and 3ae7587ff2a to 11.x. Thanks!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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