Enable GCM run in CI #1466
Merged
Enable GCM run in CI #1466
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
|
You know what. We have credits to burn for a bit. Let's turn on the GCM Run here and see what happens! |
tclune
approved these changes
May 18, 2022
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.
I am using this PR to test running the GCM with a MAPL PR. I'm wanting to know the costs, etc for this.
Change 1: Need to use the
compiler-bcsexecutor for GCM runs. Also, I don't need all theinstalldirectories, justbin,etcandlib→ orb v1.2.0Okay. Finally got it to work. In run-credit terms this goes from 1779 → 2134. Now, on top of that are the storage costs. It looks like an Intel run has 678 MiB of storage and a GNU run has 354 MiB. So a total of 1 GiB
Next up, I've set the workplace retention setting in CircleCI to be 1 day instead of 15. Not sure this matters. Still, before I re-triggered the CI, we had 3.7 GB "storage-months" of workspace.