Skip to content

Translate MySQL CONVERT() expressions to SQLite #418

Translate MySQL CONVERT() expressions to SQLite

Translate MySQL CONVERT() expressions to SQLite #418

Triggered via pull request April 7, 2026 14:59
@JanJakesJanJakes
synchronize #356
convert-fix
Status Success
Total duration 6m 22s
Artifacts

wp-tests-end-to-end.yml

on: pull_request
WordPress End-to-end Tests
6m 18s
WordPress End-to-end Tests
Fit to window
Zoom out
Zoom in

Annotations

3 errors, 1 warning, and 1 notice
[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
2) [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
2) [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
1) [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
WordPress 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
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 21 passed (53.1s)