Open
Conversation
Collaborator
|
do we need to build userdata in GitHub CI? although it doesn't sound quite right, could we skip the userdata images in |
Contributor
Author
|
Running locally should always be the same as running CI. The only difference that is ok is the infrastructure that actually runs the test/build. |
This reverts commit a85524f.
d2f1340 to
9f056e6
Compare
Collaborator
|
Totally understand. Just that producing artifacts of 5.28 GB is huge. Plus they get uploaded to GitLab LFS when using [upload]. |
Collaborator
|
can you merge this? I will try to come up with something after. current sizes: |
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.
Also reduce memory required from 90GB -> 1.8GB