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] update block style variations in global styles and check revisions match styles #62929

Open
github-actions bot opened this issue Jun 27, 2024 · 1 comment
Labels
[Type] Flaky Test Auto-generated flaky test report issue

Comments

@github-actions
Copy link

github-actions bot commented Jun 27, 2024

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

Test title

update block style variations in global styles and check revisions match styles

Test path

/test/e2e/specs/site-editor/block-style-variations.spec.js

Errors

[2024-06-27T14:31:37.116Z] Test passed after 2 failed attempts on trunk.
[2024-06-27T15:13:01.167Z] Test passed after 1 failed attempt on update/rename-modals.
[2024-06-27T15:16:42.968Z] Test passed after 1 failed attempt on try/posts-list.
[2024-06-27T16:58:39.426Z] Test passed after 1 failed attempt on remove/api-fetch-i18n-dep.
[2024-06-27T17:11:26.387Z] Test passed after 2 failed attempts on trunk.
[2024-06-27T17:18:23.812Z] Test passed after 1 failed attempt on feat/custom-select-control-v2-legacy-expose-private-api.
[2024-06-27T18:14:20.388Z] Test passed after 1 failed attempt on fix/triple-scrollbar-post-editor.
[2024-06-27T21:14:40.301Z] Test passed after 1 failed attempt on upgrade/ariakit.
[2024-06-28T16:40:18.298Z] Test passed after 1 failed attempt on try/props-fix-test.
Error: Timed out 5000ms waiting for expect(locator).toBeEnabled()

Locator: getByRole('region', { name: 'Editor top bar' }).getByRole('button', { name: 'Save' })
Expected: enabled
Received: disabled
Call log:
  - expect.toBeEnabled with timeout 5000ms
  - waiting for getByRole('region', { name: 'Editor top bar' }).getByRole('button', { name: 'Save' })
  -   locator resolved to <button type="button" aria-disabled="true" class="compon…>Save</button>
  -   unexpected value "disabled"
  -   locator resolved to <button type="button" aria-disabled="true" class="compon…>Save</button>
  -   unexpected value "disabled"
  -   locator resolved to <button type="button" aria-disabled="true" class="compon…>Save</button>
  -   unexpected value "disabled"
  -   locator resolved to <button type="button" aria-disabled="true" class="compon…>Save</button>
  -   unexpected value "disabled"
  -   locator resolved to <button type="button" aria-disabled="true" class="compon…>Save</button>
  -   unexpected value "disabled"
  -   locator resolved to <button type="button" aria-disabled="true" class="compon…>Save</button>
  -   unexpected value "disabled"
  -   locator resolved to <button type="button" aria-disabled="true" class="compon…>Save</button>
  -   unexpected value "disabled"

    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/block-style-variations.spec.js:157:5
@github-actions github-actions bot added the [Type] Flaky Test Auto-generated flaky test report issue label Jun 27, 2024
github-actions bot referenced this issue Jun 27, 2024
Co-authored-by: desrosj <[email protected]>
Co-authored-by: ellatrix <[email protected]>
github-actions bot referenced this issue Jun 27, 2024
* Recommend kebab-case in wp-class and remove outdated info about callback args

* Trigger actions again

Co-authored-by: luisherranz <[email protected]>
Co-authored-by: cbravobernal <[email protected]>
@filiphric
Copy link

Hey team! Hope you don’t mind me hopping in. I looked into this flaky test and I suspect that I was able to find the root cause. I recorded a short loom for you: https://www.loom.com/share/3fee6a5dff6547d494251e22fe1eba5f

here’s the replay of the test that I showcase in the video: https://app.replay.io/recording/apply-block-styles-variations-to-nested-blocks--a920945a-f7ab-4269-a6d2-ecbd677b8343

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Flaky Test Auto-generated flaky test report issue
Projects
None yet
Development

No branches or pull requests

1 participant