From: Patrick Steinhardt <ps@pks.im>
To: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Cc: git@vger.kernel.org, Toon Claes <toon@iotcl.com>
Subject: Re: [PATCH 5/5] t8020: fix test failure due to indeterministic tag sorting
Date: Thu, 2 Oct 2025 13:24:51 +0200 [thread overview]
Message-ID: <aN5hA1inMQojbnXq@pks.im> (raw)
In-Reply-To: <50aa008e-1cbf-4e77-8e51-6f2c32b6c12a@app.fastmail.com>
On Thu, Oct 02, 2025 at 01:10:53PM +0200, Kristoffer Haugsbakk wrote:
> On Thu, Oct 2, 2025, at 13:04, Patrick Steinhardt wrote:
> > [snip]
> >
> > But why do both of these tags point to the same commit? "km2" really is
> > supposed to be a merge, but due to the way the test is constructed the
> > merge turns into a fast-forward merge. Which means that the resulting
> > does not even contain a criss-cross merge in the first place! A quick
>
> “the resulting <noun>”
Ah, right. What's missing here is "commit graph". Fixed locally, will
send out with the next iteration.
Thanks!
Patrick
next prev parent reply other threads:[~2025-10-02 11:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 11:04 [PATCH 0/5] gitlab-ci: some fixes for failures on Windows Patrick Steinhardt
2025-10-02 11:04 ` [PATCH 1/5] gitlab-ci: dedup instructions to disable realtime monitoring Patrick Steinhardt
2025-10-02 11:04 ` [PATCH 2/5] gitlab-ci: ignore failures " Patrick Steinhardt
2025-10-02 11:04 ` [PATCH 3/5] gitlab-ci: drop workaround for Python certificate store on Windows Patrick Steinhardt
2025-10-06 10:19 ` Toon Claes
2025-10-02 11:04 ` [PATCH 4/5] gitlab-ci: upload Meson test logs as JUnit reports Patrick Steinhardt
2025-10-02 11:04 ` [PATCH 5/5] t8020: fix test failure due to indeterministic tag sorting Patrick Steinhardt
2025-10-02 11:10 ` Kristoffer Haugsbakk
2025-10-02 11:24 ` Patrick Steinhardt [this message]
2025-10-06 10:20 ` Toon Claes
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=aN5hA1inMQojbnXq@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=toon@iotcl.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).