Skip to content

Add admin notice warning when installed plugins are not tested with the current WordPress version #51224

Add admin notice warning when installed plugins are not tested with the current WordPress version

Add admin notice warning when installed plugins are not tested with the current WordPress version #51224

Triggered via pull request February 24, 2026 13:20
Status Failure
Total duration 7m 10s
Artifacts 2

end-to-end-tests.yml

on: pull_request
Matrix: e2e-tests
Slack Notifications  /  Prepare notifications
Slack Notifications / Prepare notifications
Slack Notifications  /  Cancelled notifications
Slack Notifications / Cancelled notifications
Slack Notifications  /  Failure notifications
Slack Notifications / Failure notifications
Slack Notifications  /  Fixed notifications
Slack Notifications / Fixed notifications
Slack Notifications  /  Success notifications
Slack Notifications / Success notifications
Failed workflow tasks
0s
Failed workflow tasks
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 2 notices
E2E Tests / SCRIPT_DEBUG disabled
Process completed with exit code 1.
[chromium] › tests/e2e/specs/install.test.js:34:6 › WordPress installation process › should install WordPress with pre-existing database credentials: tests/e2e/specs/install.test.js#L40
2) [chromium] › tests/e2e/specs/install.test.js:34:6 › WordPress installation process › should install WordPress with pre-existing database credentials Error: should redirect to the installation page expect(page).toHaveURL(expected) failed Expected pattern: /wp-admin\/install\.php$/ Received string: "http://localhost:8889/" Timeout: 5000ms Call log: - should redirect to the installation page with timeout 5000ms 9 × unexpected value "http://localhost:8889/" 38 | page, 39 | 'should redirect to the installation page' > 40 | ).toHaveURL( /wp-admin\/install\.php$/ ); | ^ 41 | 42 | await expect( 43 | page.getByText( /WordPress database error/ ), at /home/runner/work/wordpress-develop/wordpress-develop/tests/e2e/specs/install.test.js:40:5
[chromium] › tests/e2e/specs/cache-control-headers-directives.test.js:49:6 › Cache Control header directives › Correct directives present in cache control header when not logged in on 404 page.: tests/e2e/specs/cache-control-headers-directives.test.js#L63
1) [chromium] › tests/e2e/specs/cache-control-headers-directives.test.js:49:6 › Cache Control header directives › Correct directives present in cache control header when not logged in on 404 page. Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 404 Received: 200 61 | await context.close(); 62 | > 63 | expect( responseStatus ).toBe( 404 ); | ^ 64 | expect( responseHeaders[ 'cache-control' ] ).toContain( 'no-cache' ); 65 | expect( responseHeaders[ 'cache-control' ] ).toContain( 'no-store' ); 66 | expect( responseHeaders[ 'cache-control' ] ).toContain( 'private' ); at /home/runner/work/wordpress-develop/wordpress-develop/tests/e2e/specs/cache-control-headers-directives.test.js:63:28
[chromium] › tests/e2e/specs/cache-control-headers-directives.test.js:49:6 › Cache Control header directives › Correct directives present in cache control header when not logged in on 404 page.: tests/e2e/specs/cache-control-headers-directives.test.js#L63
1) [chromium] › tests/e2e/specs/cache-control-headers-directives.test.js:49:6 › Cache Control header directives › Correct directives present in cache control header when not logged in on 404 page. Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 404 Received: 200 61 | await context.close(); 62 | > 63 | expect( responseStatus ).toBe( 404 ); | ^ 64 | expect( responseHeaders[ 'cache-control' ] ).toContain( 'no-cache' ); 65 | expect( responseHeaders[ 'cache-control' ] ).toContain( 'no-store' ); 66 | expect( responseHeaders[ 'cache-control' ] ).toContain( 'private' ); at /home/runner/work/wordpress-develop/wordpress-develop/tests/e2e/specs/cache-control-headers-directives.test.js:63:28
[chromium] › tests/e2e/specs/cache-control-headers-directives.test.js:49:6 › Cache Control header directives › Correct directives present in cache control header when not logged in on 404 page.: tests/e2e/specs/cache-control-headers-directives.test.js#L63
1) [chromium] › tests/e2e/specs/cache-control-headers-directives.test.js:49:6 › Cache Control header directives › Correct directives present in cache control header when not logged in on 404 page. Error: expect(received).toBe(expected) // Object.is equality Expected: 404 Received: 200 61 | await context.close(); 62 | > 63 | expect( responseStatus ).toBe( 404 ); | ^ 64 | expect( responseHeaders[ 'cache-control' ] ).toContain( 'no-cache' ); 65 | expect( responseHeaders[ 'cache-control' ] ).toContain( 'no-store' ); 66 | expect( responseHeaders[ 'cache-control' ] ).toContain( 'private' ); at /home/runner/work/wordpress-develop/wordpress-develop/tests/e2e/specs/cache-control-headers-directives.test.js:63:28
E2E Tests / SCRIPT_DEBUG enabled
Process completed with exit code 1.
[chromium] › tests/e2e/specs/media-upload.test.js:11:5 › Test dismissing failed upload works correctly: tests/e2e/specs/media-upload.test.js#L14
2) [chromium] › tests/e2e/specs/media-upload.test.js:11:5 › Test dismissing failed upload works correctly Error: Not logged in 12 | // Log in before visiting admin page. 13 | await requestUtils.login(); > 14 | await admin.visitAdminPage( '/media-new.php' ); | ^ 15 | 16 | // It takes a moment for the multi-file uploader to become available. 17 | await page.waitForLoadState('load'); at Admin.visitAdminPage (/home/runner/work/wordpress-develop/wordpress-develop/node_modules/@wordpress/e2e-test-utils-playwright/src/admin/visit-admin-page.ts:36:9) at /home/runner/work/wordpress-develop/wordpress-develop/tests/e2e/specs/media-upload.test.js:14:2
[chromium] › tests/e2e/specs/cache-control-headers-directives.test.js:49:6 › Cache Control header directives › Correct directives present in cache control header when not logged in on 404 page.: tests/e2e/specs/cache-control-headers-directives.test.js#L63
1) [chromium] › tests/e2e/specs/cache-control-headers-directives.test.js:49:6 › Cache Control header directives › Correct directives present in cache control header when not logged in on 404 page. Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 404 Received: 200 61 | await context.close(); 62 | > 63 | expect( responseStatus ).toBe( 404 ); | ^ 64 | expect( responseHeaders[ 'cache-control' ] ).toContain( 'no-cache' ); 65 | expect( responseHeaders[ 'cache-control' ] ).toContain( 'no-store' ); 66 | expect( responseHeaders[ 'cache-control' ] ).toContain( 'private' ); at /home/runner/work/wordpress-develop/wordpress-develop/tests/e2e/specs/cache-control-headers-directives.test.js:63:28
[chromium] › tests/e2e/specs/cache-control-headers-directives.test.js:49:6 › Cache Control header directives › Correct directives present in cache control header when not logged in on 404 page.: tests/e2e/specs/cache-control-headers-directives.test.js#L63
1) [chromium] › tests/e2e/specs/cache-control-headers-directives.test.js:49:6 › Cache Control header directives › Correct directives present in cache control header when not logged in on 404 page. Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 404 Received: 200 61 | await context.close(); 62 | > 63 | expect( responseStatus ).toBe( 404 ); | ^ 64 | expect( responseHeaders[ 'cache-control' ] ).toContain( 'no-cache' ); 65 | expect( responseHeaders[ 'cache-control' ] ).toContain( 'no-store' ); 66 | expect( responseHeaders[ 'cache-control' ] ).toContain( 'private' ); at /home/runner/work/wordpress-develop/wordpress-develop/tests/e2e/specs/cache-control-headers-directives.test.js:63:28
[chromium] › tests/e2e/specs/cache-control-headers-directives.test.js:49:6 › Cache Control header directives › Correct directives present in cache control header when not logged in on 404 page.: tests/e2e/specs/cache-control-headers-directives.test.js#L63
1) [chromium] › tests/e2e/specs/cache-control-headers-directives.test.js:49:6 › Cache Control header directives › Correct directives present in cache control header when not logged in on 404 page. Error: expect(received).toBe(expected) // Object.is equality Expected: 404 Received: 200 61 | await context.close(); 62 | > 63 | expect( responseStatus ).toBe( 404 ); | ^ 64 | expect( responseHeaders[ 'cache-control' ] ).toContain( 'no-cache' ); 65 | expect( responseHeaders[ 'cache-control' ] ).toContain( 'no-store' ); 66 | expect( responseHeaders[ 'cache-control' ] ).toContain( 'private' ); at /home/runner/work/wordpress-develop/wordpress-develop/tests/e2e/specs/cache-control-headers-directives.test.js:63:28
🎭 Playwright Run Summary
1 failed [chromium] › tests/e2e/specs/cache-control-headers-directives.test.js:49:6 › Cache Control header directives › Correct directives present in cache control header when not logged in on 404 page. 1 flaky [chromium] › tests/e2e/specs/install.test.js:34:6 › WordPress installation process › should install WordPress with pre-existing database credentials 23 passed (57.3s)
🎭 Playwright Run Summary
1 failed [chromium] › tests/e2e/specs/cache-control-headers-directives.test.js:49:6 › Cache Control header directives › Correct directives present in cache control header when not logged in on 404 page. 1 flaky [chromium] › tests/e2e/specs/media-upload.test.js:11:5 › Test dismissing failed upload works correctly 23 passed (1.1m)

Artifacts

Produced during runtime
Name Size Digest
failures-artifacts-22352631354
778 KB
sha256:59e7619b7bdbf1050f8af515e52e6dfd45a2289a83812e78f27f4a2e3aa0a022
failures-artifacts-SCRIPT_DEBUG-22352631354
599 KB
sha256:7ec00c69b70b533bbdfc2fd7983eb5337871c4ddfe11223b9dd90bfcf5280f3d