Repository navigation
Repair wp/5.7 branch Actions: Fix theme-activation navigation race in activate-theme.js - #84780
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
50ca1dd to
ad8ebce
Compare
ad8ebce to
b361c21
Compare
b361c21 to
087768b
Compare
Part of #82936.
What?
In the Puppeteer
activateTheme()helper (packages/e2e-test-utils/src/activate-theme.js), wait for the navigation triggered by clicking "Activate" before checking that the theme is active, and give that check a 45s timeout.Why?
Clicking "Activate" loads a new page (theme switch, then a redirect back to
themes.php). Without waiting for it, the singlewaitForSelector()call has to cover that whole round trip within Puppeteer's default 30s and can time out:This race repeatedly failed CI on
wp/6.5andwp/6.4, where #83002 and #83686 fix it. It has not failed on this branch yet, so this is included proactively to keep the helper identical across branches.Use of AI Tools
This PR was created by Claude Code under my supervision. All code should be treated as AI-produced and not yet reviewed by a human until this PR is marked Ready for Review.
🤖 Generated with Claude Code