Open
Conversation
Removed options to ensure devices found and force quit simulator in the test configuration ... looking for reliable ci builds
krugerk
changed the title
Collaborator
|
Based on the failing test status, I assume this remains a work in progress. |
Contributor
Author
The culprit remains unclear to me. |
Collaborator
|
Did you learn anything here in terms of what does/does not mitigate the issue? |
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
2 participants
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
The fastlane-tests GitHub workflow uses the macOS 15. Since #678 the workflow has failed often, timing out while apparently waiting for the simulator to start. May the combination macOS 26 + iOS 26 simulator run better.
Validation
checking results in GitHub actions