ci: enable cargo nextest for ci jobs #2949
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.
Current Behaviour
The CI jobs use the default
cargo test
test runner for Rust tests.Proposed Changes
Switch to using
cargo nextest
in CI jobs in order to speed up CI.The changes should not affect builds on developers' machines;
cargo nextest
is only used ifgradlew test
is used and the environemnt variableCI
is set totrue
.For consistency, all references to the previous version of the
ockam-builder
Docker image have been updated to the new version (which includesnextest
).Fixes #2924.
Checks