Repository navigation
fix(ios): checks boot the simulator and start the tests once its first-boot work calmed down - #358
Merged
Merged
Conversation
…t-boot work calmed down
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.
A simulator booted by
xcodebuild testspends its first minutes compiling shaders and drawing lock-screen posters. On the runner's three cores that leaves no CPU time to utility-QoS work: the iOS SDK's core queues waited up to 12 s and its tests timed out at random. The step boots the simulator and waits until the mean idle CPU of the last five samples is 25 % or more, three minutes at most, and never fails on its own. Checked on ios-sdk: tests on a freshly booted simulator failed in every run, after this step none failed in three runs.