From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 92FF9CF857D for ; Thu, 3 Oct 2024 11:22:13 +0000 (UTC) Subject: Re: [kirkstone][PATCH] glibc: stable 2.35 branch updates To: openembedded-core@lists.openembedded.org From: "Hemraj, Deepthi" X-Originating-Location: IN (152.58.232.159) X-Originating-Platform: Windows Chrome 129 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Thu, 03 Oct 2024 04:22:10 -0700 References: In-Reply-To: Message-ID: <7336.1727954530167946178@lists.openembedded.org> Content-Type: multipart/alternative; boundary="7xMCHDojRxiYBvTsCuKp" List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Thu, 03 Oct 2024 11:22:13 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/205206 --7xMCHDojRxiYBvTsCuKp Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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 th= e testcase " nptl/tst-thread-affinity-sched.c" passed as expected. Hence, w= e ran the testsuite again after the update and found that the issue was not= reproduced anymore. Please find the following results after the update which has 2 less failure= s 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 --7xMCHDojRxiYBvTsCuKp Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
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 d= ebugging 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 reproduce= d anymore.
Please find the following results after the update which h= as 2 less failures than the results before update.
After Updat= e
PASS - 4781
FAIL - 145
XPASS - 6
XFAIL - 16<= br />UNSUPPORTED - 237

Before update:
PASS - 4770
X= PASS - 6
XFAIL - 16UNSUPPORTED - 237

= Diff:
PASS - +11
FAIL - -3
XPASS - 0
XFAIL - 0
UNSUPPORTED - 0
--7xMCHDojRxiYBvTsCuKp--