Protect Meets Core: Home Page Scan Report Data Adjustments #95451
natewellere2e-tests.yml
on: pull_request
Annotations
14 errors, 24 warnings, and 15 notices
|
specs/search-configure.test.js:55:2 › Search Configure › Can configure search overlay:
tools/e2e-commons/helpers/partner-provisioning.js#L30
1) specs/search-configure.test.js:55:2 › Search Configure › Can configure search overlay ─────────
Error: Jetpack Start provisioning command failed.
at ../../../../../tools/e2e-commons/helpers/partner-provisioning.js:30
28 | response = execSyncShellCommand( cmd );
29 | } catch {
> 30 | throw new Error( `Jetpack Start provisioning command failed.` );
| ^
31 | }
32 |
33 | const json = JSON.parse( response );
at provisionJetpackStartConnection (/home/runner/work/jetpack/jetpack/tools/e2e-commons/helpers/partner-provisioning.js:30:9)
at connect (/home/runner/work/jetpack/jetpack/tools/e2e-commons/env/prerequisites.js:142:3)
at ensureConnectedState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/env/prerequisites.js:125:3)
at buildPrerequisites (/home/runner/work/jetpack/jetpack/tools/e2e-commons/env/prerequisites.js:99:5)
at Object.build (/home/runner/work/jetpack/jetpack/tools/e2e-commons/env/prerequisites.js:68:4)
at /home/runner/work/jetpack/jetpack/projects/plugins/search/tests/e2e/specs/search-configure.test.js:22:3
|
|
specs/search-configure.test.js:55:2 › Search Configure › Can configure search overlay:
tools/e2e-commons/pages/page-actions.js#L43
1) specs/search-configure.test.js:55:2 › Search Configure › Can configure search overlay ─────────
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 JetpackMyPlanPage.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 syncJetpackPlanData (/home/runner/work/jetpack/jetpack/tools/e2e-commons/flows/jetpack-connect.js:73:21)
at ensurePlan (/home/runner/work/jetpack/jetpack/tools/e2e-commons/env/prerequisites.js:202:2)
at buildPrerequisites (/home/runner/work/jetpack/jetpack/tools/e2e-commons/env/prerequisites.js:99:5)
at Object.build (/home/runner/work/jetpack/jetpack/tools/e2e-commons/env/prerequisites.js:68:4)
at /home/runner/work/jetpack/jetpack/projects/plugins/search/tests/e2e/specs/search-configure.test.js:22:3
|
|
specs/search-dashboard.test.js:37:2 › Search Dashboard › Can manage search module and instant search.:
tools/e2e-commons/pages/page-actions.js#L320
2) specs/search-dashboard.test.js:37:2 › Search Dashboard › Can manage search module and instant search.
TimeoutError: locator.waitFor: Timeout 30000ms exceeded.
Call log:
- waiting for locator('.jp-search-dashboard-top__title').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 SearchDashboard.waitForElementState (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:320:17)
at SearchDashboard.waitForElementToBeVisible (/home/runner/work/jetpack/jetpack/tools/e2e-commons/pages/page-actions.js:269:21)
at SearchDashboard.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/search/tests/e2e/specs/search-dashboard.test.js:33:21
|
|
Search e2e tests
Process completed with exit code 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:
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.
|
|
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:
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
|
|
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:
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
|
|
specs/critical-css/critical-css.test.js:47:2 › Critical CSS module › Critical CSS should be generated when the module is active:
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
|
|
specs/critical-css/critical-css.test.js:47:2 › Critical CSS module › Critical CSS should be generated when the module is active:
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
|
|
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:
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
|
|
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:
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
|
|
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:
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
|
|
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:
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
|
|
specs/critical-css/critical-css.test.js:76:2 › Critical CSS module › Critical CSS Admin message should show when the theme is changed:
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
|
|
Determine tests matrix
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
E2E: Build jetpack-videopress
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
E2E: Build jetpack-boost
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
E2E: Build jetpack-social
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
E2E: Build jetpack-sync
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
E2E: Build jetpack-core
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
E2E: Build jetpack-search
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Jetpack pre-connection e2e tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Jetpack Boost - Image Guide e2e tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
VideoPress e2e tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Jetpack Boost - Image CDN e2e tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Jetpack post editor e2e tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Jetpack Boost - Concatenate JS and CSS e2e tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Jetpack Boost - Page Cache e2e tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Jetpack sync e2e tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Search e2e tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Jetpack Boost - Modules e2e tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Jetpack connection e2e tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Social e2e tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Jetpack post-connection e2e tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Jetpack Boost - Base e2e tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Jetpack Boost - Critical CSS e2e tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Test report
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Slack notification
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
🎭 Playwright Run Summary
1 passed (39.8s)
|
|
🎭 Playwright Run Summary
2 passed (41.5s)
|
|
🎭 Playwright Run Summary
1 passed (40.4s)
|
|
🎭 Playwright Run Summary
4 passed (54.8s)
|
|
🎭 Playwright Run Summary
1 passed (1.0m)
|
|
🎭 Playwright Run Summary
5 passed (1.1m)
|
|
🎭 Playwright Run Summary
5 passed (1.3m)
|
|
🎭 Playwright Run Summary
3 passed (1.5m)
|
|
🎭 Playwright Run Summary
2 failed
specs/search-configure.test.js:55:2 › Search Configure › Can configure search overlay ──────────
specs/search-dashboard.test.js:37:2 › Search Dashboard › Can manage search module and instant search.
4 passed (2.2m)
|
|
🎭 Playwright Run Summary
13 passed (2.1m)
|
|
🎭 Playwright Run Summary
2 passed (2.2m)
|
|
🎭 Playwright Run Summary
3 passed (2.6m)
|
|
🎭 Playwright Run Summary
2 passed (2.6m)
|
|
🎭 Playwright Run Summary
6 passed (2.8m)
|
|
🎭 Playwright Run Summary
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)
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
test-output-Jetpack Boost - Base
|
15.8 KB |
|
|
test-output-Jetpack Boost - Concatenate JS and CSS
|
11.4 KB |
|
|
test-output-Jetpack Boost - Critical CSS
|
98.2 KB |
|
|
test-output-Jetpack Boost - Image CDN
|
9.98 KB |
|
|
test-output-Jetpack Boost - Image Guide
|
7.89 KB |
|
|
test-output-Jetpack Boost - Modules
|
23.3 KB |
|
|
test-output-Jetpack Boost - Page Cache
|
12.9 KB |
|
|
test-output-Jetpack connection
|
11.9 KB |
|
|
test-output-Jetpack post editor
|
9.55 KB |
|
|
test-output-Jetpack post-connection
|
15.5 KB |
|
|
test-output-Jetpack pre-connection
|
7.06 KB |
|
|
test-output-Jetpack sync
|
13.5 KB |
|
|
test-output-Search
|
2.02 MB |
|
|
test-output-Social
|
14.4 KB |
|
|
test-output-VideoPress
|
6.96 KB |
|