Skip to content
WordPress End-to-end Tests

[AST] Support INSERT/REPLACE without INTO and MySQL priority modifiers #401

Sign in to view logs

[AST] Support INSERT/REPLACE without INTO and MySQL priority modifiers

[AST] Support INSERT/REPLACE without INTO and MySQL priority modifiers #401

Triggered via pull request March 30, 2026 23:53
@wp-fusewp-fuse
synchronize #343
wp-fuse:feature/pr-2-insert-without-into
Status Success
Total duration 5m 39s
Artifacts –

wp-tests-end-to-end.yml

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

Annotations

1 error, 1 warning, and 1 notice
[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
1 flaky [chromium] › install.test.js:34:6 › WordPress installation process › should install WordPress with pre-existing database credentials 22 passed (47.0s)