Tarpaulin timeout in zebra tests with latest develop

[xd009642]

So this is just a place to move the discussion from #618 to as all the other issues in that issue have been addressed. When running latest tarpaulin on zebra I get timeouts in tower-batch/tests/ed25519.rs on the tests batch_flushes_on_max_items and batch_flushes_on_max_latency. Now if I run tarpaulin filtering on just that module or those tests I don't get the timeout error and it works. So unfortunately I can't just run on the relevant tests and analyse the minimal traces. Of course once I have the llvm-cov stuff fully working it won't matter in nightly but I'd like to fix this in stable as well.

Tagging @dconnolly just to notify someone involved in zebra

[codehearts]

I've noticed a similar issue with 0.16.0 on my own project, but I haven't tried running the offending tests individually to see if they pass. I'm not sure if that could be helpful, or if this ticket is specifically about a regression in the 0.17.0 release.

I've been meaning to build a smaller proof-of-concept that doesn't take forever to run to open a ticket here, I can attach it here once I do or open a new ticket if you think it's unrelated!

[xd009642]

You can mention it here, as they're both timeouts it could help to have all the info in one place 😁

[xd009642]

Closing this issue as the llvm coverage backend is now released --engine llvm which solves a bunch of the ptrace issues