From: Anders Heimer <anders.heimer@est.tech>
To: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
openembedded-core@lists.openembedded.org
Cc: Daniel Turull <daniel.turull@ericsson.com>
Subject: Re: [OE-core] [PATCH 6/9] oeqa/oelib: test GitApplyTree patch names
Date: Wed, 24 Jun 2026 12:54:17 +0200 [thread overview]
Message-ID: <a8a958a4-d23f-4a8d-afb5-9ab4e0fb67a0@est.tech> (raw)
In-Reply-To: <DJH48HDNLJIW.EOQTZ79XS7CA@bootlin.com>
Hi Mathieu,
On 6/24/26 09:53, Mathieu Dubois-Briand wrote:
> First differing element 4:
> '2021-01-01T12:34:56Z'
> '2021-01-01T12:34:56+00:00'
>
> ['Fallback Author',
> 'fallback.author@example.com',
> 'OE Test',
> 'oe-test@example.com',
> - '2021-01-01T12:34:56Z']
> ? ^
>
> + '2021-01-01T12:34:56+00:00']
> ? ^^^^^^
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/4191
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/3961
>
> So for some reason the timezone part of the date is different : Z /
> +00:00.
>
> Yet it does work sometimes. It might be related to the host system:
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/4130
>
> Can you have a look at the issue?
Thank you for looking at this.
It is indeed related to the host system, and the git version. I bumped
the git version and could reproduce the issue locally. Git 2.45 changed
the strict ISO-8601 (%aI) representation of UTC from "+00:00" to "Z",
both values represent the same timestamp.
I will push a v2 to correct this.
Best regards,
Anders Heimer
next prev parent reply other threads:[~2026-06-24 10:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 13:35 [PATCH 0/9] oe/patch: execute patch commands without an implicit shell Anders Heimer
2026-06-23 13:35 ` [PATCH 1/9] oe/patch: drop shell=True from runcmd Anders Heimer
2026-06-23 13:35 ` [PATCH 2/9] oeqa/oelib: add runcmd tests Anders Heimer
2026-06-23 13:35 ` [PATCH 3/9] oe/patch: convert simple runcmd shell callers Anders Heimer
2026-06-23 13:35 ` [PATCH 4/9] oe/patch: avoid shell pipeline in _applypatch Anders Heimer
2026-06-23 13:35 ` [PATCH 5/9] oe/patch: remove obsolete PATCHFILE assignment Anders Heimer
2026-06-23 13:35 ` [PATCH 6/9] oeqa/oelib: test GitApplyTree patch names Anders Heimer
2026-06-24 7:53 ` [OE-core] " Mathieu Dubois-Briand
2026-06-24 10:54 ` Anders Heimer [this message]
2026-06-23 13:35 ` [PATCH 7/9] oe/patch: pass GitApplyTree commands as argv lists Anders Heimer
2026-06-23 13:35 ` [PATCH 8/9] oe/patch: return manual-resolution " Anders Heimer
2026-06-23 13:35 ` [PATCH 9/9] oeqa/oelib: test patch command argv handling Anders Heimer
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=a8a958a4-d23f-4a8d-afb5-9ab4e0fb67a0@est.tech \
--to=anders.heimer@est.tech \
--cc=daniel.turull@ericsson.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
/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