Repository navigation
Merge master into candidate-2.0 - #573
Merged
Merged
Conversation
The browser tests ran every engine one after the other in a single job, so the job got slower with every test added, toward its 10-minute limit. - Each engine now runs in its own job, in parallel, installing only its browser. Tests within a job still run one at a time. - A final job named browser-tests passes only if every engine passed, so the required checks stay the same when engines change. - The minified build, which sites load, runs in every engine; the source, which differs only by minification, runs in Chromium.
Run the browser tests in parallel, one job per engine
Brings in the parallel browser tests (one job per engine).
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.
Brings in the parallel browser tests from master (one job per engine).