search

MiniaczQ / Cargo-nextest-llvm-cov-integration-tests

2 stars 0 forks source link

Profraws don't get generated after tests run #1

Closed MiniaczQ closed 1 year ago

MiniaczQ commented 1 year ago 
unit-test  |   Extracting 1 binaries to /tmp/nextest-archive-ECVYCx
unit-test  |    Extracted 3 files to /tmp/nextest-archive-ECVYCx in 0.01s
unit-test  |     Starting 1 test across 1 binary
unit-test  |         PASS [   0.002s] nextext-llvm-cov-repro tests::print_foo
unit-test  | ------------
unit-test  |      Summary [   0.003s] 1 test run: 1 passed, 0 skipped
unit-test  | warning: not found *.profraw files in /app/target/llvm-cov-target; this may occur if target directory is accidentally cleared, or running report subcommand without running any tests or binaries
unit-test  | error: no input files specified. See llvm-profdata merge -help
unit-test  | error: failed to merge profile data: process didn't exit successfully: `/usr/local/rustup/toolchains/1.73.0-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/bin/llvm-profdata merge -sparse -f /app/target/llvm-cov-target/app-profraw-list -o /app/target/llvm-cov-target/app.profdata` (exit status: 1)
MiniaczQ commented 1 year ago

I think the binaries that nextest is building aren't correct, because running cargo llvm-cov nextest rebuilds them from ground up.

MiniaczQ commented 1 year ago

The problem was variables not being exported properly, they were only at the shell level, not os level