1) [chromium] › interactivity/router-navigate.spec.ts:124:6 › Router navigate › should reload the next page when the timeout ends TimeoutError: locator.click: Timeout 10000ms exceeded. =========================== logs =========================== waiting for getByTestId('link 1') locator resolved to <a data-testid="link 1" data-wp-on--click="actions.…>link 1</a> attempting click action waiting for element to be visible, enabled and stable element is visible, enabled and stable scrolling into view if needed done scrolling performing click action ============================================================ 150 | 151 | // Navigation should timeout almost instantly. > 152 | await page.getByTestId( 'link 1' ).click(); | ^ 153 | 154 | await expect( page ).toHaveURL( link1 ); 155 | await expect( title ).toHaveText( 'Link 1' ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:152:38

1) [chromium] › interactivity/router-navigate.spec.ts:124:6 › Router navigate › should reload the next page when the timeout ends Test finished within timeout of 100000ms, but tearing down "page" ran out of time. Please allow more time for the test, since teardown is attributed towards the test timeout budget.

Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

130 passed (6.2m)

1 skipped 114 passed (5.9m)

1 skipped 119 passed (6.8m)

1 skipped 150 passed (6.5m)

134 passed (7.2m)

3 skipped 119 passed (7.2m)

11 skipped 152 passed (7.4m)