Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Flaky Test] should stay in block settings after making a change in that area #42451

Closed
github-actions bot opened this issue Jul 15, 2022 · 2 comments
Closed
Labels
[Status] Stale Gives the original author opportunity to update before closing. Can be reopened as needed. [Type] Flaky Test Auto-generated flaky test report issue

Comments

@github-actions
Copy link

github-actions bot commented Jul 15, 2022

Flaky test detected. This is an auto-generated issue by GitHub Actions. Please do NOT edit this manually.

Test title

should stay in block settings after making a change in that area

Test path

/test/e2e/specs/widgets/customizing-widgets.spec.js

Errors

[2022-07-15T03:08:02.935Z] Test passed after 1 failed attempt on trunk.
[2023-02-27T19:57:40.079Z] Test passed after 1 failed attempt on try/set-attrs-idle.
[2023-03-21T04:18:30.860Z] Test passed after 1 failed attempt on try/grid-layout.
[2023-04-10T17:27:31.515Z] Test passed after 1 failed attempt on component-changelog-check-exclude-mobile.
[2023-04-10T18:04:52.364Z] Test passed after 1 failed attempt on component-changelog-check-exclude-mobile.
TimeoutError: page.click: Timeout 10000ms exceeded.
=========================== logs ===========================
waiting for locator('role=heading[name=/Footer #1/i][level=3]')
============================================================
    at WidgetsCustomizerPage.expandWidgetArea (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/widgets/customizing-widgets.spec.js:647:19)
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/widgets/customizing-widgets.spec.js:537:3
@github-actions github-actions bot added the [Type] Flaky Test Auto-generated flaky test report issue label Jul 15, 2022
@github-actions
Copy link
Author

This issue has gone 30 days without any activity.

@github-actions github-actions bot added the [Status] Stale Gives the original author opportunity to update before closing. Can be reopened as needed. label Aug 25, 2022
@github-actions github-actions bot reopened this Feb 27, 2023
@github-actions github-actions bot mentioned this issue Feb 27, 2023
@github-actions github-actions bot removed the [Status] Stale Gives the original author opportunity to update before closing. Can be reopened as needed. label Mar 1, 2023
@Mamaduka Mamaduka closed this as completed Mar 2, 2023
@github-actions github-actions bot reopened this Mar 21, 2023
@github-actions
Copy link
Author

This issue has gone 30 days without any activity.

@github-actions github-actions bot added the [Status] Stale Gives the original author opportunity to update before closing. Can be reopened as needed. label May 11, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Status] Stale Gives the original author opportunity to update before closing. Can be reopened as needed. [Type] Flaky Test Auto-generated flaky test report issue
Projects
None yet
Development

No branches or pull requests

1 participant