-
# š Bug
Sometimes coverage tests seem to fail to build, for example:
https://github.com/aptos-labs/aptos-core/actions/runs/7279601867/job/19836253263?pr=11079
Quoting from the build warnings ā¦
-
Property test for `sequences::len_crosscheck` passes CI and `cargo test`, but it fails in the coverage check. For details, please visit the [coverage report](https://github.com/stacks-network/clarity-ā¦
-
-
Hi :)
First of all, thanks for your work on this project.
V2 seems to have introduced a bug in the macos environment.
```
Run taiki-e/install-action@v2
/Users/runner/work/_actions/taiki-e/insā¦
-
**Describe the bug**
I run `cargo tarpaulin` and receive error `Error: "Parsing failed"`.
I am using Windows 11 and run this from Git Bash.
Complete ouptut (skipping compilation):
```
Finiā¦
-
### Describe the bug
I clone the source code of Reth v0.1.0-alpha.11 to my environment, when I run the command: cargo llvm-cov nextest --html --locked --manifest-path bin/reth/Cargo.toml --all-featuā¦
-
The Github actions for testing and code coverage take 13 and 15 minutes, respectively.
The following are quite slow:
```sh
# These libraries are needed for tauri, and can be quite big.
sudo apā¦
-
## I get this error while compiling the crate : `trust-dns-resolver = "0.21.2"`, with coverage flags and on nightly.
### Replication:
```bash
cargo new compiler-bug
cd compiler-bug
cargo add tā¦
-
### Description of the bug:
I write a toolchain rule for gcc14.1.0, but linker cannot found crt1.o
```
error: cannot open crti.o: No such file or directory,
```
even though I already specifiā¦
-
this can run in the CI