public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
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, 24 Dec 2025 20:39:23 +0800	[thread overview]
Message-ID: <8da2cc05-7587-4264-843d-aa2e57cbc161@windriver.com> (raw)
In-Reply-To: <CANNYZj9sUP6xxkOLauwXuGAZH17HM3zkmAzQHSp5vx7b5Gy2VA@mail.gmail.com>



On 12/23/25 18:21, Alexander Kanavin wrote:
> On Tue, 23 Dec 2025 at 08:36, Robert Yang <liezhi.yang@windriver.com> wrote:
> 
>>> 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
> 
> Even without Qi's patches, if a ptest failure happens, autobuilder
> will report it as a warning, and for 6.17 those were not happening
> either in autobuilder or for me locally. But 6.18 did indeed start to
> fail in the two bpf tests, so we had to patch them out:
> 
> https://git.openembedded.org/openembedded-core/log/?h=master-next
> 
> So there's probably something in your configuration that triggers
> those fails in 6.17 that doesn't happen in standard poky.

You're right! All test cases are passed in 6.17:

# TOTAL: 1450
# PASS:  1121
# SKIP:  329
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0

So we should hold on this upgrading.

I didn't use core-image-ptest-strace in previous testing, but test it manually
with core-image-sato, so I got the failures on 6.17.


// Robert

> 
> Alex



  reply	other threads:[~2025-12-24 12:39 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
2025-12-23 10:21           ` Alexander Kanavin
2025-12-24 12:39             ` Robert Yang [this message]
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=8da2cc05-7587-4264-843d-aa2e57cbc161@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