Repository navigation
Speed up PHPUnit and avoid E2E setup timeouts - #579
Merged
Merged
Conversation
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 19 minutes. View limit details
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 |
JanJakes
changed the title
JanJakes
force-pushed
the
fix-e2e-browser-setup
branch
3 times, most recently
from
October 28, 2026 15:05
e7329d8 to
a6f85a1
Compare
JanJakes
marked this pull request as ready for review
October 28, 2026 15:08
Run E2E browsers in the official image matching the installed Playwright version. Use Docker Compose for readiness and a composite action for test execution and cleanup, avoiding Ubuntu package downloads. Enable CLI OPcache with a 256 MB cache for WordPress PHPUnit while preserving test diagnostics and file-change checks. Remove unused Buildx setup from the WordPress test workflows. https://playwright.dev/docs/docker#remote-connection
Use a 64 MB JIT buffer for the WordPress and SQLite plugin PHPUnit suites. Keep the existing OPcache and test settings unchanged.
JanJakes
force-pushed
the
fix-e2e-browser-setup
branch
from
October 28, 2026 15:31
a6f85a1 to
84eb24a
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
E2E jobs sometimes exhaust their 20-minute timeout downloading Playwright system packages. This PR removes that setup step and speeds up WordPress PHPUnit.
.envfile early, so the parallel pull uses the same settings as the test environment.Test order, expected failures, error reporting, and job timeouts stay unchanged.
Measured speedups
GitHub-hosted runners vary in speed. During these measurements, the same PHPUnit job took up to about 70% longer on slower runners. To compare fairly, each PHPUnit time is divided by the webpack build time from the same job. The build runs before the tests, and this PR does not change it.
Comparing only runs on the slower runners, PHPUnit took 9m46s on average without OPcache and 7m49s with OPcache and JIT, about 20% faster. The plugin PHPUnit suites take about 10 seconds, too short to show a difference.
These are estimates from 16 runs on the same day, all on WordPress 7.1.4.
All runs