Use cargo-nextest to run test on CI and reenable tests report #1022
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.
Content
This PR changes the runner that are used for tests in CI to
cargo-nextest
. This give the following benefits :cargo2junit
and unstable cargo features.This PR also changes the way third party cargo tools are retrieved in the CI: instead of using
cargo install
that retrieve the tool source and compile them (making our github caches heavier) we now usecargo binstall
to retrieve precompiled binaries.Pre-submit checklist
Issue(s)
Closes #978