-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optimize circleci machine sizes and parallelism #3095
Merged
algojohnlee
merged 9 commits into
algorand:master
from
algojack:optimize-circleci-upload-stage
Oct 19, 2021
Merged
Optimize circleci machine sizes and parallelism #3095
algojohnlee
merged 9 commits into
algorand:master
from
algojack:optimize-circleci-upload-stage
Oct 19, 2021
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
onetechnical
approved these changes
Oct 19, 2021
Codecov Report
@@ Coverage Diff @@
## master #3095 +/- ##
==========================================
+ Coverage 43.66% 43.67% +0.01%
==========================================
Files 391 391
Lines 86859 86859
==========================================
+ Hits 37929 37938 +9
+ Misses 42898 42893 -5
+ Partials 6032 6028 -4
Continue to review full report at Codecov.
|
algobarb
approved these changes
Oct 19, 2021
please don't delete the branch when merging |
cce
pushed a commit
to cce/go-algorand
that referenced
this pull request
Oct 28, 2021
Since we increased a lot of things last week to pass beta tests quickly, we needed to go back and update machine sizes and parallelism for all but integration tests.
algojohnlee
pushed a commit
that referenced
this pull request
Nov 15, 2021
Integration tests (specifically, e2e-go tests) seem to be having resource issues lately, so this returns integration tests to using large instances (4 cores, ~16GB RAM) after they were downsized to medium (2 cores ~8GB RAM) in #3095. Nightly integration tests are already using large VMs.
Merged
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.
Since we increased a lot of things last week to pass beta tests quickly, we needed to go back and update machine sizes and parallelism for all but integration tests.
Tested on nightly tests, and few flaky tests failed on integration on first run, but on rerun passed: https://app.circleci.com/pipelines/github/algorand/go-algorand/2710/workflows/26b786ae-9d0b-403d-8e5a-29f8dd8919db