public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Randy MacLeod <randy.macleod@windriver.com>
To: raj.khem@gmail.com, Deepthi.Hemraj@windriver.com,
	Ross Burton <ross.burton@arm.com>,
	Stephan.Wolf@kontron-ais.com
Cc: openembedded-core@lists.openembedded.org,
	"steve@sakoman.com" <steve@sakoman.com>
Subject: Re: [OE-core] [kirkstone][PATCH] glibc: stable 2.35 branch updates
Date: Thu, 14 Nov 2024 17:27:38 -0500	[thread overview]
Message-ID: <f5a1f3e7-e808-4854-892d-49a77b909e64@windriver.com> (raw)
In-Reply-To: <CAMKF1srVR3LZW3Hq45XWxvFe5dkkfAxySqBzsZuyts576pqEYA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2515 bytes --]

Add Steve, Ross and Stephan.

On 2024-10-03 10:38 a.m., Khem Raj via lists.openembedded.org wrote:
> On Thu, Oct 3, 2024 at 4:22 AM Hemraj, Deepthi via
> lists.openembedded.org
> <Deepthi.Hemraj=windriver.com@lists.openembedded.org> wrote:
>> Hi Khem & Steve,
>>
>> Thanks for checking out the results and your comments.
>>
>>>> Is this regression? and is it a persistent failure?
>> We analyzed the issue further by debugging it manually and observed that the testcase "nptl/tst-thread-affinity-sched.c" passed as expected. Hence, we ran the testsuite again after the update and found that the issue was not reproduced anymore.
> Thanks, I wonder why it failed the first time. Was the system running
> these suites overloaded ?, I would like to see if there is a pattern
> to these failures.
> for now this looks ok to me to apply.

Interestingly (in a bad way!),
this regression may be related to a problem that Stephan just reported. See:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=15647

It seems that the problematic commit is:
a180e82837 Linux: Make __rseq_size useful for feature detection (bug 
31965) but let's get that confirmed in the bug report.


The lesson learned is that if there's a regression from a glibc update 
even a single intermittent failure,
we should spend more time investigating the problem.

Deepthi did re-run the tests both manually and as part of the test suite 
only to find that the issue
was not reproducible but in hindsight, we could have done more.

We'll work on improving our testing.

../Randy




>
>> Please find the following results after the update which has 2 less failures than the results before update.
>> After Update
>> PASS - 4781
>> FAIL - 145
>> XPASS - 6
>> XFAIL - 16
>> UNSUPPORTED - 237
>>
>> Before update:
>> PASS - 4770
>> FAIL - 148
>> XPASS - 6
>> XFAIL - 16
>> UNSUPPORTED - 237
>>
>> Diff:
>> PASS - +11
>> FAIL - -3
>> XPASS - 0
>> XFAIL - 0
>> UNSUPPORTED - 0
>>
>>
>>
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> View/Reply Online (#205207):https://lists.openembedded.org/g/openembedded-core/message/205207
>> Mute This Topic:https://lists.openembedded.org/mt/108647219/3616765
>> Group Owner:openembedded-core+owner@lists.openembedded.org
>> Unsubscribe:https://lists.openembedded.org/g/openembedded-core/unsub [randy.macleod@windriver.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>

-- 
# Randy MacLeod
# Wind River Linux

[-- Attachment #2: Type: text/html, Size: 4712 bytes --]

  reply	other threads:[~2024-11-14 22:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-25 13:11 [kirkstone][PATCH] glibc: stable 2.35 branch updates Deepthi.Hemraj
2024-09-25 13:16 ` Hemraj, Deepthi
2024-09-25 15:17   ` [OE-core] " Khem Raj
2024-09-26  5:34     ` Hemraj, Deepthi
2024-09-27 12:56       ` [OE-core] " Steve Sakoman
2024-10-03 11:22         ` Hemraj, Deepthi
2024-10-03 14:38           ` [OE-core] " Khem Raj
2024-11-14 22:27             ` Randy MacLeod [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-01-25 16:16 [OE-core][kirkstone][PATCH] " Peter Marko
2026-02-23 21:14 ` [kirkstone][PATCH] " Colin McAllister
2026-02-23 22:32   ` [OE-core] " Yoann Congal
2025-10-06 12:51 Deepesh.Varatharajan
2025-10-06 16:58 ` [OE-core] " Khem Raj
2025-07-29 21:45 [OE-core][kirkstone][PATCH] " Peter Marko
2025-07-30 15:32 ` Steve Sakoman
2025-07-30 20:51   ` Marko, Peter
2025-07-24  7:56 [kirkstone][PATCH] " Deepesh.Varatharajan
2025-07-24 15:58 ` [OE-core] " Khem Raj
2025-05-09  4:30 Deepesh.Varatharajan
2025-05-09  5:07 ` [OE-core] " Khem Raj
2024-05-30  5:17 Deepthi.Hemraj
2024-05-30 15:57 ` Hemraj, Deepthi
2024-05-30 17:29   ` [OE-core] " Khem Raj
2023-09-13 11:18 Sanjana
2023-09-13 17:41 ` [OE-core] " Khem Raj
2023-06-12  9:44 Deepthi Hemraj
2023-06-12  9:58 ` Deepthi.Hemraj
2023-06-12 15:07   ` [OE-core] " Khem Raj
2023-06-13  7:14     ` Hemraj, Deepthi
2023-06-13 13:57       ` Khem Raj

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=f5a1f3e7-e808-4854-892d-49a77b909e64@windriver.com \
    --to=randy.macleod@windriver.com \
    --cc=Deepthi.Hemraj@windriver.com \
    --cc=Stephan.Wolf@kontron-ais.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=ross.burton@arm.com \
    --cc=steve@sakoman.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