ci: use nextest for running rust tests #2031
Conversation
| # - uses: bmwill/rust-cache@v1 # Fork of 'Swatinem/rust-cache' which allows caching additional paths | ||
| # with: | ||
| # path: ~/.cargo/registry/src/**/librocksdb-sys-* | ||
| - uses: taiki-e/install-action@nextest |
There was a problem hiding this comment.
I think the latest advice is to use baptiste0928/cargo-installdue to its superior caching.
There was a problem hiding this comment.
This is actually downloading pre-compiled binary so caching isn't even needed.
| cargo build --all-features --lib | ||
| cargo test --all-features --no-run # -j N # uncomment and set a low number if builds start OOMing again | ||
| cargo test --all-features | ||
| cargo nextest run --all-features --profile ci |
There was a problem hiding this comment.
Do we want to use the --config-file option here to make sure our custom config file is always taken into account? (w/o relying on default location that is, since it's relative to the workspace root .. imagine if we move everything to crates/)
There was a problem hiding this comment.
Even with everything moved to crates/ directory we'd still keep the repo root as the workspace root I'd think
| [profile.ci.junit] | ||
| path = "junit.xml" |
There was a problem hiding this comment.
I'm not sure what we would use this for?
There was a problem hiding this comment.
This generates a junit file that could be later used in order to analyze the test run to do things like open up issues for flaky tests, etc
It's unused now
No description provided.