On Tue, Jul 26, 2022 at 01:09:13PM +0200, Ævar Arnfjörð Bjarmason wrote: > Per [2] the GitHub fork of git.git runs with these in CI, so it's > already useful to some forks of this repository. Yeah, it has been helpful there and I think this is worth doing as part of our CI. It's a lot of CPU versus running the test suite once on Linux, but probably not compared to the overall cost of our current CI. For the GitHub fork, the code-coverage issues you noticed were easy: we only built one variant, so we could just test with those knobs. ;) But I tend to agree with your approach here to just test on one platform, which covers _most_ of the code. It's certainly better than the status quo, and it strikes a nice balance of CPU versus coverage. One thing I'd say... > diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml > index cd1f52692a5..4f59a7aa44c 100644 > --- a/.github/workflows/main.yml > +++ b/.github/workflows/main.yml > @@ -251,6 +251,12 @@ jobs: > - jobname: linux-leaks > cc: gcc > pool: ubuntu-latest > + - jobname: SANITIZE=address > + cc: gcc > + pool: ubuntu-latest > + - jobname: SANITIZE=undefined > + cc: gcc > + pool: ubuntu-latest There's really no reason to split the "address" and "undefined" builds into two jobs. We expect them to pass, and if one fails, having the results split is not likely to give any extra information. So I think one job with SANITIZE=address,undefined is fine, and reclaims some of the extra CPU we're spending. -Peff
