From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: Teng Long <dyroneteng@gmail.com>, Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/3] ci sanitizer cleanups and performance improvements
Date: Thu, 1 Jun 2023 14:02:20 -0400 [thread overview]
Message-ID: <20230601180220.GA4167745@coredump.intra.peff.net> (raw)
Here are a few patches to tweak our CI sanitizer setup. The first one
hopefully increases coverage. The other two just aim to reduce the
amount of CPU we use.
[1/3]: ci: use clang for ASan/UBSan checks
[2/3]: ci: run ASan/UBSan in a single job
[3/3]: ci: drop linux-clang job
.github/workflows/main.yml | 10 ++--------
ci/lib.sh | 7 ++-----
2 files changed, 4 insertions(+), 13 deletions(-)
-Peff
next reply other threads:[~2023-06-01 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 18:02 Jeff King [this message]
2023-06-01 18:03 ` [PATCH 1/3] ci: use clang for ASan/UBSan checks Jeff King
2023-06-01 18:09 ` [PATCH 2/3] ci: run ASan/UBSan in a single job Jeff King
2023-06-01 18:10 ` [PATCH 3/3] ci: drop linux-clang job Jeff King
2023-06-03 1:35 ` [PATCH 0/3] ci sanitizer cleanups and performance improvements Junio C Hamano
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=20230601180220.GA4167745@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=dyroneteng@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).