Skip to content

Adding a docker-based dev env #97046

Adding a docker-based dev env

Adding a docker-based dev env #97046

Triggered via pull request January 14, 2025 16:19
Status Failure
Total duration 33m 19s
Artifacts 15

e2e-tests.yml

on: pull_request
Determine tests matrix
1m 10s
Determine tests matrix
Matrix: build-projects
Matrix: e2e-tests
Test report
2s
Test report
Slack notification
3m 3s
Slack notification
Fit to window
Zoom out
Zoom in

Annotations

10 errors, 25 warnings, and 15 notices
[chromium] › specs/base/common.test.js:17:1 › Click on the plugins page should navigate to Boost settings page: tools/e2e-commons/pages/page-actions.js#L320
1) [chromium] › specs/base/common.test.js:17:1 › Click on the plugins page should navigate to Boost settings page 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/base/common.test.js:18:2
[chromium] › specs/base/common.test.js:17:1 › Click on the plugins page should navigate to Boost settings page: tools/e2e-commons/pages/page-actions.js#L320
1) [chromium] › specs/base/common.test.js:17:1 › Click on the plugins page should navigate to Boost settings page Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── 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/base/common.test.js:18:2
[chromium] › specs/base/common.test.js:17:1 › Click on the plugins page should navigate to Boost settings page: tools/e2e-commons/pages/page-actions.js#L320
1) [chromium] › specs/base/common.test.js:17:1 › Click on the plugins page should navigate to Boost settings page Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── 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/base/common.test.js:18:2
[chromium] › specs/base/common.test.js:24:1 › Click on the sidebar Boost Jetpack submenu should navigate to Boost settings page: tools/e2e-commons/pages/page-actions.js#L320
2) [chromium] › specs/base/common.test.js:24:1 › Click on the sidebar Boost Jetpack submenu should navigate to Boost settings page 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/base/common.test.js:27:2
[chromium] › specs/base/common.test.js:24:1 › Click on the sidebar Boost Jetpack submenu should navigate to Boost settings page: tools/e2e-commons/pages/page-actions.js#L320
2) [chromium] › specs/base/common.test.js:24:1 › Click on the sidebar Boost Jetpack submenu should navigate to Boost settings page Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── 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/base/common.test.js:27:2
[chromium] › specs/base/common.test.js:24:1 › Click on the sidebar Boost Jetpack submenu should navigate to Boost settings page: tools/e2e-commons/pages/page-actions.js#L320
2) [chromium] › specs/base/common.test.js:24:1 › Click on the sidebar Boost Jetpack submenu should navigate to Boost settings page Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── 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/base/common.test.js:27:2
[chromium] › specs/base/common.test.js:32:1 › Deactivating the plugin should clear Critical CSS and Dismissed Recommendation notice option: tools/e2e-commons/pages/page-actions.js#L320
3) [chromium] › specs/base/common.test.js:32:1 › Deactivating the plugin should clear Critical CSS and Dismissed Recommendation notice option 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/base/common.test.js:41:27
[chromium] › specs/base/common.test.js:32:1 › Deactivating the plugin should clear Critical CSS and Dismissed Recommendation notice option: tools/e2e-commons/pages/page-actions.js#L320
3) [chromium] › specs/base/common.test.js:32:1 › Deactivating the plugin should clear Critical CSS and Dismissed Recommendation notice option 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/base/common.test.js:41:27
[chromium] › specs/base/common.test.js:32:1 › Deactivating the plugin should clear Critical CSS and Dismissed Recommendation notice option: tools/e2e-commons/pages/page-actions.js#L320
3) [chromium] › specs/base/common.test.js:32:1 › Deactivating the plugin should clear Critical CSS and Dismissed Recommendation notice option Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── 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/base/common.test.js:41:27
[chromium] › specs/base/get-started.test.ts:22:2 › Getting started page › User should see the getting started pricing table: tools/e2e-commons/pages/page-actions.js#L320
4) [chromium] › specs/base/get-started.test.ts:22:2 › Getting started page › User should see the getting started pricing table 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/base/get-started.test.ts:13:22
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-search
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-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-social
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 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 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 - 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
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
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 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
Search 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 - 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
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
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
Slack notification
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
Test report
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 (41.9s)
🎭 Playwright Run Summary
1 passed (51.5s)
🎭 Playwright Run Summary
1 passed (1.3m)
🎭 Playwright Run Summary
5 passed (1.3m)
🎭 Playwright Run Summary
8 passed (1.9m)
🎭 Playwright Run Summary
5 passed (1.8m)
🎭 Playwright Run Summary
3 passed (2.0m)
🎭 Playwright Run Summary
13 passed (1.8m)
🎭 Playwright Run Summary
4 passed (1.0m)
🎭 Playwright Run Summary
6 passed (2.3m)
🎭 Playwright Run Summary
3 passed (2.7m)
🎭 Playwright Run Summary
2 passed (3.0m)
🎭 Playwright Run Summary
2 passed (43.3s)
🎭 Playwright Run Summary
2 passed (3.3m)
🎭 Playwright Run Summary
6 failed [chromium] › specs/base/common.test.js:17:1 › Click on the plugins page should navigate to Boost settings page [chromium] › specs/base/common.test.js:24:1 › Click on the sidebar Boost Jetpack submenu should navigate to Boost settings page [chromium] › specs/base/common.test.js:32:1 › Deactivating the plugin should clear Critical CSS and Dismissed Recommendation notice option [chromium] › specs/base/get-started.test.ts:22:2 › Getting started page › User should see the getting started pricing table [chromium] › specs/base/get-started.test.ts:33:2 › Getting started page › User should be able to purchase the premium plan [chromium] › specs/base/get-started.test.ts:49:2 › Getting started page › User should be able to get started with the free plan

Artifacts

Produced during runtime
Name Size
test-output-Jetpack Boost - Base
478 KB
test-output-Jetpack Boost - Concatenate JS and CSS
11.1 KB
test-output-Jetpack Boost - Critical CSS
15.3 KB
test-output-Jetpack Boost - Image CDN
9.65 KB
test-output-Jetpack Boost - Image Guide
7.51 KB
test-output-Jetpack Boost - Modules
24.6 KB
test-output-Jetpack Boost - Page Cache
12.6 KB
test-output-Jetpack connection
13.4 KB
test-output-Jetpack post editor
11.1 KB
test-output-Jetpack post-connection
16.2 KB
test-output-Jetpack pre-connection
7.51 KB
test-output-Jetpack sync
14.7 KB
test-output-Search
24.6 KB
test-output-Social
14.8 KB
test-output-VideoPress
6.95 KB