Closed strogdon closed 2 years ago
sage -t --long --warn-long 96.7 --random-seed=323793429833434243810534467855837341563 /usr/lib/python3.10/site-packages/sage/schemes/toric/sheaf/klyachko.py
also fails on s-o-g but
sage -t --long /usr/lib/python3.10/site-packages/sage/schemes/toric/sheaf/klyachko.py
selects the random-seed
sage -t --long --warn-long 92.2 --random-seed=303102343567653614112271349982422554511 /usr/lib/python3.10/site-packages/sage/schemes/toric/sheaf/klyachko.py
[151 tests, 6.90 s]
----------------------------------------------------------------------
All tests passed!
That needs a post on sage-devel. It looks like you have found a particular case that needs to be studied.
It looks like random-seed
is not a done deal. See
https://trac.sagemath.org/ticket/32773 https://trac.sagemath.org/ticket/29935 https://trac.sagemath.org/ticket/32544
It does exactly what it's supposed to do. Find bugs.
I learned something about random-seed
.
This is on vanilla but I'm sure the phenomenon exist on s-o-g. Sage automatically sets the
random-seed
when doctesting. When running the testsuite I have the failurewhich I can replicate by running the test individually using the indicated
random-seed
. However running the test individually asSage selects a new
random-seed
and the test passesAny idea what's up?