Workflows: Prime a WP install and skip install for the actual test run. #256
Conversation
This file contains 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
|
Previously: 1m 53s This equates to a workflow run time reduction of ~43%. |
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.
Pull Request
What changed?
The PHPUnit test workflow now performs a dummy run to prime the WordPress install for tests.
When this completes, the actual test run is performed, with the
WP_TESTS_SKIP_INSTALLenvironment variable set to1.Why did it change?
Since many of the tests must run in separate processes, the WordPress installation occurs in each process. This is an unnecessary delay. By priming the install and explicitly disabling the install attempts in the actual runs, this delay is removed.
Also, it's nice to have nice things.
Did you fix any specific issues?
Fixes #257
CERTIFICATION
By opening this pull request, I do agree to abide by the Code of Conduct and be bound by the terms of the Contribution Guidelines in effect on the date and time of my contribution as proven by the revision information in GitHub.