ci: run unit tests in separate processes #1559
Merged
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.
What this PR does / why we need it?
Since Axon uses global variables, run all tests in one process may cause unexpected errors.
With this PR, unit tests will run in separate processes, instead of in threads.
False errors in the unit tests decrease developers' expectation threshold, make developers feel that failed CI checks are reasonable.
Like the story of the boy who cried wolf, it's dangerous.
I have to check CI every time when I see a red cross mark ❌, false errors also increase my mental load.
Let false errors f**k off!
Out of Topic
The
$HOME/.cargo/bin
has more than 250 MiB binaries, which will be restored from cache, and then they will be overwritten by the binaries that download from internet.Every workflow will put their tools that be downloaded into that directory, but no workflows will clean that directory.
Execute
ls -l ~/.cargo/bin/`
.CI Settings
CI Usage
Tip: Check the CI you want to run below, and then comment
/run-ci
.CI Switch
CI Description