Protect Meets Core: Home Page Scan Report Data Adjustments #95451
Annotations
10 errors, 1 warning, and 1 notice
|
Run Jetpack Boost - Critical CSS tests:
projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js#L1
1) specs/critical-css/critical-css.test.js:27:2 › Critical CSS module › No Critical CSS meta information should show on the admin when the module is inactive
Test timeout of 300000ms exceeded.
|
|
Run Jetpack Boost - Critical CSS tests:
tools/e2e-commons/pages/page-actions.js#L43
1) specs/critical-css/critical-css.test.js:27:2 › Critical CSS module › No Critical CSS meta information should show on the admin when the module is inactive
Error: page.goto: Target page, context or browser has been closed
at ../../../../../tools/e2e-commons/pages/page-actions.js:43
41 | } catch ( e ) {
42 | logger.error( `Error navigating to ${ url } (1). Retrying once.\n${ e }` );
> 43 | response = await this.page.goto( url, options );
| ^
44 | }
45 |
46 | return response;
at JetpackBoostPage.goto (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:43:31)
at Function.visit (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/wp-page.js:31:3)
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:29:28
|
|
Run Jetpack Boost - Critical CSS tests:
tools/e2e-commons/pages/page-actions.js#L320
1) specs/critical-css/critical-css.test.js:27:2 › Critical CSS module › No Critical CSS meta information should show on the admin when the module is inactive
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
TimeoutError: locator.waitFor: Timeout 20000ms exceeded.
Call log:
- waiting for locator('#jb-dashboard').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.waitForPage (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:67:16)
at Function.init (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/wp-page.js:18:3)
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:29:28
|
|
Run Jetpack Boost - Critical CSS tests:
tools/e2e-commons/pages/page-actions.js#L320
2) 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-dashboard').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.waitForPage (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:67:16)
at Function.init (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/wp-page.js:18:3)
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:49:28
|
|
Run Jetpack Boost - Critical CSS tests:
tools/e2e-commons/pages/page-actions.js#L320
2) 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-dashboard').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.waitForPage (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:67:16)
at Function.init (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/wp-page.js:18:3)
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:49:28
|
|
Run Jetpack Boost - Critical CSS tests:
tools/e2e-commons/pages/page-actions.js#L320
3) 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 20000ms exceeded.
Call log:
- waiting for locator('#jb-dashboard').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.waitForPage (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:67:16)
at Function.init (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/wp-page.js:18:3)
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:63:28
|
|
Run Jetpack Boost - Critical CSS tests:
tools/e2e-commons/pages/page-actions.js#L320
3) 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 20000ms exceeded.
Call log:
- waiting for locator('#jb-dashboard').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.waitForPage (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:67:16)
at Function.init (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/wp-page.js:18:3)
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:63:28
|
|
Run Jetpack Boost - Critical CSS tests:
projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js#L72
4) 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
|
|
Run Jetpack Boost - Critical CSS tests:
projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js#L72
4) 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
|
|
Run Jetpack Boost - Critical CSS tests:
tools/e2e-commons/pages/page-actions.js#L320
5) 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('#dashboard-widgets-wrap').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 DashboardPage.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:320:17)
at DashboardPage.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:269:21)
at DashboardPage.waitForPage (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:67:16)
at Function.init (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/wp-page.js:18:3)
at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:78:3
|
|
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Run Jetpack Boost - Critical CSS tests
7 failed
specs/critical-css/critical-css.test.js:27:2 › Critical CSS module › No Critical CSS meta information should show on the admin when the module is inactive
specs/critical-css/critical-css.test.js:47:2 › Critical CSS module › Critical CSS should be generated when the module is active
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
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
specs/critical-css/critical-css.test.js:76:2 › Critical CSS module › Critical CSS Admin message should show when the theme is changed
specs/critical-css/critical-css.test.js:101:2 › Critical CSS module › Critical CSS should be generated with an error (advanced recommendations)
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
1 passed (12.0m)
|
Loading