From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH] ci: add address and undefined sanitizer tasks
Date: Sun, 09 Oct 2022 15:44:22 -0700 [thread overview]
Message-ID: <xmqq8rlo62ih.fsf@gitster.g> (raw)
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
* 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(+)
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}"
--
2.38.0-167-gf9a88ca9e9
next reply other threads:[~2022-10-09 23:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 22:44 Junio C Hamano [this message]
2022-10-10 23:25 ` [PATCH] ci: add address and undefined sanitizer tasks Junio C Hamano
2022-10-11 0:00 ` Jeff King
2022-10-11 0:09 ` Junio C Hamano
2022-10-21 5:59 ` Junio C Hamano
2022-10-21 6:25 ` Jeff King
2022-10-11 0:21 ` [PATCH v2] " Junio C Hamano
2022-10-11 0:28 ` Jeff King
2022-10-11 8:23 ` Ævar Arnfjörð Bjarmason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq8rlo62ih.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).