#62808 closed defect (bug) (fixed)
Puppeteer tests in old branches failing
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | 6.7.2 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Build/Test Tools | Keywords: | has-patch |
Focuses: | Cc: |
Description
Puppeteer-based tests in older branches have started failing recently. This seems to be related to the ubuntu-latest
alias being updated to use ubuntu-24
instead of ubuntu-22
.
Change History (31)
This ticket was mentioned in PR #8128 on WordPress/wordpress-develop by @desrosj.
5 weeks ago
#1
- Keywords has-patch added; needs-patch removed
This ticket was mentioned in PR #8127 on WordPress/wordpress-develop by @desrosj.
5 weeks ago
#2
Trac ticket: https://core.trac.wordpress.org/ticket/62808
This ticket was mentioned in PR #8126 on WordPress/wordpress-develop by @desrosj.
5 weeks ago
#3
Trac ticket: https://core.trac.wordpress.org/ticket/62808.
#4
@
5 weeks ago
This is confirmed to be happening as a result of the ubuntu-24
upgrade.
It seems that some level of updating Puppeteer/Qunit will fix the issue in the 6.0 branch. However, this would require a handful of other compatibility backports for the older branches as well. Those are also hamstrung by the fact that these older branches run Node.js 14.x.
Either update route is not ideal.
@swissspidy shared that he recently fixed this with a GitHub Actions step. I've spot tested that in a few branches, and it fixes the tests for the 4.1, 5.4, and 6.0 branches. The attached PR to trunk
adds an input to the workflow and only runs that new step if true
is passed.
5 weeks ago
#5
Adjusted the input name and added some additional docs about the purpose of the new step.
Trac ticket: https://core.trac.wordpress.org/ticket/62808.