Repository navigation
Run the macOS tests one file at a time in CI - #30
Merged
Merged
Conversation
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
1 participant
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.
The macOS job failed or hung in about three of the last eight runs, each time in a different browser or ffmpeg test: a page load, clip frame extraction, a render. Linux and Windows always pass, and the same tests pass locally in seconds. The macOS runners have three cores, and Node runs two test files at once there. Two files rendering at the same time seem to starve Chrome and ffmpeg.
macOS now runs one test file at a time. The job should take a few minutes longer. Linux and Windows are unchanged.