Tests: Try reviewing a specific E2E test. #152605
end2end-test.yml
on: pull_request
Annotations
5 errors and 8 notices
|
[chromium] › specs/editor/various/publish-panel.spec.js:11:2 › Post publish panel › should move focus back to the Publish panel toggle button when canceling:
test/e2e/specs/editor/various/publish-panel.spec.js#L33
2) [chromium] › specs/editor/various/publish-panel.spec.js:11:2 › Post publish panel › should move focus back to the Publish panel toggle button when canceling
Error: expect(locator).toBeFocused() failed
Locator: locator('role=region[name="Editor top bar"i]').locator('role=button[name="Publish"i]')
Expected: focused
Received: inactive
Timeout: 5000ms
Call log:
- Expect "toBeFocused" with timeout 5000ms
- waiting for locator('role=region[name="Editor top bar"i]').locator('role=button[name="Publish"i]')
9 × locator resolved to <button type="button" aria-expanded="true" aria-disabled="false" class="components-button editor-post-publish-panel__toggle editor-post-publish-button__button is-primary is-compact">Publish</button>
- unexpected value "inactive"
31 |
32 | // Test focus is moved back to the Publish panel toggle button.
> 33 | await expect( publishPanelToggleButton ).toBeFocused();
| ^
34 | } );
35 |
36 | test( 'should move focus back to the Publish panel toggle button after publishing and closing the panel', async ( {
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/publish-panel.spec.js:33:44
|
|
[chromium] › specs/editor/various/post-content-focus-mode.spec.js:129:3 › Post Content focus mode › post content inside a template part › post title and content are editable and blocks can be inserted:
packages/e2e-test-utils-playwright/src/editor/select-blocks.ts#L26
1) [chromium] › specs/editor/various/post-content-focus-mode.spec.js:129:3 › Post Content focus mode › post content inside a template part › post title and content are editable and blocks can be inserted › Paragraph and Group blocks are available in the inserter
TimeoutError: locator.getAttribute: Timeout 10000ms exceeded.
Call log:
- waiting for locator('[name="editor-canvas"]').contentFrame().getByText('Initial content')
at ../../../packages/e2e-test-utils-playwright/src/editor/select-blocks.ts:26
24 | : endSelectorOrLocator;
25 |
> 26 | const startClientId = await startBlock.getAttribute( 'data-block' );
| ^
27 | const endClientId = await endBlock?.getAttribute( 'data-block' );
28 |
29 | if ( endClientId ) {
at Editor.selectBlocks (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/editor/select-blocks.ts:26:41)
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/post-content-focus-mode.spec.js:163:18
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/post-content-focus-mode.spec.js:159:15
|
|
[chromium] › specs/editor/blocks/navigation-frontend-interactivity.spec.js:528:3 › Navigation block - Frontend interactivity › Legacy openSubmenusOnClick backward compatibility › Should render and migrate legacy openSubmenusOnClick blocks:
test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js#L615
1) [chromium] › specs/editor/blocks/navigation-frontend-interactivity.spec.js:528:3 › Navigation block - Frontend interactivity › Legacy openSubmenusOnClick backward compatibility › Should render and migrate legacy openSubmenusOnClick blocks › Save post and verify migration was written to database
Error: expect(received).toContain(expected) // indexOf
Expected substring: "\"submenuVisibility\":\"click\""
Received string: "<!-- wp:navigation {\"openSubmenusOnClick\":true,\"overlayMenu\":\"never\"} -->
<!-- wp:navigation-submenu {\"label\":\"Products\"} -->
<!-- wp:navigation-link {\"label\":\"Product 1\",\"url\":\"#\"} /-->
<!-- wp:navigation-link {\"label\":\"Product 2\",\"url\":\"#\"} /-->
<!-- /wp:navigation-submenu -->
<!-- wp:navigation-link {\"label\":\"About\",\"url\":\"#\"} /-->
<!-- /wp:navigation -->"
613 | const content = savedPost.content.raw;
614 |
> 615 | expect( content ).toContain( '"submenuVisibility":"click"' );
| ^
616 | expect( content ).not.toContain( 'openSubmenusOnClick' );
617 | } );
618 |
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:615:23
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:593:4
|
|
[firefox] › specs/editor/various/writing-flow.spec.js:626:2 › Writing Flow (@firefox:
test/e2e/specs/editor/various/writing-flow.spec.js#L634
1) [firefox] › specs/editor/various/writing-flow.spec.js:626:2 › Writing Flow (@Firefox, @WebKit) › should merge paragraphs
Error: Timeout 5000ms exceeded while waiting on the predicate
632 | await page.keyboard.press( 'Backspace' );
633 |
> 634 | await expect.poll( editor.getEditedPostContent )
| ^
635 | .toBe( `<!-- wp:paragraph -->
636 | <p>12</p>
637 | <!-- /wp:paragraph -->` );
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/writing-flow.spec.js:634:3
|
|
[chromium] › specs/editor/collaboration/collaboration-stress.spec.ts:323:6 › Collaboration - Stress Test › three users concurrently edit a large post with diverse blocks:
test/e2e/specs/editor/collaboration/collaboration-stress.spec.ts#L417
1) [chromium] › specs/editor/collaboration/collaboration-stress.spec.ts:323:6 › Collaboration - Stress Test › three users concurrently edit a large post with diverse blocks
Error: expect(received).toContain(expected) // indexOf
Expected substring: "Admin was here"
Received string: "[{\"name\":\"core/heading\",\"attributes\":{\"content\":\"Introduction\",\"level\":2},\"innerBlocks\":[]},{\"name\":\"core/paragraph\",\"attributes\":{\"content\":\"The system processes data through multiple layers of abstraction ensuring consistency across all nodes. Reliability is maintained by distributed components that handle requests efficiently within the network. Each architecture layer guarantees strict ordering for operations that modify shared state. Synchronization protocols use vector clocks to track causal dependencies between updates. Optimistic replication propagates changes using conflict resolution based on deterministic rules. Concurrent modifications are detected and merged by specialized functions in the coordination layer. The protocol maintains eventual consistency while minimizing latency for participating clients. State transitions are validated against invariants before being committed to the distributed log. Recovery mechanisms\",\"dropCap\":false},\"innerBlocks\":[]},{\"name\":\"core/paragraph\",\"attributes\":{\"content\":\"Reliability is maintained by distributed components that handle requests efficiently within the network. Each architecture layer guarantees strict ordering for operations that modify shared state. Synchronization protocols use vector clocks to track causal dependencies between updates. Optimistic replication propagates changes using conflict resolution based on deterministic rules. Concurrent modifications are detected and merged by specialized functions in the coordination layer. The protocol maintains eventual consistency while minimizing latency for participating clients. State transitions are validated against invariants before being committed to the distributed log. Recovery mechanisms restore consistency after partial failures using checkpointed snapshots. Performance monitoring tracks throughput and latency\",\"dropCap\":false},\"innerBlocks\":[]},{\"name\":\"core/paragraph\",\"attributes\":{\"content\":\"Each architecture layer guarantees strict ordering for operations that modify shared state. Synchronization protocols use vector clocks to track causal dependencies between updates. Optimistic replication propagates changes using conflict resolution based on deterministic rules. Concurrent modifications are detected and merged by specialized functions in the coordination layer. The protocol maintains eventual consistency while minimizing latency for participating clients. State transitions are validated against invariants before being committed to the distributed log. Recovery mechanisms restore consistency after partial failures using checkpointed snapshots. Performance monitoring tracks throughput and latency metrics across all participating services. The coordination layer batches updates to reduce network\",\"dropCap\":false},\"innerBlocks\":[]},{\"name\":\"core/paragraph\",\"attributes\":{\"content\":\"Synchronization protocols use vector clocks to track causal dependencies between updates. Optimistic replication propagates changes using conflict resolution based on deterministic rules. Concurrent modifications are detected and merged by specialized functions in the coordination layer. The protocol maintains eventual consistency while minimizing latency for participating clients. State transitions are validated against invariants before being committed to the distributed log. Recovery mechanisms restore consistency after partial failures using checkpointed snapshots. Performance monitoring tracks throughput and latency metrics across all participating services. The coordination layer batches updates to reduce network overhead during peak traffic periods. Load balancing distributes requests across available replicas\",\"dropCap\":false},\"innerBlocks\":[]},{\
|
|
🎭 Playwright Run Summary
3 skipped
245 passed (11.2m)
|
|
🎭 Playwright Run Summary
2 flaky
[chromium] › specs/editor/various/post-content-focus-mode.spec.js:129:3 › Post Content focus mode › post content inside a template part › post title and content are editable and blocks can be inserted
[chromium] › specs/editor/various/publish-panel.spec.js:11:2 › Post publish panel › should move focus back to the Publish panel toggle button when canceling
5 skipped
246 passed (11.9m)
|
|
🎭 Playwright Run Summary
1 skipped
242 passed (13.8m)
|
|
🎭 Playwright Run Summary
4 skipped
246 passed (14.3m)
|
|
🎭 Playwright Run Summary
1 flaky
[chromium] › specs/editor/blocks/navigation-frontend-interactivity.spec.js:528:3 › Navigation block - Frontend interactivity › Legacy openSubmenusOnClick backward compatibility › Should render and migrate legacy openSubmenusOnClick blocks
259 passed (15.2m)
|
|
🎭 Playwright Run Summary
7 skipped
280 passed (17.6m)
|
|
|
|
🎭 Playwright Run Summary
1 flaky
[chromium] › specs/editor/collaboration/collaboration-stress.spec.ts:323:6 › Collaboration - Stress Test › three users concurrently edit a large post with diverse blocks
1 skipped
250 passed (25.9m)
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
blob-reports-merged
|
181 MB |
sha256:61e4d683a0bbf1013f9dd3be3a2ff5cd37ad005a9ffd9a9d142db0871eea3c51
|
|
|
flaky-tests-report
|
12.4 KB |
sha256:a973b0949df8347c61ff1cc29ebf55b6f936b0f819b70609dee7f35fe2e8e795
|
|
|
html-report--attempt-1
|
180 MB |
sha256:e2022c2cf99b92df33adf16787b6c742767e1039664f8d04ab23d3da971dbb02
|
|