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: Tue, 23 Dec 2025 15:36:06 +0800 [thread overview]
Message-ID: <473904dd-5f19-4331-91a3-4ccdab694c1c@windriver.com> (raw)
In-Reply-To: <CANNYZj8c1DRLJfxZMVVT3fx2Db8fnUc8A73_pE3AasKRMQ6U1A@mail.gmail.com>
Hi Alexander,
On 12/17/25 16:41, Alexander Kanavin wrote:
> On Wed, 17 Dec 2025 at 03:58, Robert Yang <liezhi.yang@windriver.com> 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.
>
> But we do run strace ptests, and they do not fail, e.g. with latest
> nightly master:
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/2761/steps/14/logs/stdio
>
> Does bitbake -c testimage core-image-ptest-strace fail for you? How
> did you set up and ran the tests to see them fail?
You didn't see the failure is because core-image-ptest has PTEST_EXPECT_FAILURE
as reported by Qi:
https://lists.openembedded.org/g/openembedded-core/message/227411
I can see the failure after applied Qi's patches. Or we can manually see the
failures via:
# pest-runner strace
// Robert
>
> Alex
next prev parent reply other threads:[~2025-12-23 7:36 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
2025-12-17 8:41 ` Alexander Kanavin
2025-12-23 7:36 ` Robert Yang [this message]
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=473904dd-5f19-4331-91a3-4ccdab694c1c@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