On debian testing (buster) no problem when updating from 10.0.
A question:
- since some months (?) I always configure "without system singular"
( ./configure --without-system-singular ), as singular in debian testing
changed to a recent version.
* Is it always necessary ? (yes, I think...)
On Debian testing, upgrading 10.0 to 10.0.beta1 and running ptestlong gibes the three permanent failures reported for 10.0 :
sage -t --long --warn-long 196.8 --random-seed=74389171265200921011491634830844765513 src/sage/coding/linear_code.py # 2 doctests failed sage -t --long --warn-long 196.8 --random-seed=74389171265200921011491634830844765513 src/sage/coding/code_constructions.py # 1 doctest failed sage -t --long --warn-long 196.8 --random-seed=74389171265200921011491634830844765513 src/sage/repl/ipython_kernel/kernel.py # 1 doctest failedI can confirm that the third one is indeed a local issue.
HTH,
----------------------------------------------------------------------
sage -t --long --warn-long 227.1 --random-seed=137852481551826196838278081478820577572 src/sage/rings/polynomial/multi_polynomial_ideal.py # Killed due to segmentation fault
sage -t --long --warn-long 227.1 --random-seed=137852481551826196838278081478820577572 src/sage/libs/giac/__init__.py # Timed out
sage -t --long --warn-long 227.1 --random-seed=137852481551826196838278081478820577572 src/sage/modular/modform_hecketriangle/readme.py # 1 doctest failed
sage -t --long --warn-long 227.1 --random-seed=137852481551826196838278081478820577572 src/sage/modular/modform_hecketriangle/abstract_space.py # 3 doctests failed
sage -t --long --warn-long 227.1 --random-seed=137852481551826196838278081478820577572 src/sage/modular/modform_hecketriangle/space.py # 2 doctests failed
----------------------------------------------------------------------
25/05/2023 12:26、Emmanuel Charpentier <emanuel.c...@gmail.com>のメール:
--
You received this message because you are subscribed to the Google Groups "sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/7de385b1-9952-4985-8112-222f78a80632n%40googlegroups.com.