From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: Git mailing list <git@vger.kernel.org>
Subject: Re: [PATCH 2/2] unit-tests: ignore --long-tests
Date: Fri, 23 Oct 2026 12:45:16 +0530 [thread overview]
Message-ID: <57e42fb9-b60d-43d5-abef-432ddf8da34d@gmail.com> (raw)
In-Reply-To: <atsDvfHx3_EkrI6Z@pks.im>
On 10/23/26 12:20, Patrick Steinhardt wrote:
>>
>> $ meson test -v --test-args='-ilx'
>>
>> So, ignore -l / --long-tests in our clar tests.
>
> TIL, I didn't even know we had this switch to run long tests. That makes
> me wonder whether we should have an "--features-testbed" switch to make
> it easy to run tests same as our CI job that sets all those test
> variables, and then adapt CI to use it. It's always a pain to specify
> all of these environment variables.
>
That would indeed be a good addition! It may help us easily emulate the
feature-testbed job locally. I say "easy" hoping it does not need any
kind of additional niche dependency in order to run locally. It seems so
on taking a quick look at the the CI script :-)
> That's of course outside of the scope of this patch series, but I've got
> a pending series where I may be able to squeeze this into.
>
Cool!
>> This does not show up as a problem while running our CI as we enable
>> the expensive prerequiiste via the GIT_TEST_LONG env variable.
>
> s/prerequiiste/prerequisite/
>
Good catch. Will fix this!
>> diff --git a/t/unit-tests/unit-test.c b/t/unit-tests/unit-test.c
>> index d066c8a4c8..06ffd0f5bb 100644
>> --- a/t/unit-tests/unit-test.c
>> +++ b/t/unit-tests/unit-test.c
>> @@ -28,6 +28,7 @@ int cmd_main(int argc, const char **argv)
>> */
>> OPT_NOOP_NOARG('d', "debug"),
>> OPT_NOOP_NOARG(0, "github-workflow-markup"),
>> + OPT_NOOP_NOARG('l', "long-tests"),
>> OPT_NOOP_NOARG(0, "no-bin-wrappers"),
>> OPT_NOOP_ARG(0, "no-chain-lint"),
>> OPT_NOOP_ARG(0, "root"),
>
> Looks obviously good to me, thanks!
>
Thanks for the prompt review!
--
Sivaraam
next prev parent reply other threads:[~2026-10-23 7:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 11:01 [PATCH 0/2] Make our clar tests ignore the long-tests argument Kaartic Sivaraam
2026-10-22 11:01 ` [PATCH 1/2] unit-tests: reshuffle NOOP arguments to maintain order Kaartic Sivaraam
2026-10-23 6:50 ` Patrick Steinhardt
2026-10-22 11:01 ` [PATCH 2/2] unit-tests: ignore --long-tests Kaartic Sivaraam
2026-10-23 6:50 ` Patrick Steinhardt
2026-10-23 7:15 ` Kaartic Sivaraam [this message]
2026-10-26 7:31 ` [PATCH v2 0/2] Make our clar tests ignore the long-tests argument Kaartic Sivaraam
2026-10-26 7:31 ` [PATCH v2 1/2] unit-tests: reshuffle NOOP arguments to maintain order Kaartic Sivaraam
2026-10-26 7:31 ` [PATCH v2 2/2] unit-tests: ignore --long-tests Kaartic Sivaraam
2026-10-26 8:11 ` [PATCH v2 0/2] Make our clar tests ignore the long-tests argument Patrick Steinhardt
2026-10-26 16:10 ` 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=57e42fb9-b60d-43d5-abef-432ddf8da34d@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
/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