From: "Sanjana V" <sanjanasanju1608@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [mickledore] glibc: stable 2.37 branch updates.
Date: Wed, 11 Oct 2023 23:19:17 -0700 [thread overview]
Message-ID: <20679.1697091557461045335@lists.openembedded.org> (raw)
In-Reply-To: <20231005110207.1582338-1-Yash.Shinde@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 717 bytes --]
Regression testing is done and below are the test results.
Before glibc update
Summary of test results:
PASS:4727
FAIL:240
XPASS:4
XFAIL:16
UNSUPPORTED:220
After glibc update
Summary of test results:
PASS:4729
FAIL:239
XPASS:4
XFAIL:16
UNSUPPORTED:221
These are the newly added test cases
PASS: io/tst-fcntl-lock-lfs
UNSUPPORTED: nss/mtrace-tst-nss-gai-hv2-canonname
And below are new failures
FAIL: nptl/tst-thread-affinity-pthread
FAIL: nptl/tst-thread-affinity-pthread2
FAIL: nptl/tst-thread-affinity-sched
And below are new passes
PASS: malloc/tst-mallocfork3-mcheck
PASS: nptl/tst-pthread-setuid-loop
PASS: resolv/tst-ns_name_length_uncompressed
PASS: string/test-strcasecmp
[-- Attachment #2: Type: text/html, Size: 1148 bytes --]
next prev parent reply other threads:[~2023-10-12 6:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 11:02 [mickledore] glibc: stable 2.37 branch updates Yash.Shinde
2023-10-12 6:19 ` Sanjana V [this message]
2023-10-12 6:25 ` Sundeep KOKKONDA
2023-10-12 14:08 ` [OE-core] " Steve Sakoman
[not found] ` <178D6163664B05A3.21112@lists.openembedded.org>
2023-10-12 14:33 ` Steve Sakoman
2023-10-12 6:32 ` Khem Raj
2023-10-12 12:14 ` Sanjana V
2023-10-12 14:16 ` [OE-core] " Khem Raj
2023-10-19 6:18 ` Sanjana.Venkatesh
2023-10-19 6:28 ` Sanjana.Venkatesh
2023-10-19 6:37 ` Sanjana.Venkatesh
2023-10-19 12:16 ` Sanjana.Venkatesh
2023-10-19 23:02 ` [OE-core] " Khem Raj
2023-10-20 13:52 ` Steve Sakoman
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=20679.1697091557461045335@lists.openembedded.org \
--to=sanjanasanju1608@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.