From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <richard.purdie@linuxfoundation.org>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] Revert "qemux86-64: Reduce tuning to core2-64"
Date: Mon, 11 Aug 2025 14:44:51 +0200 [thread overview]
Message-ID: <DBZLWMNEMBSO.1REVKMRL4CMZO@bootlin.com> (raw)
In-Reply-To: <20250810222523.2487072-1-richard.purdie@linuxfoundation.org>
On Mon Aug 11, 2025 at 12:25 AM CEST, Richard Purdie via lists.openembedded.org wrote:
> This was originally applied as our autobuilder had older hardware and couldn't
> cope with the newer settings. This has been resolved in the new cluster so we
> can go back to the newer tuning, which software is now more likely to need.
>
> This reverts commit 369b1dfa28b1791d45f068acc765190defecd460.
> ---
Hi Richard,
I believe this is breaking numpy ptests. I'm not sure to understand why,
but git bisect points on this change and it is confirmed by only failing
on x86-64.
Failed ptests:
{'python3-numpy': ['python3.13/site-packages/numpy/_core/tests/test_umath_accuracy.py:TestAccuracy.test_validate_transcendentals']}
https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/2067
https://valkyrie.yocto.io/pub/non-release/20250811-33/testresults/qemux86-64-ptest/core-image-ptest-python3-numpy/
Best regards,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-08-11 12:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-10 22:25 [PATCH] Revert "qemux86-64: Reduce tuning to core2-64" Richard Purdie
2025-08-10 22:41 ` [OE-core] " Khem Raj
2025-08-11 9:25 ` Alexander Kanavin
2025-08-19 9:42 ` Alexander Kanavin
2025-08-11 12:44 ` Mathieu Dubois-Briand [this message]
2025-08-11 18:09 ` Khem Raj
[not found] <185AA85CDF829DFA.24055@lists.openembedded.org>
2025-08-11 8:18 ` Etienne Cordonnier
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=DBZLWMNEMBSO.1REVKMRL4CMZO@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.