From: Sam James <sam@gentoo.org>
To: distributions@lists.linux.dev
Subject: Possible issues with arpack-3.9.0
Date: Sun, 02 Apr 2023 19:46:13 +0100 [thread overview]
Message-ID: <87zg7qt90v.fsf@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 722 bytes --]
Hi folks,
I came across this a week or so ago and it came back to mind because of
the openblas kerfuffle [0].
arpack-3.9.0 will in some cases give deterministic failure as the
randomness in the retry mechanism seems busted.
This can cause e.g. igraph's test suite to fail.
References:
- https://github.com/opencollab/arpack-ng/issues/401
- https://github.com/opencollab/arpack-ng/issues/410
Ths discussion is quite long and the second bug linked tries
to summarise it. It's complicated and for now I've just yanked
arpack-3.9.0 in Gentoo (masked it).
[0] https://lore.kernel.org/distributions/CAE6_+UeiCzpyA9-XVgX1x5Ucjccng0rdw-+WCZbtMnLX8VOKgQ@mail.gmail.com/T/#m6ed52b95d975ae3b047f5704e6f2cc9914e112fe
best,
sam
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]
reply other threads:[~2023-04-02 18:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87zg7qt90v.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=distributions@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).