1) [chromium] › specs/modules/modules-common.test.js:34:3 › Modules › The critical_css module state should toggle to an inverse state TimeoutError: locator.waitFor: Timeout 20000ms exceeded. Call log: - waiting for locator('.jb-feature-toggle-critical_css .components-form-toggle') to be visible at lib/pages/wp-admin/JetpackBoostPage.js:76 74 | `.jb-feature-toggle-${ moduleName } .components-form-toggle` 75 | ); > 76 | await toggleSwitch.waitFor(); | ^ 77 | const classNames = await toggleSwitch.getAttribute( 'class' ); 78 | 79 | return classNames.includes( 'is-checked' ); at JetpackBoostPage.isModuleEnabled (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/pages/wp-admin/JetpackBoostPage.js:76:22) at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/modules/modules-common.test.js:37:28

1) [chromium] › specs/modules/modules-common.test.js:34:3 › Modules › The critical_css module state should toggle to an inverse state Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.waitFor: Timeout 20000ms exceeded. Call log: - waiting for locator('.jb-feature-toggle-critical_css .components-form-toggle') to be visible at lib/pages/wp-admin/JetpackBoostPage.js:76 74 | `.jb-feature-toggle-${ moduleName } .components-form-toggle` 75 | ); > 76 | await toggleSwitch.waitFor(); | ^ 77 | const classNames = await toggleSwitch.getAttribute( 'class' ); 78 | 79 | return classNames.includes( 'is-checked' ); at JetpackBoostPage.isModuleEnabled (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/pages/wp-admin/JetpackBoostPage.js:76:22) at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/modules/modules-common.test.js:37:28

1) [chromium] › specs/modules/modules-common.test.js:34:3 › Modules › The critical_css module state should toggle to an inverse state Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.waitFor: Timeout 20000ms exceeded. Call log: - waiting for locator('.jb-feature-toggle-critical_css .components-form-toggle') to be visible at lib/pages/wp-admin/JetpackBoostPage.js:76 74 | `.jb-feature-toggle-${ moduleName } .components-form-toggle` 75 | ); > 76 | await toggleSwitch.waitFor(); | ^ 77 | const classNames = await toggleSwitch.getAttribute( 'class' ); 78 | 79 | return classNames.includes( 'is-checked' ); at JetpackBoostPage.isModuleEnabled (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/pages/wp-admin/JetpackBoostPage.js:76:22) at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/modules/modules-common.test.js:37:28

Process completed with exit code 1.

1) [chromium] › specs/critical-css/critical-css.test.js:47:2 › Critical CSS module › Critical CSS should be generated when the module is active TimeoutError: locator.waitFor: Timeout 20000ms exceeded. Call log: - waiting for locator('.jb-critical-css-progress').first() to be visible at ../../../../../tools/e2e-commons/pages/page-actions.js:320 318 | ); 319 | const element = this.page.locator( selector ).first(); > 320 | await element.waitFor( { state, timeout } ); | ^ 321 | return element; 322 | } 323 | at JetpackBoostPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:320:17) at JetpackBoostPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:269:21) at JetpackBoostPage.waitForCriticalCssGenerationProgressUIVisibility (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/pages/wp-admin/JetpackBoostPage.js:111:15) at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:51:27

1) [chromium] › specs/critical-css/critical-css.test.js:47:2 › Critical CSS module › Critical CSS should be generated when the module is active Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.waitFor: Timeout 20000ms exceeded. Call log: - waiting for locator('.jb-critical-css-progress').first() to be visible at ../../../../../tools/e2e-commons/pages/page-actions.js:320 318 | ); 319 | const element = this.page.locator( selector ).first(); > 320 | await element.waitFor( { state, timeout } ); | ^ 321 | return element; 322 | } 323 | at JetpackBoostPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:320:17) at JetpackBoostPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:269:21) at JetpackBoostPage.waitForCriticalCssGenerationProgressUIVisibility (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/pages/wp-admin/JetpackBoostPage.js:111:15) at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:51:27

