From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Reproducible but not universal breakage with openblas 0.3.19 and numpy/scipy
Date: Thu, 23 Dec 2021 05:47:02 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34673@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
New issue by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/34673
Description:
This issue tracks the issue described in 722054111e50649f3381906c9a646f44adb5cc02:
>Python code built around python3-numpy and python3-scipy (both linked with openblas) began emitting warnings after the 0.3.19 update:
>```python
> /usr/lib/python3.10/concurrent/futures/thread.py:58:
> RuntimeWarning: overflow encountered in multiply
> result = self.fn(*self.args, **self.kwargs)
>```
>
>that broke program behavior in an Azure VM environment using Intel Xeon Platinum 8272CL CPUs; the problem was not seen on an AMD Ryzen 5 3600 or an Intel Core i7-9750H. Downgrading openblas while leaving the rest of the stack untouched eliminates the problem.
>
>Unfortunately, I do not yet have a proof of concept that can be shared publicly or more detail about the specific failure, but let's revert to the last known good version until a specific cause can be identified.
next reply other threads:[~2021-12-23 4:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 4:47 ahesford [this message]
2021-12-23 14:32 ` ahesford
2022-06-20 2:13 ` github-actions
2023-06-27 20:34 ` [ISSUE] [CLOSED] " ahesford
2023-06-27 20:34 ` ahesford
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34673@inbox.vuxu.org \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).