From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Harish.Sadineni@windriver.com, openembedded-core@lists.openembedded.org
Cc: Randy.MacLeod@windriver.com, Naveen.Gowda@windriver.com,
Sundeep.Kokkonda@windriver.com,
Shivaprasad.Moodalappa@windriver.com
Subject: Re: [OE-core] [PATCH 1/2] gcc: Oe-selftest failure analysis - fix for host key verfication & kex exchange identification failures
Date: Thu, 25 Apr 2024 13:35:52 +0100 [thread overview]
Message-ID: <9e2d9685c9d39d04cc58ae3f8a9e24cdf4b9d8ea.camel@linuxfoundation.org> (raw)
In-Reply-To: <20240418105051.2559536-1-Harish.Sadineni@windriver.com>
I did compare a build with this patch in it with the 5.0 rc4 test
report:
http://autobuilder.yocto.io/pub/non-release/20240424-25/testresults/testresult-report.txt
vs
http://autobuilder.yocto.io/pub/releases/yocto-5.0.rc4/testreport.txt
which shows:
gcc | 149932 | 15 | 27534 | 1548
gcc-g++ | 219372 | 22 | 21074 | 1350
gcc-libatomic | 27 | 0 | 27 | 513
gcc-libgomp | 3428 | 0 | 1960 | 582
gcc-libitm | 24 | 0 | 24 | 430
gcc-libstdc++-v3 | 9722 | 0 | 5447 | 2202
vs
gcc | 149794 | 31 | 27672 | 1446
gcc-g++ | 219325 | 31 | 21128 | 1100
gcc-libatomic | 27 | 1 | 27 | 517
gcc-libgomp | 3411 | 15 | 1977 | 782
gcc-libitm | 24 | 1 | 24 | 397
gcc-libstdc++-v3 | 9705 | 32 | 5464 | 2669
so I'm not sure this is fixing the large number of skipped tests that
it is supposed to fix?
Cheers,
Richard
next prev parent reply other threads:[~2024-04-25 12:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 10:50 [PATCH 1/2] gcc: Oe-selftest failure analysis - fix for host key verfication & kex exchange identification failures Harish.Sadineni
2024-04-18 10:50 ` [PATCH 2/2] gcc: Oe-selftest failure analysis - allowing multiple ssh sessions Harish.Sadineni
2024-04-18 11:00 ` Sadineni, Harish
2024-04-18 10:57 ` [PATCH 1/2] gcc: Oe-selftest failure analysis - fix for host key verfication & kex exchange identification failures Sadineni, Harish
2024-04-18 11:07 ` Patchtest results for " patchtest
2024-04-25 12:07 ` [OE-core] " Richard Purdie
2024-04-25 12:35 ` Richard Purdie [this message]
2024-07-16 18:20 ` Sadineni, Harish
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=9e2d9685c9d39d04cc58ae3f8a9e24cdf4b9d8ea.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Harish.Sadineni@windriver.com \
--cc=Naveen.Gowda@windriver.com \
--cc=Randy.MacLeod@windriver.com \
--cc=Shivaprasad.Moodalappa@windriver.com \
--cc=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