From: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
To: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/7] elfutils: upgrade 0.196 -> 0.197
Date: Tue, 20 Oct 2026 17:33:14 +0200 [thread overview]
Message-ID: <5d063647-f13a-48cc-afff-a2ef9688e281@est.tech> (raw)
In-Reply-To: <DM9Q75SEZA82.3LDAH4WKTQUCF@bootlin.com>
On 2026-10-20 16:13, Mathieu Dubois-Briand wrote:
> The log in there is really verbose. I hope you can extract some useful
> data from these few thousand lines of ptest log.
Hi Mathieu,
Able to identify the problem and verified locally and sent v2.
Actually recipe is expecting two test cases to fail but those are
passing now after upgrade and dropped that change.
Regards,
Jaipaul
next prev parent reply other threads:[~2026-10-20 15:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 9:29 [PATCH 0/7] Upgrades on 20th October Jaipaul Cheernam
2026-10-20 9:29 ` [PATCH 1/7] elfutils: upgrade 0.196 -> 0.197 Jaipaul Cheernam
2026-10-20 14:13 ` [OE-core] " Mathieu Dubois-Briand
2026-10-20 15:33 ` Jaipaul Cheernam [this message]
2026-10-20 15:42 ` Khem Raj
2026-10-20 15:31 ` [PATCH v2] " Jaipaul Cheernam
2026-10-20 17:26 ` [PATCH v3] " Jaipaul Cheernam
2026-10-20 9:29 ` [PATCH 2/7] ethtool: upgrade 7.1 -> 7.2 Jaipaul Cheernam
2026-10-20 9:29 ` [PATCH 3/7] repo: upgrade 2.68.1 -> 2.69 Jaipaul Cheernam
2026-10-20 9:29 ` [PATCH 4/7] libzip: upgrade 1.12 -> 1.12.1 Jaipaul Cheernam
2026-10-20 9:29 ` [PATCH 5/7] libunistring: upgrade 1.4.2 -> 1.5 Jaipaul Cheernam
2026-10-20 9:29 ` [PATCH 6/7] log4cplus: upgrade 2.2.0.1 -> 2.2.1 Jaipaul Cheernam
2026-10-20 9:29 ` [PATCH 7/7] python3-jsonpointer: upgrade 3.2.1 -> 3.4 Jaipaul Cheernam
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=5d063647-f13a-48cc-afff-a2ef9688e281@est.tech \
--to=jaipaul.cheernam@est.tech \
--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