Address WordPress PHPUnit test fails: charset detection, length validation etc #417
end-to-end-tests.yml
on: pull_request
End-to-end Tests
6m 3s
Annotations
4 errors, 1 warning, and 1 notice
|
End-to-end Tests
Process completed with exit code 1.
|
|
[chromium] › query-monitor-plugin.test.js:23:6 › Query Monitor plugin › should activate:
tests/e2e/specs/query-monitor-plugin.test.js#L30
1) [chromium] › query-monitor-plugin.test.js:23:6 › Query Monitor plugin › should activate ───────
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
TimeoutError: locator.click: Timeout 10000ms exceeded.
Call log:
- waiting for locator('a[role="menuitem"][href="#qm-overview"][aria-expanded="false"]')
28 |
29 | // Click on the Query Monitor menu item in the WordPress admin bar.
> 30 | await page.locator('a[role="menuitem"][href="#qm-overview"][aria-expanded="false"]').click();
| ^
31 |
32 | // Wait for the Query Monitor panel to open.
33 | await page.locator( '#query-monitor-main' ).waitFor();
at /home/runner/work/sqlite-database-integration/sqlite-database-integration/tests/e2e/specs/query-monitor-plugin.test.js:30:88
|
|
[chromium] › query-monitor-plugin.test.js:23:6 › Query Monitor plugin › should activate:
tests/e2e/specs/query-monitor-plugin.test.js#L30
1) [chromium] › query-monitor-plugin.test.js:23:6 › Query Monitor plugin › should activate ───────
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
TimeoutError: locator.click: Timeout 10000ms exceeded.
Call log:
- waiting for locator('a[role="menuitem"][href="#qm-overview"][aria-expanded="false"]')
28 |
29 | // Click on the Query Monitor menu item in the WordPress admin bar.
> 30 | await page.locator('a[role="menuitem"][href="#qm-overview"][aria-expanded="false"]').click();
| ^
31 |
32 | // Wait for the Query Monitor panel to open.
33 | await page.locator( '#query-monitor-main' ).waitFor();
at /home/runner/work/sqlite-database-integration/sqlite-database-integration/tests/e2e/specs/query-monitor-plugin.test.js:30:88
|
|
[chromium] › query-monitor-plugin.test.js:23:6 › Query Monitor plugin › should activate:
tests/e2e/specs/query-monitor-plugin.test.js#L30
1) [chromium] › query-monitor-plugin.test.js:23:6 › Query Monitor plugin › should activate ───────
TimeoutError: locator.click: Timeout 10000ms exceeded.
Call log:
- waiting for locator('a[role="menuitem"][href="#qm-overview"][aria-expanded="false"]')
28 |
29 | // Click on the Query Monitor menu item in the WordPress admin bar.
> 30 | await page.locator('a[role="menuitem"][href="#qm-overview"][aria-expanded="false"]').click();
| ^
31 |
32 | // Wait for the Query Monitor panel to open.
33 | await page.locator( '#query-monitor-main' ).waitFor();
at /home/runner/work/sqlite-database-integration/sqlite-database-integration/tests/e2e/specs/query-monitor-plugin.test.js:30:88
|
|
End-to-end Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
🎭 Playwright Run Summary
1 failed
[chromium] › query-monitor-plugin.test.js:23:6 › Query Monitor plugin › should activate ────────
|