Jason Heeris

Thanks for that, I missed the significance of those in the docs. I thought they were more for "smoke" tests. I will give this a go. Note that the workflow...

Don't take too much from my vague description there, I am still trying to make both ends of a CI pipeline meet in the middle so it's hard to describe...

Oh a bare-metal `no-std` deployment is (thankfully) way beyond what I want to measure coverage for. Think OpenWRT/router style platforms, that's closer to what I'm using. After reading a tonne...

This also relates to something I mention in #1352: needing to run separate CI jobs for build + test, and for coverage. It's not possible to get jUnit XML output...

Just confirming, all I had to do was add that flag and it works perfectly in [my example project](https://gitlab.com/detly/tarp-test/-/pipelines/770502589).

As a note, I think you could add support for [Ninja](https://ninja-build.org/) and get out-of-the-box support for the vast majority of C and C++ projects.

> I'm not sure whether or how well serial access will work from inside flatpak even with that issue resolved. Apart from that, it does actually work! I get serial...

> No repo/ppa, but the CI does build and publish `.debs`, which you can find links to here: https://wezfurlong.org/wezterm/install/linux.html#installing-on-ubuntu-and-debian-based-systems Ah I saw that, and initially dismissed it because of the...

> FWIW, I just setup an apt repo for wezterm. Details can be found at https://wezfurlong.org/wezterm/install/linux.html#installing-on-ubuntu Ah I missed this, thanks! I really appreciate it.

Any in particular you had in mind?