Skip to content

Make post meta row button treatment consistent #105568

Make post meta row button treatment consistent

Make post meta row button treatment consistent #105568

Triggered via pull request May 30, 2024 10:30
Status Success
Total duration 31m 53s
Artifacts 2

end2end-test.yml

on: pull_request
Matrix: e2e-playwright
Merge Artifacts
3s
Merge Artifacts
Report to GitHub
4m 34s
Report to GitHub
Fit to window
Zoom out
Zoom in

Annotations

9 errors, 1 warning, and 8 notices
[chromium] › site-editor/dataviews-list-layout-keyboard.spec.js:34:2 › Dataviews List Layout › Items list is reachable via TAB: test/e2e/specs/site-editor/dataviews-list-layout-keyboard.spec.js#L57
1) [chromium] › site-editor/dataviews-list-layout-keyboard.spec.js:34:2 › Dataviews List Layout › Items list is reachable via TAB Error: Timed out 5000ms waiting for expect(locator).toBeFocused() Locator: getByLabel('Privacy Policy') Expected: focused Received: inactive Call log: - expect.toBeFocused with timeout 5000ms - waiting for getByLabel('Privacy Policy') - locator resolved to <div role="button" tabindex="-1" id="view-list-0-173"…>…</div> - unexpected value "not focused" - locator resolved to <div role="button" tabindex="-1" id="view-list-0-173"…>…</div> - unexpected value "not focused" - locator resolved to <div role="button" tabindex="-1" id="view-list-0-173"…>…</div> - unexpected value "not focused" - locator resolved to <div role="button" tabindex="-1" id="view-list-0-173"…>…</div> - unexpected value "not focused" - locator resolved to <div role="button" tabindex="-1" id="view-list-0-173"…>…</div> - unexpected value "not focused" - locator resolved to <div role="button" tabindex="-1" id="view-list-0-173"…>…</div> - unexpected value "not focused" - locator resolved to <div role="button" tabindex="-1" id="view-list-0-173"…>…</div> - unexpected value "not focused" - locator resolved to <div role="button" tabindex="-1" id="view-list-0-173"…>…</div> - unexpected value "not focused" - locator resolved to <div role="button" tabindex="-1" id="view-list-0-173"…>…</div> - unexpected value "not focused" 55 | await expect( page.getByRole( 'grid' ) ).toBeVisible(); 56 | await page.keyboard.press( 'Tab' ); > 57 | await expect( page.getByLabel( 'Privacy Policy' ) ).toBeFocused(); | ^ 58 | } ); 59 | 60 | test( 'Navigates from items list to preview via TAB, and vice versa', async ( { at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/dataviews-list-layout-keyboard.spec.js:57:55
[chromium] › editor/blocks/comments.spec.js:60:2 › Comments › Pagination links are working as expected: test/e2e/specs/editor/blocks/comments.spec.js#L24
1) [chromium] › editor/blocks/comments.spec.js:60:2 › Comments › Pagination links are working as expected Test timeout of 100000ms exceeded while running "beforeEach" hook. 22 | } ); 23 | > 24 | test.beforeEach( async ( { commentsBlockUtils } ) => { | ^ 25 | // Ideally, we'd set options in beforeAll or afterAll. Unfortunately, these 26 | // aren't exposed via the REST API, so we have to set them through the 27 | // relevant wp-admin screen, which involves page utils; but those are at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/comments.spec.js:24:7
[chromium] › editor/blocks/comments.spec.js:60:2 › Comments › Pagination links are working as expected: test/e2e/specs/editor/blocks/comments.spec.js#L1
1) [chromium] › editor/blocks/comments.spec.js:60:2 › Comments › Pagination links are working as expected Test timeout of 100000ms exceeded.
[chromium] › editor/blocks/comments.spec.js:60:2 › Comments › Pagination links are working as expected: test/e2e/specs/editor/blocks/comments.spec.js#L41
1) [chromium] › editor/blocks/comments.spec.js:60:2 › Comments › Pagination links are working as expected "afterAll" hook timeout of 100000ms exceeded. 39 | } ); 40 | > 41 | test.afterAll( async ( { requestUtils } ) => { | ^ 42 | await requestUtils.activateTheme( 'twentytwentyone' ); 43 | } ); 44 | at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/comments.spec.js:41:7
[chromium] › editor/blocks/comments.spec.js:60:2 › Comments › Pagination links are working as expected: test/e2e/specs/editor/blocks/comments.spec.js#L1
1) [chromium] › editor/blocks/comments.spec.js:60:2 › Comments › Pagination links are working as expected Error: Object with guid response@ab8cfe6d2f9ade207fc4060bef5b4881 was not bound in the connection
[chromium] › editor/blocks/comments.spec.js:60:2 › Comments › Pagination links are working as expected: test/e2e/specs/editor/blocks/comments.spec.js#L24
1) [chromium] › editor/blocks/comments.spec.js:60:2 › Comments › Pagination links are working as expected Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 100000ms exceeded while running "beforeEach" hook. 22 | } ); 23 | > 24 | test.beforeEach( async ( { commentsBlockUtils } ) => { | ^ 25 | // Ideally, we'd set options in beforeAll or afterAll. Unfortunately, these 26 | // aren't exposed via the REST API, so we have to set them through the 27 | // relevant wp-admin screen, which involves page utils; but those are at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/comments.spec.js:24:7
[chromium] › editor/blocks/comments.spec.js:60:2 › Comments › Pagination links are working as expected: test/e2e/specs/editor/blocks/comments.spec.js#L1
1) [chromium] › editor/blocks/comments.spec.js:60:2 › Comments › Pagination links are working as expected Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 100000ms exceeded.
[chromium] › editor/blocks/comments.spec.js:60:2 › Comments › Pagination links are working as expected: test/e2e/specs/editor/blocks/comments.spec.js#L41
1) [chromium] › editor/blocks/comments.spec.js:60:2 › Comments › Pagination links are working as expected Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── "afterAll" hook timeout of 100000ms exceeded. 39 | } ); 40 | > 41 | test.afterAll( async ( { requestUtils } ) => { | ^ 42 | await requestUtils.activateTheme( 'twentytwentyone' ); 43 | } ); 44 | at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/comments.spec.js:41:7
[chromium] › editor/blocks/comments.spec.js:60:2 › Comments › Pagination links are working as expected: test/e2e/specs/editor/blocks/comments.spec.js#L1
1) [chromium] › editor/blocks/comments.spec.js:60:2 › Comments › Pagination links are working as expected Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Object with guid response@30b6e12c90849217400b101b72023de8 was not bound in the connection
Report to GitHub
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: ./packages/report-flaky-tests. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
🎭 Playwright Run Summary
4 skipped 191 passed (5.5m)
🎭 Playwright Run Summary
3 skipped 146 passed (7.9m)
🎭 Playwright Run Summary
1 flaky [chromium] › site-editor/dataviews-list-layout-keyboard.spec.js:34:2 › Dataviews List Layout › Items list is reachable via TAB 184 passed (8.9m)
🎭 Playwright Run Summary
1 skipped 189 passed (9.3m)
🎭 Playwright Run Summary
1 skipped 190 passed (9.3m)
🎭 Playwright Run Summary
1 skipped 189 passed (9.7m)
🎭 Playwright Run Summary
222 passed (12.5m)
🎭 Playwright Run Summary
1 flaky [chromium] › editor/blocks/comments.spec.js:60:2 › Comments › Pagination links are working as expected 189 passed (19.6m)

Artifacts

Produced during runtime
Name Size
failures-artifacts Expired
1.41 MB
flaky-tests-report Expired
2.2 KB