From: Robert Yang <liezhi.yang@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org, randy.macleod@windriver.com
Subject: Re: [OE-core] [PATCH 1/1] strace: 6.17 -> 6.18
Date: Wed, 17 Dec 2025 10:58:29 +0800 [thread overview]
Message-ID: <b127705e-0b9a-4a5b-9fcc-c3014e4c680c@windriver.com> (raw)
In-Reply-To: <CANNYZj8=3egJPC3dT1bc-9n=38-OAyAKfwb81mJjuiSiqVcaQw@mail.gmail.com>
Hi Alexander,
On 12/16/25 19:29, Alexander Kanavin wrote:
> On Tue, 16 Dec 2025 at 10:57, Robert Yang via lists.openembedded.org
> <liezhi.yang=windriver.com@lists.openembedded.org> wrote:
>> The 6.17 has 27 failed test cases, and 6.18 only has 2 failed ones:
>> FAIL: bpf.gen.test
>> FAIL: bpf-v.gen.test
>
> This needs a bit more context. If the old version had failures, and
> the new version still has failures, why aren't they seen in testing?
They are ptest failures, and there is no specific test for it, so we don't see
the failures. I did look into the failures, but didn't know how to fix that, the
newer version has less failures than the older one, so I sent the upgrade patch.
// Robert
> Where and how do they happen? Should they be fixed rather?
> > Alex
next prev parent reply other threads:[~2025-12-17 2:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 9:57 [PATCH 0/1] strace: 6.17 -> 6.18 liezhi.yang
2025-12-16 9:57 ` [PATCH 1/1] " liezhi.yang
2025-12-16 11:29 ` [OE-core] " Alexander Kanavin
2025-12-17 2:58 ` Robert Yang [this message]
2025-12-17 8:41 ` Alexander Kanavin
2025-12-23 7:36 ` Robert Yang
2025-12-23 10:21 ` Alexander Kanavin
2025-12-24 12:39 ` Robert Yang
2025-12-24 13:58 ` Alexander Kanavin
2025-12-25 2:35 ` Robert Yang
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=b127705e-0b9a-4a5b-9fcc-c3014e4c680c@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.macleod@windriver.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