-
Notifications
You must be signed in to change notification settings - Fork 493
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
Checking CircleCI tests run once and only once #2749
Checking CircleCI tests run once and only once #2749
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2749 +/- ##
==========================================
- Coverage 47.14% 47.11% -0.04%
==========================================
Files 349 349
Lines 56430 56430
==========================================
- Hits 26606 26588 -18
- Misses 26845 26861 +16
- Partials 2979 2981 +2
Continue to review full report at Codecov.
|
c952d98
to
68e791c
Compare
a5d4058
to
12bb942
Compare
…circleci-tests-run-only-once
OK, I pushed the revert of 11d153a to undo the double-sharding skips that intentionally introduced. |
once i clean up normal tests, i will switch to nightlies and clean up nightlies too, before switching back to normal. |
…hub.com:algorand/go-algorand into jack/1489-checking-circleci-tests-run-only-once
Based on the matrix job @algojack added in #2749, this turns the other per-platform jobs into matrix jobs too. The most significant change in this PR is switching from building in the home directory (/home/circleci on Linux and /Users/distiller on Mac) to instead build out of /opt/cibuild to make it easier for the matrix jobs to share configuration.
Our partitioned tests might be skipping tests or running them twice. Here we want to make sure they don't do that.
Summary
Our partitioned tests might be skipping tests or running them twice. Here we want to make sure they don't do that.
Test Plan
Testing in CircleCI on this branch before merging to master