From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] sagemath: test failures on aarch64
Date: Mon, 11 Dec 2023 01:13:31 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47683@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1283 bytes --]
New issue by dkwo on void-packages repository
https://github.com/void-linux/void-packages/issues/47683
Description:
### Is this a new report?
Yes
### System Info
asahi 6.6 series (apple silicon aarch64)
### Package(s) Affected
sagemath
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
it's important that singular is also rebuilt, as it needs ntl (otherwise, lots of segfaults in sage tests).
### Expected behaviour
pass the testsuite
### Actual behaviour
```
sage -t --warn-long 9.9 --random-seed=152816534303222946788861922984252620675 /usr/lib/python3.12/site-packages/sage/misc/persist.pyx # 2 doctests failed
sage -t --warn-long 9.9 --random-seed=152816534303222946788861922984252620675 /usr/lib/python3.12/site-packages/sage/misc/inline_fortran.py # 3 doctests failed
sage -t --warn-long 9.9 --random-seed=152816534303222946788861922984252620675 /usr/lib/python3.12/site-packages/sage/repl/ipython_extension.py # 4 doctests failed
```
full test output https://paste.c-net.org/CahootsUnicorn or
[sage-test-fail.log](https://github.com/void-linux/void-packages/files/13629727/sage-test-fail.log)
### Steps to reproduce
```
./xbps-pkg singular
./xbps-pkg sagemath
xi singular sagemath
`sage -t --all`
```
next reply other threads:[~2023-12-11 0:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 0:13 dkwo [this message]
2023-12-11 0:18 ` dkwo
2023-12-11 1:11 ` tornaria
2023-12-11 1:21 ` dkwo
2023-12-11 1:22 ` dkwo
2023-12-12 16:22 ` [ISSUE] [CLOSED] sagemath: test failures dkwo
2023-12-12 16:22 ` dkwo
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-47683@inbox.vuxu.org \
--to=dkwo@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).