1) [chromium] › specs/critical-css/critical-css.test.js:47:2 › Critical CSS module › Critical CSS should be generated when the module is active Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.waitFor: Timeout 20000ms exceeded. Call log: - waiting for locator('.jb-critical-css-progress').first() to be visible at ../../../../../tools/e2e-commons/pages/page-actions.js:320 318 | ); 319 | const element = this.page.locator( selector ).first(); > 320 | await element.waitFor( { state, timeout } ); | ^ 321 | return element; 322 | } 323 | at JetpackBoostPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:320:17) at JetpackBoostPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:269:21) at JetpackBoostPage.waitForCriticalCssGenerationProgressUIVisibility (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/pages/wp-admin/JetpackBoostPage.js:111:15) at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:51:27

2) [chromium] › specs/critical-css/critical-css.test.js:60:2 › Critical CSS module › Critical CSS meta information should show on the admin when the module is re-activated TimeoutError: locator.waitFor: Timeout 180000ms exceeded. Call log: - waiting for locator('[data-testid="critical-css-meta"]').first() to be visible at ../../../../../tools/e2e-commons/pages/page-actions.js:320 318 | ); 319 | const element = this.page.locator( selector ).first(); > 320 | await element.waitFor( { state, timeout } ); | ^ 321 | return element; 322 | } 323 | at JetpackBoostPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:320:17) at JetpackBoostPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:269:21) at JetpackBoostPage.waitForCriticalCssMetaInfoVisibility (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/pages/wp-admin/JetpackBoostPage.js:106:15) at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:65:27

2) [chromium] › specs/critical-css/critical-css.test.js:60:2 › Critical CSS module › Critical CSS meta information should show on the admin when the module is re-activated Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.waitFor: Timeout 180000ms exceeded. Call log: - waiting for locator('[data-testid="critical-css-meta"]').first() to be visible at ../../../../../tools/e2e-commons/pages/page-actions.js:320 318 | ); 319 | const element = this.page.locator( selector ).first(); > 320 | await element.waitFor( { state, timeout } ); | ^ 321 | return element; 322 | } 323 | at JetpackBoostPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:320:17) at JetpackBoostPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:269:21) at JetpackBoostPage.waitForCriticalCssMetaInfoVisibility (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/pages/wp-admin/JetpackBoostPage.js:106:15) at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:65:27

2) [chromium] › specs/critical-css/critical-css.test.js:60:2 › Critical CSS module › Critical CSS meta information should show on the admin when the module is re-activated Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.waitFor: Timeout 180000ms exceeded. Call log: - waiting for locator('[data-testid="critical-css-meta"]').first() to be visible at ../../../../../tools/e2e-commons/pages/page-actions.js:320 318 | ); 319 | const element = this.page.locator( selector ).first(); > 320 | await element.waitFor( { state, timeout } ); | ^ 321 | return element; 322 | } 323 | at JetpackBoostPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:320:17) at JetpackBoostPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:269:21) at JetpackBoostPage.waitForCriticalCssMetaInfoVisibility (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/pages/wp-admin/JetpackBoostPage.js:106:15) at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:65:27

3) [chromium] › specs/critical-css/critical-css.test.js:70:2 › Critical CSS module › Critical CSS should be available on the frontend when the module is active TimeoutError: locator.innerText: Timeout 20000ms exceeded. Call log: - waiting for locator('#jetpack-boost-critical-css') 70 | test( 'Critical CSS should be available on the frontend when the module is active', async () => { 71 | await PostFrontendPage.visit( page ); > 72 | const criticalCss = await page.locator( '#jetpack-boost-critical-css' ).innerText(); | ^ 73 | expect( criticalCss.length, 'Critical CSS should be displayed' ).toBeGreaterThan( 100 ); 74 | } ); 75 | at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:72:75

3) [chromium] › specs/critical-css/critical-css.test.js:70:2 › Critical CSS module › Critical CSS should be available on the frontend when the module is active Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.innerText: Timeout 20000ms exceeded. Call log: - waiting for locator('#jetpack-boost-critical-css') 70 | test( 'Critical CSS should be available on the frontend when the module is active', async () => { 71 | await PostFrontendPage.visit( page ); > 72 | const criticalCss = await page.locator( '#jetpack-boost-critical-css' ).innerText(); | ^ 73 | expect( criticalCss.length, 'Critical CSS should be displayed' ).toBeGreaterThan( 100 ); 74 | } ); 75 | at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:72:75

