[wasm] Codespaces need more disc to succeed building on container creation #99803
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
…rkspaces/.codespaces".
…fter codespaces setup when occupied disc space drops.
… VM before the command finishes.
dotnet-issue-labeler
bot
added
the
needs-area-label
|
Tagging subscribers to 'arch-wasm': @lewing |
akoeplinger
approved these changes
Mar 16, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Temporary fix for #99690. There are no machines of same number of cores and RAM as the currently lowest required one, so as the result of this PR we will be able to use pre-built codespaces for wasm / wasm MT only with 8-core machine. The PR can be most probably reverted when codespaces will fix the issue with excessive size occupancy for
codespaces/shared/editors/jetbrains.https://github.com/orgs/community/discussions/57767