Opened 25 hours ago
Last modified 21 hours ago
#66744 new defect (bug)
Build/Test Tools: Release-day Installation and Upgrade Tests fail before the new zip reaches every download server
| Reported by: | adrianmoldovanwp | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Awaiting Review |
| Component: | Build/Test Tools | Version: | |
| Severity: | normal | Keywords: | has-patch |
| Cc: | Focuses: | tests |
Description
WordPress.org dispatches the Installation Tests and Upgrade Tests workflows seconds after it uploads a release zip. Every job downloads the zip itself, and the jobs fail:
Downloading update from https://wordpress.org/wordpress-5.0.32.zip... Error: Download failed.
On 2026-11-18:
- 5.6.24: Upgrade Tests failed 60 of 75 jobs (run), and Installation Tests failed 42 jobs in each of two attempts (run).
- 5.0.32: Upgrade Tests failed attempts 1–4 (run), and Installation Tests failed attempts 1–3 (run). Both passed about 21 minutes after the upload.
Installation Tests already retry the download, but for only 30 seconds. The Upgrade Tests step does not retry. The error does not show the HTTP status.
- Proposed fix: in each workflow, one job downloads the zip with WP-CLI, retries for up to 45 minutes, requires a verified md5, and gives the zip to every job. Each run downloads once instead of up to 75 times, and WP-CLI shows the HTTP status of each failed try. Runs for
latest,nightlyanddevelopdo not change.
Other options considered:
- Longer retry in each job: up to 75 jobs per run each wait up to 20 minutes.
- Delay the dispatch, or add a job that only waits for the zip: one good download does not mean every server has the zip.
- One job downloads with curl and shares the zip.
- One job fills the WP-CLI cache and shares it: this depends on WP-CLI's internal cache layout, and a cache miss fails silently.
Change History (1)
This ticket was mentioned in PR #16106 on WordPress/wordpress-develop by @adrianmoldovanwp.
21 hours ago
#1
- Keywords has-patch added
Note:
See TracTickets
for help on using tickets.
WordPress.org starts the Installation Tests and Upgrade Tests runs right after it uploads a release. For about 20 minutes, some download servers do not have the new zip yet, and every job that downloads it can fail.
Now one job in each workflow downloads the zip with WP-CLI. It tries every 60 seconds for up to 45 minutes and accepts the zip only when WP-CLI verifies its md5 hash. The test jobs then take the zip from that job instead of downloading it again. WP-CLI does not stop a downgrade when it updates from a zip, so Upgrade Tests skip the update when
wp core update --minoralready reached or passed the target. If the download job fails, the test jobs are skipped and the run reports a failure.Runs for
latest,nightly,trunkanddevelopkeep the current steps. The start versions andwp core update --minorin Upgrade Tests also keep their current download.Testing Instructions
These jobs only run in
WordPress/wordpress-develop. To test on a fork, change thegithub.repositorychecks to the fork's name.5.0.32. One job logsmd5 hash verified, and all test jobs pass.9.9.9. The download job fails after 45 minutes, and the test jobs are skipped.latestandnightly, and Upgrade Tests withlatest. No zip is shared, and the test jobs download WordPress as before.6.4.3. The 6.4 jobs logis not older than 6.4.3, so there is nothing to upgrade.5.9and6.0. The post-install smoke check passes.Test runs on a fork
unzip, so the smoke check passes (#66403).wp core updatedownloads WordPress as before.wp core update --minoralready passed the target.The 9.9.9 runs used a 2-minute wait instead of 45 minutes.
Use of AI Tools
AI assistance: Yes