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: Thu, 25 Dec 2025 10:35:37 +0800	[thread overview]
Message-ID: <58f97151-088b-4b98-ab09-7291b1db7a00@windriver.com> (raw)
In-Reply-To: <CANNYZj_LgEZvfNiKua=bmTaC0pyvCTKr=fDmWiDRV5Vqp20omw@mail.gmail.com>



On 12/24/25 21:58, Alexander Kanavin wrote:
> On Wed, 24 Dec 2025 at 13:39, Robert Yang <liezhi.yang@windriver.com> wrote:
>> 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.
> 
> The upgrade has already merged, as it was needed for the kernel
> updates. The two failing bpf tests were patched out so that reset can
> pass.

Thank you very much!

// Robert

> 
> Alex



      reply	other threads:[~2025-12-25  2:35 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
2025-12-24 13:58               ` Alexander Kanavin
2025-12-25  2:35                 ` Robert Yang [this message]

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=58f97151-088b-4b98-ab09-7291b1db7a00@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