3) [chromium] › specs/critical-css/critical-css.test.js:70:2 › Critical CSS module › Critical CSS should be available on the frontend when the module is active Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.innerText: Timeout 20000ms exceeded. Call log: - waiting for locator('#jetpack-boost-critical-css') 70 | test( 'Critical CSS should be available on the frontend when the module is active', async () => { 71 | await PostFrontendPage.visit( page ); > 72 | const criticalCss = await page.locator( '#jetpack-boost-critical-css' ).innerText(); | ^ 73 | expect( criticalCss.length, 'Critical CSS should be displayed' ).toBeGreaterThan( 100 ); 74 | } ); 75 | at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:72:75

4) [chromium] › specs/critical-css/critical-css.test.js:76:2 › Critical CSS module › Critical CSS Admin message should show when the theme is changed TimeoutError: locator.waitFor: Timeout 20000ms exceeded. Call log: - waiting for locator('.jb-critical-css-progress').first() to be visible at ../../../../../tools/e2e-commons/pages/page-actions.js:320 318 | ); 319 | const element = this.page.locator( selector ).first(); > 320 | await element.waitFor( { state, timeout } ); | ^ 321 | return element; 322 | } 323 | at JetpackBoostPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:320:17) at JetpackBoostPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:269:21) at JetpackBoostPage.waitForCriticalCssGenerationProgressUIVisibility (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/pages/wp-admin/JetpackBoostPage.js:111:15) at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:92:27

1) [chromium] › specs/page-cache/page-cache.test.js:89:2 › Cache module › Page Cache meta information should show on the admin when the module is active TimeoutError: page.click: Timeout 20000ms exceeded. Call log: - waiting for locator('[id="submit"]') - locator resolved to <input id="submit" type="submit" name="submit" value="Save Changes" class="button button-primary"/> - 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 - click action done - waiting for scheduled navigations to finish at lib/pages/wp-admin/PermalinksPage.js:20 18 | const selector = '[id="permalink-input-day-name"]'; 19 | await this.page.click( selector ); > 20 | await this.page.click( '[id="submit"]' ); | ^ 21 | await this.waitForLoad(); 22 | } 23 | } at PermalinksPage.useDayNameStructure (/home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/lib/pages/wp-admin/PermalinksPage.js:20:19) at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/page-cache/page-cache.test.js:91:3

The job running on runner GitHub Actions 289 has exceeded the maximum execution time of 60 minutes.

The operation was canceled.

1 passed (51.5s)

2 passed (3.4m)

1 passed (1.2m)

3 passed (2.1m)

1 failed [chromium] › specs/modules/modules-common.test.js:34:3 › Modules › The critical_css module state should toggle to an inverse state 4 did not run 8 passed (3.4m)

2 passed (3.1m)

5 passed (1.2m)

6 failed [chromium] › specs/critical-css/critical-css.test.js:47:2 › Critical CSS module › Critical CSS should be generated when the module is active [chromium] › specs/critical-css/critical-css.test.js:60:2 › Critical CSS module › Critical CSS meta information should show on the admin when the module is re-activated [chromium] › specs/critical-css/critical-css.test.js:70:2 › Critical CSS module › Critical CSS should be available on the frontend when the module is active [chromium] › specs/critical-css/critical-css.test.js:76:2 › Critical CSS module › Critical CSS Admin message should show when the theme is changed [chromium] › specs/critical-css/critical-css.test.js:101:2 › Critical CSS module › Critical CSS should be generated with an error (advanced recommendations) [chromium] › specs/critical-css/critical-css.test.js:132:2 › Critical CSS module › User can access the Critical advanced recommendations and go back to settings page 2 passed (18.7m)

1 flaky [chromium] › specs/page-cache/page-cache.test.js:89:2 › Cache module › Page Cache meta information should show on the admin when the module is active 4 passed (2.7m)

4 passed (55.7s)

2 passed (37.3s)

6 passed (2.2m)

3 passed (2.7m)