[Experimental] Transition to macos 13 and Xcode 14.3 #1797
Closed
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
maratal
changed the title
maratal
changed the title
|
This work is done in #1801 |
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.
See #1801
Contains work from #1783
The reason why tests stop failing after
ttltime has been increased in #1783 remains unknown, but I think it's due to different hardware Github uses for its beta servers where low performance can affect how test executes with smaller timeout values. So I would run those workflows again when macOS 13 (by reverting explicit switch to macos 13 3bb354d) will become the latest available os and see how tests will behave there.The test "test__081..." was modified to reflect what it says in the title and to be similar to the "test__080..." which has similar title and conditions. But I left the previous version of the "test__081..." with the "skip" prefix and created an issue for dealing with it later, since I think that behavior of this test is rather confusing and is in contradiction to its own title.