Skip to content

Weekly Testing Digest workflow failing #177

Closed

Description

@nikunj8866

Description

The scheduled Weekly Testing Digest workflow failed this week, so the digest was not posted to the Make/Test blog.

Failed run

https://github.com/WordPress/test-handbook/actions/runs/27542061411

cc: @juanmaguitar @3kori

Activity

  1. 3kori commented on Jun 20, 2026

    @3kori
    Collaborator

    The issue is a mismatch between the Playwright version and the expected browser version, as pointed out by @ozgursar.

    Each version of Playwright needs specific versions of browser binaries to operate. You will need to use the Playwright CLI to install these browsers.
    With every release, Playwright updates the versions of the browsers it supports, so that the latest Playwright would support the latest browsers at any moment. It means that every time you update Playwright, you might need to re-run the install CLI command.

    Playwright docs

    Our cache currently contains v1223 browser and Playwright expects v1228 browser. I've been looking for a way to check whether browser support has changed, but I haven't found one yet. I am now leaning towards two possible approaches:

    Remove the cache step

    Just like the heading says, we can remove the cache step, Install Playwright system deps step and the conditionals. This means that the workflow will have to download the browser for each run. Personally, I don't have an issue with this since this runs once every week.

    Flushing cache every two weeks

    Using a similar method as the one in WordPress-Develop, where we can clear cache after two weeks. This will prevent the cache from going stale, but an issue might still occur if Playwright releases a new version a day after clearing and saving the cache.

    I would like to hear your thoughts on this @juanmaguitar

  2. 3kori commented on Jun 20, 2026

    @3kori
    Collaborator

    I have deleted the current cache to make way for Monday's run before we reach a consensus on a fix for the issue.

  3. ozgursar commented on Jun 22, 2026

    @ozgursar
    Collaborator

    Thanks for working on this @3kori. As this workflow runs only once per week, I think removing the cache stop is better.

  4. juanmaguitar commented on Jun 22, 2026

    @juanmaguitar
    Collaborator

    I agree. Removing the cache makes sense 👍
    Let's see how it goes later today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions