Junio C Hamano <gitster@xxxxxxxxx> writes:
> Signed-off-by: Junio C Hamano <gitster@xxxxxxxxx>
> ---
> * I've been running my local post-integration-pre-pushout tests of
> 'seen' with these two sanitizer tests, which has saved me from a
> few potential embarrassments early. As it takes a lot extra time
> to run these locally, I am aiming to burden contributors who run
> their due diligence "before sending the patch" checks using the
> GitHub Actions CI ;-).
>
> The way the patch adds jobs to CI just imitates how -leaks one is
> defined.
>
> .github/workflows/main.yml | 6 ++++++
> ci/lib.sh | 3 +++
> 2 files changed, 9 insertions(+)
One downside is that the usual CI cycle for a branch that takes a
bit shorter than 40 minutes seems to take between 50 to 60 minutes
(the primary culprit seems to be the address sanitizer).
Arguably, that 10 or 20 minutes are time saved from human
developers' time, so it might not be too bad, but I'll keep
it out of 'next' for now.
> diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
> index 831f4df56c..2f80da7cfb 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: linux-address
> + cc: gcc
> + pool: ubuntu-latest
> + - jobname: linux-undefined
> + cc: gcc
> + pool: ubuntu-latest
> env:
> CC: ${{matrix.vector.cc}}
> CC_PACKAGE: ${{matrix.vector.cc_package}}
> diff --git a/ci/lib.sh b/ci/lib.sh
> index 1b0cc2b57d..678edd5abb 100755
> --- a/ci/lib.sh
> +++ b/ci/lib.sh
> @@ -278,6 +278,9 @@ linux-leaks)
> export GIT_TEST_PASSING_SANITIZE_LEAK=true
> export GIT_TEST_SANITIZE_LEAK_LOG=true
> ;;
> +linux-address | linux-undefined)
> + export SANITIZE=${jobname#linux-}
> + ;;
> esac
>
> MAKEFLAGS="$MAKEFLAGS CC=${CC:-cc}"
