From: "Sundeep KOKKONDA" <sundeep.kokkonda@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [scarthgap][PATCH] glibc: stable 2.39 branch updates.
Date: Fri, 17 May 2024 09:33:33 -0700 [thread overview]
Message-ID: <20714.1715963613869990683@lists.openembedded.org> (raw)
In-Reply-To: <20240517162237.3941083-1-sundeep.kokkonda@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
Regression testing is done and below are the results:
Before glibc update:
-------------------------------------------------
Recipe | Passed | Failed | Skipped |
-------------------------------------------------
glibc | 5037 | 123 | 156 |
glibc-user | 4858 | 231 | 227 |
-------------------------------------------------
After glibc update:
-------------------------------------------------
Recipe | Passed | Failed | Skipped |
-------------------------------------------------
glibc | 5043 | 123 | 156 |
glibc-user | 4866 | 229 | 227 |
-------------------------------------------------
ptest shows below tests as failed after glibc update:
tst-malloc-fork-deadlock-malloc-check, tst-robustpi7, tst-thread-affinity-pthread2
[-- Attachment #2: Type: text/html, Size: 2639 bytes --]
next prev parent reply other threads:[~2024-05-17 16:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 16:22 [scarthgap][PATCH] glibc: stable 2.39 branch updates sundeep.kokkonda
2024-05-17 16:33 ` Sundeep KOKKONDA [this message]
2024-05-17 16:48 ` [OE-core] " Khem Raj
2024-05-17 16:53 ` Marko, Peter
2024-05-17 21:09 ` Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2024-07-19 8:28 Deepthi.Hemraj
2024-09-29 16:18 Deepesh.Varatharajan
2024-11-25 8:01 Deepthi.Hemraj
2024-11-25 16:13 ` Khem Raj
2025-05-01 3:03 Deepesh.Varatharajan
2025-07-21 12:23 Deepesh.Varatharajan
2025-10-07 6:31 Deepesh.Varatharajan
2026-01-25 16:16 [OE-core][scarthgap][PATCH] " Peter Marko
2026-02-06 5:24 ` [scarthgap][PATCH] " Hemanth.KumarMD
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=20714.1715963613869990683@lists.openembedded.org \
--to=sundeep.kokkonda@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/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