From: Phillip Wood <phillip.wood123@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH] ci(*-leaks): skip the git-svn tests to save time
Date: Tue, 20 Jan 2026 10:34:39 +0000 [thread overview]
Message-ID: <79c29032-dc32-4030-95ad-dfbd50d9b6ab@gmail.com> (raw)
In-Reply-To: <xmqqa4yc5brq.fsf@gitster.g>
On 17/01/2026 18:34, Junio C Hamano wrote:
>
> Yup, I generally like this direction, and introducing NO_P4_TESTS
> and NO_CVS_TESTS would not be so bad. Here is how it looks on top
> of Dscho's patch.
>
> --- >8 ---
> Subject: [PATCH] ci: skip CVS and P4 tests in leaks job, too
>
> Looking at the CI logs, the p4 and cvs tests account for another 24
> minutes of test time and they offer minimal value for quite a
> similar reason as the previous step.
>
> Let's introduce and use a mechanism to skip these tests to save
> some resources.
The patch looks good to me, it is very convenient that we can put the
test in the library files rather than each test file. Should we drop
these tests from the ASan job as well?
Thanks
Phillip
> Suggested-by: Phillip Wood <phillip.wood123@gmail.com>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
> ci/lib.sh | 2 ++
> t/lib-cvs.sh | 6 ++++++
> t/lib-git-p4.sh | 5 +++++
> 3 files changed, 13 insertions(+)
>
> diff --git a/ci/lib.sh b/ci/lib.sh
> index a165c7f268..3ecbf147db 100755
> --- a/ci/lib.sh
> +++ b/ci/lib.sh
> @@ -356,7 +356,9 @@ linux-musl-meson)
> ;;
> linux-leaks|linux-reftable-leaks)
> export SANITIZE=leak
> + export NO_CVS_TESTS=LetsSaveSomeTime
> export NO_SVN_TESTS=LetsSaveSomeTime
> + export NO_P4_TESTS=LetsSaveSomeTime
> ;;
> linux-asan-ubsan)
> export SANITIZE=address,undefined
> diff --git a/t/lib-cvs.sh b/t/lib-cvs.sh
> index 57b9b2db9b..c8b4404888 100644
> --- a/t/lib-cvs.sh
> +++ b/t/lib-cvs.sh
> @@ -2,6 +2,12 @@
>
> . ./test-lib.sh
>
> +if test -n "$NO_CVS_TESTS"
> +then
> + skip_all='skipping git cvs tests, NO_CVS_TESTS defined'
> + test_done
> +fi
> +
> unset CVS_SERVER
>
> if ! type cvs >/dev/null 2>&1
> diff --git a/t/lib-git-p4.sh b/t/lib-git-p4.sh
> index 2a5b8738ea..d22e9c684a 100644
> --- a/t/lib-git-p4.sh
> +++ b/t/lib-git-p4.sh
> @@ -16,6 +16,11 @@ P4D_TIMEOUT=300
>
> . ./test-lib.sh
>
> +if test -n "$NO_P4_TESTS"
> +then
> + skip_all='skipping git p4 tests, NO_P4_TESTS defined'
> + test_done
> +fi
> if ! test_have_prereq PYTHON
> then
> skip_all='skipping git p4 tests; python not available'
next prev parent reply other threads:[~2026-01-20 10:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 17:31 [PATCH] ci(*-leaks): skip the git-svn tests to save time Johannes Schindelin via GitGitGadget
2026-01-16 19:20 ` Junio C Hamano
2026-01-17 15:04 ` Phillip Wood
2026-01-17 18:34 ` Junio C Hamano
2026-01-17 19:02 ` Kristoffer Haugsbakk
2026-01-18 0:35 ` Junio C Hamano
2026-01-20 10:31 ` Phillip Wood
2026-01-20 10:34 ` Phillip Wood [this message]
2026-01-20 15:42 ` Junio C Hamano
2026-01-23 14:47 ` Phillip Wood
2026-01-23 17:46 ` Junio C Hamano
2026-01-26 9:47 ` Phillip Wood
2026-01-26 16:06 ` 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=79c29032-dc32-4030-95ad-dfbd50d9b6ab@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=phillip.wood@dunelm.org.uk \
/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