Github messages for voidlinux
 help / color / mirror / Atom feed
From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: DRAFT: sagemath update to 9.7
Date: Sat, 29 Oct 2022 18:55:32 +0200	[thread overview]
Message-ID: <20221029165532.bhK2QErL0vLC5UuLXqdyqiMFdKpk68GIQOFVCGXsb8k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39876@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 3206 bytes --]

New comment by tornaria on void-packages repository

https://github.com/void-linux/void-packages/pull/39876#issuecomment-1295901019

Comment:
I'm not sure what  went wrong with i686. All started with
```
sage -t --warn-long 30.0 --random-seed=0 /builddir/sage-9.7/pkgs/sagemath-standard/build/lib.linux-x86_64-cpython-310/sage/manifolds/differentiable/pseudo_riemannian_submanifold.py
**********************************************************************
File "/builddir/sage-9.7/pkgs/sagemath-standard/build/lib.linux-x86_64-cpython-310/sage/manifolds/differentiable/pseudo_riemannian_submanifold.py", line 26, in sage.manifolds.differentiable.pseudo_riemannian_submanifold
Failed example:
    E.<w,x,y> = M.chart()
Exception raised:
    Traceback (most recent call last):
      File "sage/symbolic/expression.pyx", line 13959, in sage.symbolic.expression.send_sage_domain_to_maxima (build/cythonized/sage/symbolic/expression.cpp:104209)
        assume(v, 'real')
      File "/builddir/sage-9.7/pkgs/sagemath-standard/build/lib.linux-x86_64-cpython-310/sage/symbolic/assumptions.py", line 676, in assume
        x.assume()
      File "/builddir/sage-9.7/pkgs/sagemath-standard/build/lib.linux-x86_64-cpython-310/sage/symbolic/assumptions.py", line 249, in assume
        self._validate_feature()
      File "/builddir/sage-9.7/pkgs/sagemath-standard/build/lib.linux-x86_64-cpython-310/sage/symbolic/assumptions.py", line 219, in _validate_feature
        _valid_feature_strings.update(repr(x).strip() for x in list(maxima("features")))
      File "sage/misc/lazy_import.pyx", line 391, in sage.misc.lazy_import.LazyImport.__call__ (build/cythonized/sage/misc/lazy_import.c:4393)
        return self.get_object()(*args, **kwds)
      File "sage/misc/lazy_import.pyx", line 216, in sage.misc.lazy_import.LazyImport.get_object (build/cythonized/sage/misc/lazy_import.c:2674)
        return self._get_object()
      File "sage/misc/lazy_import.pyx", line 252, in sage.misc.lazy_import.LazyImport._get_object (build/cythonized/sage/misc/lazy_import.c:2998)
        self._object = getattr(__import__(self._module, {}, {}, [self._name]), self._name)
      File "/builddir/sage-9.7/pkgs/sagemath-standard/build/lib.linux-x86_64-cpython-310/sage/interfaces/maxima_lib.py", line 119, in <module>
        ecl_eval("(set-pathnames)")
      File "sage/libs/ecl.pyx", line 1352, in sage.libs.ecl.ecl_eval (build/cythonized/sage/libs/ecl.c:10922)
        cpdef EclObject ecl_eval(str s):
      File "sage/libs/ecl.pyx", line 1375, in sage.libs.ecl.ecl_eval (build/cythonized/sage/libs/ecl.c:10855)
        o=ecl_safe_eval(python_to_ecl(s, True))
      File "sage/libs/ecl.pyx", line 321, in sage.libs.ecl.ecl_safe_eval (build/cythonized/sage/libs/ecl.c:5637)
        raise RuntimeError("ECL says: {}".format(message))
    RuntimeError: ECL says: Could not create directory "/tmp/.sage/maxima/binary"
    C library error: "File exists"
```
Probably a race condition, since CI is doctesting using 2 threads. More doctest failures after this are all caused by `E` not being defined, etc.

I don't think we should delay this PR for this (maybe someone can restart that test to be sure).

  parent reply	other threads:[~2022-10-29 16:55 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-10 22:19 [PR PATCH] " tornaria
2022-10-11 12:58 ` tornaria
2022-10-11 13:51 ` dkwo
2022-10-11 14:33 ` ahesford
2022-10-11 19:13 ` tornaria
2022-10-11 19:23 ` ahesford
2022-10-11 21:35 ` [PR PATCH] [Updated] " tornaria
2022-10-11 21:37 ` tornaria
2022-10-12 14:46 ` [PR PATCH] [Updated] " tornaria
2022-10-12 18:18 ` dkwo
2022-10-12 18:18 ` dkwo
2022-10-12 20:17 ` tornaria
2022-10-12 22:02 ` dkwo
2022-10-13  3:15 ` [PR PATCH] [Updated] " tornaria
2022-10-13 14:03 ` tornaria
2022-10-14 20:11 ` tornaria
2022-10-16  1:52 ` tornaria
2022-10-17  4:51 ` tornaria
2022-10-29  2:30 ` tornaria
2022-10-29 11:02 ` tornaria
2022-10-29 11:12 ` ahesford
2022-10-29 12:16 ` [PR PATCH] [Updated] " tornaria
2022-10-29 16:55 ` tornaria [this message]
2022-10-29 16:58 ` sagemath: " tornaria
2022-10-30 17:09 ` tornaria
2022-10-30 22:06 ` [PR PATCH] [Updated] " tornaria
2022-10-30 23:37 ` tornaria
2022-10-31 11:56 ` tornaria
2022-10-31 14:40 ` dkwo
2022-10-31 15:27 ` [PR PATCH] [Closed]: " ahesford
2022-10-31 15:37 ` ahesford
2022-10-31 20:30 ` tornaria
2022-11-03 13:36 ` tornaria
2022-11-03 13:59 ` 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=20221029165532.bhK2QErL0vLC5UuLXqdyqiMFdKpk68GIQOFVCGXsb8k@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).