proc-macro crate in workspace unexpectently exits

[Javagedes]

Describe the bug
Workspaces with a proc-macro crate fail to execute tests (The failure happens when execution of the test exe begins, but before any test starts) with the following error:

2024-10-28T15:58:05.678629Z  INFO cargo_tarpaulin::process_handling: running D:\a\rust-ci-testing\rust-ci-testing\target\debug\deps\rust_proc_macro-6ef64dc17f0828ce.exe
2024-10-28T15:58:05.678931Z  INFO cargo_tarpaulin::process_handling: Setting LLVM_PROFILE_FILE
2024-10-28T15:58:05.686895Z ERROR cargo_tarpaulin: Test failed during run
Error: "Test failed during run"
Error: Process completed with exit code 1.

I can only reproduce on a github action windows-latest runner (but 100% of the time). It does not happen on ubuntu-latest image (even with the --engine llvm flag) and it does not happen on windows locally. it fails with or without any tests actually in the crate. It fails with engine llvm and --no-dead-code

I tried adding tests to see if that helped any, but it continued to fail. I also tried adding tests as described in #326 but it continues to fail.

I am currently on:
cargo-tarpaulin 0.31.2
1.80.0

To Reproduce
I have set up a repo with a CI job that hits the issue: Javagedes/rust-ci-testing with an example run here: action/Run Tests

Expected behavior
I would expect the test harness to not unexpectedly fail without running any tests.

[xd009642]

Hmm that's super odd, could you add --dump-traces to the tarpaulin flags. Hopefully it's not so long that GHA gives up on printing the logs.

I don't really use windows so this might take me some time to replicate (I need to find a windows machine and setup a dev env or find a friend who can help to get a quicker turnaround)

[nightkr]

I'm seeing something similar on Linux after upgrading to Rust 1.83.0, both in CI (GitHub Actions) and locally (Arch). Rust 1.82.0 seems to work fine.

[xd009642]

oh weird/interesting that's very helpful thanks 👍

[nightkr]

Output from --dump-traces: tarpaulin_20241129173337.json

[nightkr]

Of course, feel free to split this into a separate issue if it seems unrelated.