Closed ChristianBeilschmidt closed 1 year ago
That's pretty odd, as 0.22.0 didn't touch the ptrace tracing at all, the only change that could impact it is setting --ignore-tests
as default.
You could always try --engine llvm
to use the llvm coverage but some projects are reporting spurious failures in CI I can't recreate (but only one person)
Closing as inactive
We experience spurious segfaults in our coverage runs on our GitHub CI as well as locally.
This is one example: https://github.com/geo-engine/geoengine/actions/runs/3233572540/jobs/5295594939
It ran through the second time in this case. All tests work in our non-tarpaulin runs.
Unfortunately, I cannot generate a minimal example to reproduce it in a smaller setting. But I am wondering if other projects experience similar problems.
We currently went back to 0.21 to have our CI working again.