You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[CI] Wait for static-file responses and use public Ubuntu mirrors - #4509
Firefox's static-file test waits forever in frame.goto() even though the screenshot shows jQuery rendered and the trace has a complete 200 response. Set the iframe URL and wait for that frame's navigation response instead. Keep checking the same-origin fetch, HTTP status, body, and WordPress response origin.
Ubuntu's Azure mirror took 22–23 minutes to download browser dependencies, leaving two jobs without enough time to build and run tests. Remove that entry from the runner's mirror list. Keep the public Ubuntu archive and security mirrors.
The trunk run shows the navigation timeout. The first PR run passes that test and shows the slow package downloads.
No new skips, extra retries, longer job limits, or runtime changes.
Testing
The static-file test passed five times in each browser with retries disabled. The full Firefox boundary file also passed. The apt step was checked with the runner's mirror list, an absent mirror list, and a real Ubuntu package download. Full CI passed on this update.
No actionable comments were generated in the recent review. 🎉
ℹ️ Recent review info
⚙️ Run configuration
Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: defaults
Review profile: CHILL
Plan: Advanced
Run ID: bf8e626f-12cc-4606-bfbf-f7ea2479981d
📥 Commits
Reviewing files that changed from the base of the PR and between 781626f and af38e4c.
📒 Files selected for processing: 2
.github/actions/prepare-playground/action.yml
AGENTS.md
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 2 remain after this review.
📝 Walkthrough
The static-file navigation test now observes the WordPress iframe’s navigation response and checks its status, body, and origin. The browser dependency setup removes Azure Ubuntu mirror entries when the apt mirror list exists.
Changes: WordPress iframe navigation test
Layer / File(s)
Summary
Observe and validate iframe navigation packages/playground/website/playwright/wordpress-frame/wordpress-frame.spec.ts
The test waits for the matching navigation response in the #wp iframe and checks its status, body, and origin.
Browser dependency apt setup
Layer / File(s)
Summary
Configure apt mirrors for browser dependencies .github/actions/prepare-playground/action.yml, AGENTS.md
The setup removes azure.archive.ubuntu.com entries from /etc/apt/apt-mirrors.txt when the file exists. The testing guidance describes this change and notes that the public Ubuntu archive and security mirrors remain available.
No concrete merge-blocking risk is established in the changed test or mirror configuration.
Pre-merge checks: 5
Check name
Status
Explanation
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Title check
The title clearly and concisely identifies both main changes: waiting for static-file responses and using public Ubuntu mirrors in CI.
Docstring Coverage
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1 files. (2 skipped: 2 unsupported.)
✨ Finishing Touches
🧪 Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
adamziel
changed the title
[Website] Wait for static-file navigation responses in E2E tests
[CI] Wait for static-file responses and use public Ubuntu mirrors
Oct 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses two CI problems:
frame.goto()even though the screenshot shows jQuery rendered and the trace has a complete 200 response. Set the iframe URL and wait for that frame's navigation response instead. Keep checking the same-origin fetch, HTTP status, body, and WordPress response origin.The trunk run shows the navigation timeout. The first PR run passes that test and shows the slow package downloads.
No new skips, extra retries, longer job limits, or runtime changes.
Testing
The static-file test passed five times in each browser with retries disabled. The full Firefox boundary file also passed. The apt step was checked with the runner's mirror list, an absent mirror list, and a real Ubuntu package download. Full CI passed on this update.