How to get coverage for cross compiled targets?

[ReenigneArcher]

I'm new to Rust and been fighting with my GitHub workflow to get cross compiling working. I think I finally got it working (at least for aarch64-unknown-linux-gnu), and come to find out that tarpaulin still fails at the end of the step. I think it compiled properly but doesn't actually run the tests.

This is my workflow (in it's current state): https://github.com/LizardByte/Koko/blob/79770d24499c49643c01eee38c938ae457a5c7ca/.github/workflows/ci.yml#L91-L233

Anything that can be done, or should I not expect to get coverage data for cross compiled targets?

[xd009642]

So there's quite a bit in that actions file - a bit too much to instantly grok my end. Hopefully, though this is helpful. If you're cross-compiling then your executable is going to be running on a different host than the target host typically. And if I can compile something for say windows on my linux laptop I can't run it without something like WINE. Or looking at your targets likely QEMU.

With that in mind you may have to run the coverage job in something like QEMU 🤔

[ReenigneArcher]

@xd009642 thank you for the reply. I figured that was the case and I was trying a different approach to use the new public ubuntu arm runners with containers for alpine, but that seems to open a whole new set of issues.

Anyway, I'll take a look at using qemu to run the tests (hopefully allowing it to compile without qemu will be fine).