TimeoutError: Navigation timeout of 30000 ms exceeded at /home/runner/work/gutenberg/gutenberg/node_modules/puppeteer-core/src/common/LifecycleWatcher.ts:205:18 at FrameManager.waitForFrameNavigation (/home/runner/work/gutenberg/gutenberg/node_modules/puppeteer-core/src/common/FrameManager.ts:238:19) at Frame.waitForNavigation (/home/runner/work/gutenberg/gutenberg/node_modules/puppeteer-core/src/common/FrameManager.ts:785:12) at Page.waitForNavigation (/home/runner/work/gutenberg/gutenberg/node_modules/puppeteer-core/src/common/Page.ts:1833:12) at async Promise.all (index 1) at Object.<anonymous> (/home/runner/work/gutenberg/gutenberg/packages/e2e-tests/specs/local/demo.test.js:33:3)

Process completed with exit code 1.

1) [chromium] › editor/various/post-editor-template-mode.spec.js:73:2 › Post Editor Template mode › Allow creating custom block templates in classic themes Test timeout of 100000ms exceeded.

1) [chromium] › editor/various/post-editor-template-mode.spec.js:73:2 › Post Editor Template mode › Allow creating custom block templates in classic themes Error: page.waitForLoadState: Navigation failed because page was closed! 207 | // And the save states will not be counted as dirty. 208 | // There is likely a bug in the code, waiting for the snackbar above should be enough. > 209 | await this.page.waitForLoadState( 'networkidle' ); | ^ 210 | } 211 | 212 | async saveTemplateWithoutPublishing() { at PostEditorTemplateMode.createNewTemplate (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/post-editor-template-mode.spec.js:209:19) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/post-editor-template-mode.spec.js:85:3

1) [chromium] › editor/various/post-editor-template-mode.spec.js:73:2 › Post Editor Template mode › Allow creating custom block templates in classic themes Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 100000ms exceeded.

1) [chromium] › editor/various/post-editor-template-mode.spec.js:73:2 › Post Editor Template mode › Allow creating custom block templates in classic themes Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: page.waitForLoadState: Navigation failed because page was closed! 207 | // And the save states will not be counted as dirty. 208 | // There is likely a bug in the code, waiting for the snackbar above should be enough. > 209 | await this.page.waitForLoadState( 'networkidle' ); | ^ 210 | } 211 | 212 | async saveTemplateWithoutPublishing() { at PostEditorTemplateMode.createNewTemplate (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/post-editor-template-mode.spec.js:209:19) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/post-editor-template-mode.spec.js:85:3

1) [chromium] › editor/various/post-editor-template-mode.spec.js:73:2 › Post Editor Template mode › Allow creating custom block templates in classic themes Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 100000ms exceeded.

1) [chromium] › editor/various/post-editor-template-mode.spec.js:73:2 › Post Editor Template mode › Allow creating custom block templates in classic themes Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: page.waitForLoadState: Navigation failed because page was closed! 207 | // And the save states will not be counted as dirty. 208 | // There is likely a bug in the code, waiting for the snackbar above should be enough. > 209 | await this.page.waitForLoadState( 'networkidle' ); | ^ 210 | } 211 | 212 | async saveTemplateWithoutPublishing() { at PostEditorTemplateMode.createNewTemplate (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/post-editor-template-mode.spec.js:209:19) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/post-editor-template-mode.spec.js:85:3

2) [webkit] › editor/various/a11y-region-navigation.spec.js:15:2 › Region navigation (@Firefox, @WebKit) › navigates forward and back again { code: 'internal_server_error', message: '<p>There has been a critical error on this website.</p><p><a href="https://wordpress.org/documentation/article/faq-troubleshooting/">Learn more about troubleshooting WordPress.</a></p>', data: { status: 500 }, additional_errors: [] }

Process completed with exit code 1.

314 passed (26.4m)