Use Ubuntu jammy instead of noble for now
#140
Merged
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
|
Will need to update branch protection to expect jammy jobs to succeed, not noble. |
0xTim
approved these changes
Oct 11, 2024
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.
Swift 6 has had significant build time regressions which hopefully will become less significant by Swift 6.0.3.
Regardless, even on Swift 5.10, Swift noble seems to have build time / memory-usage regressions.
We've also had reports of similar OOM problems by Heorku users on Discord.
Swift build times are already not good, and there is a chance of running out of memory which will be confusing to users.
Let's not risk it and just use Swift jammy for now.