From: Phillip Wood <phillip.wood123@gmail•com>
To: Patrick Steinhardt <ps@pks•im>, Junio C Hamano <gitster@pobox•com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx•de>, git@vger•kernel.org
Subject: Re: [PATCH] gitlab-ci: always run MSVC-based Meson job
Date: Tue, 6 May 2025 14:17:21 +0100 [thread overview]
Message-ID: <142f6110-b26d-4495-9b68-7c438b17f86b@gmail.com> (raw)
In-Reply-To: <aBnm4fP1RYgoIEc4@pks.im>
On 06/05/2025 11:39, Patrick Steinhardt wrote:
> On Mon, Apr 28, 2025 at 11:44:08AM -0700, Junio C Hamano wrote:
>> Johannes Schindelin <Johannes.Schindelin@gmx•de> writes:
>>
>> Or perhaps we pick a
>> single representative job and only after it passes start other
>> jobs? None of the tweaks along these lines I can think of feel
>> satisfying to me.
>
> Wouldn't that only mean that the pipeline takes even longer from start
> to finish? Even if the representative job succeeds it doesn't tell me
> anything about whether there are leaks, or whether it works on Windows,
> or on macOS. But given that I am on Linux, I especially care about jobs
> that use a platform different than my own and always wait for them to
> finish before sending out a patch series to the mailing list.
I did wonder if it is possible to make a failing job kill/cancel all the
other jobs but I think we have a few flaky tests that occasionally
randomly fail which complicates things.
Best Wishes
Phillip
> Patrick
>
next prev parent reply other threads:[~2025-05-06 13:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 9:32 [PATCH] gitlab-ci: always run MSVC-based Meson job Patrick Steinhardt
2025-04-28 10:59 ` Johannes Schindelin
2025-04-28 18:44 ` Junio C Hamano
2025-05-06 10:39 ` Patrick Steinhardt
2025-05-06 13:17 ` Phillip Wood [this message]
2025-05-13 9:12 ` Patrick Steinhardt
2025-05-13 17:03 ` Junio C Hamano
2025-05-14 2:16 ` Patrick Steinhardt
2025-05-14 16:55 ` 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=142f6110-b26d-4495-9b68-7c438b17f86b@gmail.com \
--to=phillip.wood123@gmail$(echo .)com \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=ps@pks$(echo .)im \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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