-
Notifications
You must be signed in to change notification settings - Fork 471
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
tests: disable TestInitialSync on CI #5053
tests: disable TestInitialSync on CI #5053
Conversation
@@ -245,6 +246,10 @@ func TestInitialSync(t *testing.T) { | |||
t.Skip("Test takes ~25 seconds.") | |||
} | |||
|
|||
if strings.ToUpper(os.Getenv("CIRCLECI")) == "TRUE" { | |||
t.Skip("Test is too heavy for amd64 builder running in parallel with other packages") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it really running in parallel with other packages though? I thought we don't allow that
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
try make test
and observe LA 100+ with all cores busy and 8+ test processes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is far as I know, tests do not run with others when t.Parallel() is not called.
That the the whole reason why we have multiple runs on CircleCi.
If we are running things in parallel, something has changed!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
t.Parallel() takes effect only within a single package (test binary)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we disable package-level parallelism in CI by passing -p 1
in the .circleci/confiig.yml file though
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh, I expected it calling make test. Then it is very weird it fails time to time
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible to run it with 5 instead of 10 full nodes instead?
or — nightly tests are running on medium (2 cores) could change the resource class used by test_nightly to run on large (4 cores) instead?
Codecov Report
@@ Coverage Diff @@
## master #5053 +/- ##
==========================================
- Coverage 53.57% 53.56% -0.02%
==========================================
Files 430 430
Lines 54091 54091
==========================================
- Hits 28979 28973 -6
- Misses 22868 22872 +4
- Partials 2244 2246 +2
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for doing this.
A couple of more tests will have the same faith:
TestSyncingFullNode
TestSimpleUpgrade
305eddf
to
8e3b681
Compare
Summary
TestInitialSync creates 10 full nodes that is too much for CI builder.
Test Plan
This is a test