#62843 closed defect (bug) (fixed)
Update Playwright to the latest version
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 6.7.2 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Build/Test Tools | Keywords: | has-patch |
Focuses: | Cc: |
Description
The E2E and Performance testing workflows have started failing recently for older branches using Playwright (6.5 and earlier). This seems to be due to the change for ubuntu-latest to now point to ubuntu-24 instead of ubuntu-22.
Updating Playwright to the latest version seems to fix the issue with no obvious side effects. Since this only effects build tooling and not the built software, this seems like a reasonable change to make in somewhat older branches.
To avoid having trunk
running an older version than 6.5 and earlier, Playwright should just be updated in all branches making use of the dependency (6.4-6.8 & trunk
).
Change History (17)
This ticket was mentioned in PR #8164 on WordPress/wordpress-develop by @desrosj.
4 weeks ago
#1
This ticket was mentioned in PR #8163 on WordPress/wordpress-develop by @desrosj.
4 weeks ago
#2
The E2E and Performance testing workflows have started failing recently for branches using Playwright. This seems to be due to the change for ubuntu-latest
to now point to ubuntu-24
instead of ubuntu-22
.
Updating Playwright to the latest version seems to fix the issue with no obvious side effects. Since this only effects build tooling and not the built software, this seems like a reasonable change to make in a somewhat older branch.
See also #8169, #8164, #8164, #8171.
Trac ticket: https://core.trac.wordpress.org/ticket/62843
This ticket was mentioned in PR #8169 on WordPress/wordpress-develop by @desrosj.
4 weeks ago
#3
The E2E and Performance testing workflows have started failing recently for branches using Playwright. This seems to be due to the change for ubuntu-latest
to now point to ubuntu-24
instead of ubuntu-22
.
Updating Playwright to the latest version seems to fix the issue with no obvious side effects. Since this only effects build tooling and not the built software, this seems like a reasonable change to make in a somewhat older branch.
This updates Playwright to the latest version in trunk
so that older versions are not more up to date than trunk
.
See also #8163, #8164, #8170, #8171.
Trac ticket: https://core.trac.wordpress.org/ticket/62843
This ticket was mentioned in PR #8170 on WordPress/wordpress-develop by @desrosj.
4 weeks ago
#4
The E2E and Performance testing workflows have started failing recently for branches using Playwright. This seems to be due to the change for ubuntu-latest
to now point to ubuntu-24
instead of ubuntu-22
.
Updating Playwright to the latest version seems to fix the issue with no obvious side effects. Since this only effects build tooling and not the built software, this seems like a reasonable change to make in a somewhat older branch.
This updates the 6.6 branch so that older versions are not more up to date.
Trac ticket: https://core.trac.wordpress.org/ticket/62843
This ticket was mentioned in PR #8171 on WordPress/wordpress-develop by @desrosj.
4 weeks ago
#5
The E2E and Performance testing workflows have started failing recently for branches using Playwright. This seems to be due to the change for ubuntu-latest
to now point to ubuntu-24
instead of ubuntu-22
.
Updating Playwright to the latest version seems to fix the issue with no obvious side effects. Since this only effects build tooling and not the built software, this seems like a reasonable change to make in a somewhat older branch.
This updates the 6.7 branch so that older versions are not more up to date.
Trac ticket: https://core.trac.wordpress.org/ticket/62843
#11
@
4 weeks ago
- Owner set to desrosj
- Resolution set to fixed
- Status changed from new to closed
In 59686:
The E2E and Performance testing workflows have started failing recently for branches using Playwright. This seems to be due to the change for
ubuntu-latest
to now point toubuntu-24
instead ofubuntu-22
.Updating Playwright to the latest version seems to fix the issue with no obvious side effects. Since this only effects build tooling and not the built software, this seems like a reasonable change to make in a somewhat older branch.
See also #8169, #8163, #8170, #8171.
Trac ticket: https://core.trac.wordpress.org/ticket/62843