WordPress.org
Get WordPress

Make WordPress Core

Opened 8 weeks ago

Last modified 8 weeks ago

#63024 new defect (bug)

Address the errors that cause annotations in the e2e test workflows

Reported by: johnbillion's profile johnbillion Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version:
Component: Build/Test Tools Keywords: needs-testing
Focuses: Cc:

Description

The end to end tests workflow on GitHub Actions produces errors that are output as annotations on the workflow runs but don't cause them to fail. These should be investigated and fixed as necessary.

Here's an example run: ​https://github.com/WordPress/wordpress-develop/actions/runs/13549269287

[chromium] › install.test.js:34:6 › WordPress installation process › should install WordPress with pre-existing database credentials: 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/wordpress-develop/wordpress-develop/tests/e2e/specs/install.test.js:40:5

Change History (1)

#1 @swissspidy
8 weeks ago

Yeah looks like they're flaky and only pass on the third attempt or so, hence no failure.

Good thing is the debug artefacts are uploaded for easier debugging.

Note: See TracTickets for help on using tickets.