-
Is it expected to get no coverage report after a panic inside a test? My command is `cargo llvm-cov nextest --workspace --lcov --output-path cargotest.lcov --no-fail-fast` in https://github.com/Materi…
-
I have seen the other issues and comments in #144 related to argument parsing for nextest. I also realize it is a good chance this was already fixed yesterday in #197 and haven't tested to build cargo…
-
`cargo nextest run --no-fail-fast` produces one failure on my machine:
```
FAIL [ 0.064s] wgpu::wgpu-tests zero_init_texture_after_discard::discarding_depth_target_reset…
-
CI check continuous Failed serveral times, which can normal execution in the local environment.
Task: https://github.com/rooch-network/rooch/actions/runs/6013202366/job/16329191126?pr=720
```
…
-
# 🐛 Bug
## To reproduce
**Code snippet to reproduce**
```rust
scripts/dev_setup.sh
```
**Stack trace/error message**
```
Installing Rust......
info: This is the version for the rust…
-
[nextest](https://github.com/nextest-rs/nextest) is an alternative to the standard `cargo test` test runner. Some advantages over the standard test runner which I found could be of interest for us:
…
-
cargo-llvm-cov v0.5.3
Maybe I'm misunderstanding, but the tests are not skipped when running either `cargo llvm-cov` or `cargo nextest run` alone, so my expectations are the tests should not be ski…
-
Tests (particularly the integration tests I think) take >20mins to complete; can we speed this up? Does `cargo nextest` help at all (did we try it and find it didn't?). Any other way to parallelise te…
-
# Current
There is some nextest config here
https://github.com/build-trust/ockam/tree/develop/.config
# Desired
Move it to https://github.com/build-trust/ockam/tree/develop/tools without bre…
-
## Summary
```
cargo-package-nextest> test object_cache::tests::invalidate ... FAILED
cargo-package-nextest> failures:
cargo-package-nextest> failures:
cargo-package-nextest> object_cache::…