Add PostgreSQL database driver #1184
adamzielAnnotations
12 errors, 2 warnings, and 2 notices
|
WordPress End-to-end Tests / postgresql
Process completed with exit code 1.
|
|
[chromium] › install.test.js:34:6 › WordPress installation process › should install WordPress with pre-existing database credentials:
wordpress/tests/e2e/specs/install.test.js#L40
2) [chromium] › install.test.js:34:6 › WordPress installation process › should install WordPress with pre-existing database credentials
Error: should redirect to the installation page
Timed out 5000ms waiting for expect(locator).toHaveURL(expected)
Locator: locator(':root')
Expected pattern: /wp-admin\/install\.php$/
Received string: "http://localhost:8889/"
Call log:
- should redirect to the installation page with timeout 5000ms
- waiting for locator(':root')
9 × locator resolved to <html lang="en-US">…</html>
- 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/sqlite-database-integration/sqlite-database-integration/wordpress/tests/e2e/specs/install.test.js:40:5
|
|
[chromium] › gutenberg-plugin.test.js:25:6 › Gutenberg plugin › should activate:
wordpress/tests/e2e/specs/gutenberg-plugin.test.js#L0
1) [chromium] › gutenberg-plugin.test.js:25:6 › Gutenberg plugin › should activate ───────────────
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
{
code: 'rest_no_route',
message: 'No route was found matching the URL and request method.',
data: { status: 404 }
}
|
|
[chromium] › gutenberg-plugin.test.js:25:6 › Gutenberg plugin › should activate:
wordpress/tests/e2e/specs/gutenberg-plugin.test.js#L0
1) [chromium] › gutenberg-plugin.test.js:25:6 › Gutenberg plugin › should activate ───────────────
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
{
code: 'rest_no_route',
message: 'No route was found matching the URL and request method.',
data: { status: 404 }
}
|
|
[chromium] › gutenberg-plugin.test.js:25:6 › Gutenberg plugin › should activate:
wordpress/tests/e2e/specs/gutenberg-plugin.test.js#L0
1) [chromium] › gutenberg-plugin.test.js:25:6 › Gutenberg plugin › should activate ───────────────
{
code: 'rest_no_route',
message: 'No route was found matching the URL and request method.',
data: { status: 404 }
}
|
|
WordPress End-to-end Tests / sqlite
Process completed with exit code 1.
|
|
[chromium] › profile/applications-passwords.test.js:19:6 › Manage applications passwords › should correctly create a new application password:
wordpress/tests/e2e/specs/profile/applications-passwords.test.js#L26
3) [chromium] › profile/applications-passwords.test.js:19:6 › Manage applications passwords › should correctly create a new application password
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
TypeError: Cannot read properties of undefined (reading 'name')
24 |
25 | const [ app ] = await applicationPasswords.get();
> 26 | expect( app['name']).toBe( TEST_APPLICATION_NAME );
| ^
27 |
28 | const successMessage = page.getByRole( 'alert' );
29 |
at /home/runner/work/sqlite-database-integration/sqlite-database-integration/wordpress/tests/e2e/specs/profile/applications-passwords.test.js:26:14
|
|
[chromium] › profile/applications-passwords.test.js:19:6 › Manage applications passwords › should correctly create a new application password:
wordpress/tests/e2e/specs/profile/applications-passwords.test.js#L98
3) [chromium] › profile/applications-passwords.test.js:19:6 › Manage applications passwords › should correctly create a new application password
Error: Not logged in
96 |
97 | async create(applicationName = TEST_APPLICATION_NAME) {
> 98 | await this.admin.visitAdminPage( '/profile.php' );
| ^
99 |
100 | const newPasswordField = this.page.getByRole( 'textbox', { name: 'New Application Password Name' } );
101 | await expect( newPasswordField ).toBeVisible();
at Admin.visitAdminPage (/home/runner/work/sqlite-database-integration/sqlite-database-integration/wordpress/node_modules/@wordpress/e2e-test-utils-playwright/src/admin/visit-admin-page.ts:36:9)
at ApplicationPasswords.create (/home/runner/work/sqlite-database-integration/sqlite-database-integration/wordpress/tests/e2e/specs/profile/applications-passwords.test.js:98:3)
at /home/runner/work/sqlite-database-integration/sqlite-database-integration/wordpress/tests/e2e/specs/profile/applications-passwords.test.js:23:3
|
|
[chromium] › install.test.js:34:6 › WordPress installation process › should install WordPress with pre-existing database credentials:
wordpress/tests/e2e/specs/install.test.js#L40
2) [chromium] › install.test.js:34:6 › WordPress installation process › should install WordPress with pre-existing database credentials
Error: should redirect to the installation page
Timed out 5000ms waiting for expect(locator).toHaveURL(expected)
Locator: locator(':root')
Expected pattern: /wp-admin\/install\.php$/
Received string: "http://localhost:8889/"
Call log:
- should redirect to the installation page with timeout 5000ms
- waiting for locator(':root')
9 × locator resolved to <html lang="en-US">…</html>
- 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/sqlite-database-integration/sqlite-database-integration/wordpress/tests/e2e/specs/install.test.js:40:5
|
|
[chromium] › gutenberg-plugin.test.js:25:6 › Gutenberg plugin › should activate:
wordpress/tests/e2e/specs/gutenberg-plugin.test.js#L0
1) [chromium] › gutenberg-plugin.test.js:25:6 › Gutenberg plugin › should activate ───────────────
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
{
code: 'rest_no_route',
message: 'No route was found matching the URL and request method.',
data: { status: 404 }
}
|
|
[chromium] › gutenberg-plugin.test.js:25:6 › Gutenberg plugin › should activate:
wordpress/tests/e2e/specs/gutenberg-plugin.test.js#L0
1) [chromium] › gutenberg-plugin.test.js:25:6 › Gutenberg plugin › should activate ───────────────
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
{
code: 'rest_no_route',
message: 'No route was found matching the URL and request method.',
data: { status: 404 }
}
|
|
[chromium] › gutenberg-plugin.test.js:25:6 › Gutenberg plugin › should activate:
wordpress/tests/e2e/specs/gutenberg-plugin.test.js#L0
1) [chromium] › gutenberg-plugin.test.js:25:6 › Gutenberg plugin › should activate ───────────────
{
code: 'rest_no_route',
message: 'No route was found matching the URL and request method.',
data: { status: 404 }
}
|
|
WordPress End-to-end Tests / postgresql
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 16th, 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/
|
|
WordPress End-to-end Tests / sqlite
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 16th, 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] › gutenberg-plugin.test.js:25:6 › Gutenberg plugin › should activate ────────────────
1 flaky
[chromium] › install.test.js:34:6 › WordPress installation process › should install WordPress with pre-existing database credentials
21 passed (1.1m)
|
|
🎭 Playwright Run Summary
1 failed
[chromium] › gutenberg-plugin.test.js:25:6 › Gutenberg plugin › should activate ────────────────
2 flaky
[chromium] › install.test.js:34:6 › WordPress installation process › should install WordPress with pre-existing database credentials
[chromium] › profile/applications-passwords.test.js:19:6 › Manage applications passwords › should correctly create a new application password
20 passed (52.1s)
|