From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: sagemath: rebuild for dep updates and fixes
Date: Fri, 03 Feb 2023 02:29:01 +0100 [thread overview]
Message-ID: <20230203012901.-JyRV0Va0BNor_1PMqoeEkh5h2J6l0ppPqO0cxtWAqg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42048@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1943 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/42048#issuecomment-1414588622
Comment:
So `x86_64` (both glibc and musl) failed with this:
```
sage -t --warn-long 30.0 --random-seed=0 /builddir/sagemath-9.7/pkgs/sagemath-standard/build/lib.linux-x86_64-cpython-311/sage/interfaces/expect.py
**********************************************************************
File "/builddir/sagemath-9.7/pkgs/sagemath-standard/build/lib.linux-x86_64-cpython-311/sage/interfaces/expect.py", line 937, in sage.interfaces.expect.Expect._eval_line
Failed example:
singular.interrupt()
Expected:
True
Got:
False
**********************************************************************
File "/builddir/sagemath-9.7/pkgs/sagemath-standard/build/lib.linux-x86_64-cpython-311/sage/interfaces/expect.py", line 943, in sage.interfaces.expect.Expect._eval_line
Failed example:
singular('2+3')
Expected:
Singular crashed -- automatically restarting.
5
Got:
5
**********************************************************************
1 item had failures:
2 of 16 in sage.interfaces.expect.Expect._eval_line
[101 tests, 2 failures, 23.40 s]
```
It has already happened before (https://github.com/void-linux/void-packages/pull/39876#issuecomment-1274649461, https://github.com/void-linux/void-packages/pull/41085#issuecomment-1351712588).
This was already known upstream (https://trac.sagemath.org/ticket/33907) and it turns out I already fixed this (it's even merged upstream for 9.8!) but I forgot. This only happens under very heavy load (as here in CI, but not in my box even if I run 16 threads on 8 cores, it has to be way more loaded to trigger)
I'll push a new PR with the patch from https://git.sagemath.org/sage.git/commit?id=6f5c1c2fc8bcfb5e6555716d05ce70511795ffa1.
Meanwhile my local tests with all the above PR together are successful.
next prev parent reply other threads:[~2023-02-03 1:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 22:54 [PR PATCH] Sagemath tornaria
2023-02-02 23:07 ` sagemath: rebuild for dep updates and fixes tornaria
2023-02-02 23:16 ` [PR PATCH] [Updated] " tornaria
2023-02-03 1:29 ` tornaria [this message]
2023-02-03 1:33 ` tornaria
2023-02-03 23:42 ` tornaria
2023-02-04 1:04 ` tornaria
2023-02-04 1:38 ` tornaria
2023-02-04 11:47 ` [PR PATCH] [Updated] " tornaria
2023-02-05 14:00 ` tornaria
2023-02-05 14:00 ` tornaria
2023-02-05 14:42 ` [PR PATCH] [Updated] " tornaria
2023-02-05 14:56 ` tornaria
2023-02-06 2:54 ` [PR PATCH] [Updated] " tornaria
2023-02-06 12:43 ` tornaria
2023-02-06 21:23 ` dkwo
2023-02-06 21:24 ` dkwo
2023-02-06 21:39 ` tornaria
2023-02-06 23:37 ` dkwo
2023-02-06 23:42 ` dkwo
2023-02-07 16:47 ` dkwo
2023-02-13 15:58 ` tornaria
2023-02-13 16:08 ` dkwo
2023-02-13 18:31 ` [PR PATCH] [Updated] " tornaria
2023-02-14 0:11 ` tornaria
2023-02-14 0:17 ` tornaria
2023-02-14 13:03 ` [PR PATCH] [Updated] sagemath: update to 9.8 tornaria
2023-02-14 13:05 ` tornaria
2023-02-15 13:19 ` tornaria
2023-02-15 13:32 ` [PR PATCH] [Merged]: " leahneukirchen
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=20230203012901.-JyRV0Va0BNor_1PMqoeEkh5h2J6l0ppPqO0cxtWAqg@z \
--to=tornaria@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).