RE: [OE-core] [scarthgap][PATCH] glibc: stable 2.39 branch updates

["Marko, Peter" <Peter.Marko@siemens.com>]

> -----Original Message-----
> From: openembedded-core@lists.openembedded.org <openembedded-
> core@lists.openembedded.org> On Behalf Of Yoann Congal via
> lists.openembedded.org
> Sent: Friday, February 6, 2026 7:48
> To: Hemanth.KumarMD@windriver.com; openembedded-
> core@lists.openembedded.org
> Subject: Re: [OE-core] [scarthgap][PATCH] glibc: stable 2.39 branch updates
> 
> Hello,
> 
> On Fri Feb 6, 2026 at 6:24 AM CET, Hemanth.KumarMD via
> lists.openembedded.org wrote:
> > Hello Peter,
> 
> (Yoann here)
> 
> > We sometimes see regressions in glibc test runs depending on the local
> > environment. In such cases, it can help to re-trigger the tests to
> > check whether the failures are consistently reproducible. It may also
> > be useful to cross-check the results with autobuilder runs, which
> > generally provide a more stable baseline before concluding on
> > regressions.

I am planning to run the testsuites again during weekend.
I also find it weird that every update shows different "before" results than previous one showin in "after" result.
Not sure if it's flakiness or local conditions like CPU overload at time of running tests.

> 
> I'm willing to test this on the autobuilder. But I never done that...
> Any pointer? Where do I get the nice test report with the comparison to
> the previous version?

The tests are run via "bitbake glibc-testsuite -c check"

The comparison table is created manually from task logfile.
Basic testcase changes can be extracted from the same file.
New/Removed tests need to be extracted from result files, bit of manual work.

> 
> Thanks!
> --
> Yoann Congal
> Smile ECS