Hi,
almost everything works installed from scratch with recommended system
packages on manjaro.
I get some doctests failures
sage -t --long --warn-long 58.0
--random-seed=56439470687750385659257200164528769383
src/sage/interfaces/four_ti_2.py # 5 doctests failed
Which are just deprecation
Thanks Volker for preparing the release.
All tests pass on debian buster, except
sage -t --long --random-seed=146168601452887490256495561253701871534
src/sage/tests/cmdline.py # 3 doctests failed
as squlite executable is not
Build gets stuck on debian buster. `make sdist-clean` did not help.
After pressing Ctrl + C it seems fine.
Jonathan
For some reason I can't attach a file anymore, so the config.log is here
http://page.mi.fu-berlin.de/kliem/config.log
[sagenb_export-3.3] INFO: This is taking longer than usual.
This problem has already been resolved in
https://trac.sagemath.org/ticket/32031.
setuptools currently removes setuptools_scm without triggering a rebuild.
So I would recommond
make setuptools_scm-clean
to fix this.
emanuel.c...@gmail.com schrieb am Sonntag, 27. Juni 2021 um 13:49:28 UTC+2:
Just for completeness. You can just fix this with
make setuptools_scm-clean
The patch in https://trac.sagemath.org/ticket/32031 will fix the underlying
problem so that this won't be needed in the future.
Dima Pasechnik schrieb am Dienstag, 22. Juni 2021 um 22:04:56 UTC+2:
> On Tue, Jun 22,
Thanks Volker for the new release.
Unfortunatly, installation fails for me due to mpmath
https://trac.sagemath.org/ticket/31564 and py
https://trac.sagemath.org/ticket/30416.
Both of them require setuptools-scm in the setup.py (no pyproject.toml),
but do not pick up our setuptools_scm
Oh yes, you probably have too few sucessful tests
I would propose to change this (init_warn_long) to set
self.optioins.warn_long = 60
in case of this RuntimeError
jonatha...@googlemail.com schrieb am Dienstag, 16. Februar 2021 um 19:27:39
UTC+1:
> Here is what I think is relevant
>
> in
Here is what I think is relevant
in control.py
431 def _init_warn_long(self):
432 + 23 lines:
"""
455 if
Yes.
Long time ago, I created a list of known failures when using some system
packages (most of them are taken care of by now and new ones came up,
however this one is old):
https://trac.sagemath.org/ticket/27122#comment:40
>From this you see that this is ticket 29092:
I opened https://trac.sagemath.org/ticket/30958 for the C99 thing that
caused the following:
The first one is new, I think. File "src/sage/graphs/connectivity.pyx",
line 2686, in sage.graphs.connectivity._Component.__init__
Failed example:
cython(os.linesep.join(cython_code))
[...]
Thank you Samuel for your reply.
I know nothing about windows and I have been amazed by the fact that the
windows binaries are produced somehow. In that way, it doesn't surprise me
that they are not just produced somehow, but a decent effort is put into
it. I just never looked into it, because
There no windows binaries for 9.2 yet. Maybe there is a reason for it, but
I should wanted to post that.
http://mirror.aarnet.edu.au/pub/sage/win/index.html
jaap...@gmail.com schrieb am Mittwoch, 28. Oktober 2020 um 22:51:36 UTC+1:
> On Raspberry Pi OS 64 bit build ok with the "usual" test
On ubuntu bionic incremental build of and dateutils fail.
Those are the logs:
Found local metadata for zipp-0.5.2
2 Attempting to download package zipp-0.5.2.tar.gz from mirrors
3 https://mirror.koddos.net/sagemath/spkg/upstream/zipp/zipp-0.5.2.tar.gz
4
pynormaliz 2.12 isn't on the mirrors yet
(I can work around that)
Dima Pasechnik schrieb am Montag, 7. September 2020 um 13:20:34 UTC+2:
> please also send the top-level config.log
> Otherwise it is not clear how to reproduce this, e.g. what Python is used.
>
> On Mon, Sep 7, 2020 at 10:09 AM
I'm responsible for some ridiculous long doctests in
`src/sage/geometry/polyhedron/library.py`.
https://trac.sagemath.org/ticket/30489 is a two line ticket (positive
review), which should take care of the time out.
https://trac.sagemath.org/ticket/30490 reduces the doctesting time a bit
more
I have create https://trac.sagemath.org/ticket/30427 for the memory leak in
divisors of integers.
jonatha...@googlemail.com schrieb am Freitag, 21. August 2020 um 09:08:44
UTC+2:
> I can confirm the rings/integer.pyx failure from running it in the shell.
>
> sage: n = prod(primes_first_n(25))
I can confirm the rings/integer.pyx failure from running it in the shell.
sage: n = prod(primes_first_n(25))
sage: _ = n.divisors()
If I cancel the second line many time (after a few seconds each), I see an
increase in memory usage.
There doesn't seem to be a limit to it.
I can immitate the
17 matches
Mail list logo