Fixed in #34557

https://trac.sagemath.org/ticket/34557

which needs review.

On Monday, September 19, 2022 at 5:38:59 PM UTC+9 Clemens Heuberger wrote:

> On most of my machines, ptestlong passes (except for the usual transient 
> failures in src/sage/interfaces/process.pyx ). 
>
> However, on one machine, where there has not been any problem with 
> 9.7.rc1, I 
> consistently get the doctest failure below. It seems to depend on the 
> random 
> seed; with another seed (270396188935382102109749143081031101710), the 
> doctest 
> passes. 
>
> ==== 
>
> $ ./sage -t --long --warn-long 162.9 
> --random-seed=106591066711905509746265618740333072762 
> src/sage/rings/polynomial/polynomial_element.pyx 
> Running doctests with ID 2022-09-19-10-22-38-e10a920f. 
> Running with SAGE_LOCAL='/local/cheuberg/local/sage-9.7.rc2/local' and 
> SAGE_VENV='/local/cheuberg/local/sage-9.7.rc2/local/var/lib/sage/venv-python3.10.5'
>  
>
> Using --optional=ccache,debian,pip,sage,sage_spkg 
> Features to be detected: 
> 4ti2,benzene,bliss,buckygen,conway_polynomials,csdp,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_cubic_hecke,database_jones_numfield,database_knotinfo,dvipng,gfan,graphviz,imagemagick,jupymake,kenzo,latte_int,lrslib,mcqd,meataxe,msolve,nauty,palp,pandoc,pdf2svg,pdftocairo,phitigra,plantri,polytopes_db,polytopes_db_4d,pynormaliz,python_igraph,rubiks,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.groups,sage.misc.cython,sage.plot,sage.rings.number_field,sage.rings.padics,sage.rings.real_double,sage.symbolic,sage_numerical_backends_coin,sagemath_doc_html,sphinx,tdlib
>  
>
> Doctesting 1 file. 
> sage -t --long --warn-long 162.9 
> --random-seed=106591066711905509746265618740333072762 
> src/sage/rings/polynomial/polynomial_element.pyx 
> ********************************************************************** 
> File "src/sage/rings/polynomial/polynomial_element.pyx", line 11653, in 
> sage.rings.polynomial.polynomial_element.Polynomial_generic_dense.quo_rem 
> Failed example: 
> f.quo_rem(g) 
> Expected: 
> Traceback (most recent call last): 
> ... 
> ArithmeticError: division non exact (consider coercing to polynomials over 
> the fraction field) 
> Got: 
> (-7*y^5 + 1/4*y^2 + (-1/2*x + 1/2)*y, 
> 11/2*y^4 + (-x^2 - 1/3*x + 2/3)*y^3 - 1/3*y^2 - y - 1) 
> ********************************************************************** 
> 1 item had failures: 
> 1 of 24 in 
> sage.rings.polynomial.polynomial_element.Polynomial_generic_dense.quo_rem 
> [2716 tests, 1 failure, 8.97 s] 
> ---------------------------------------------------------------------- 
> sage -t --long --warn-long 162.9 
> --random-seed=106591066711905509746265618740333072762 
> src/sage/rings/polynomial/polynomial_element.pyx # 1 doctest failed 
> ---------------------------------------------------------------------- 
> Total time for all tests: 19.3 seconds 
> cpu time: 8.8 seconds 
> cumulative wall time: 9.0 seconds 
> Features detected for doctesting: 
> pytest is not installed in the venv, skip checking tests that rely on it 
>
>
> Am 17.09.22 um 13:04 schrieb Volker Braun: 
> > As always, you can get the latest beta version from the "develop" git 
> branch. 
> > Alternatively, the self-contained source tarball is at 
> > http://www.sagemath.org/download-latest.html 
> > 
> > This should be the last rc... 
> > 
> > 59ac11a9375 (tag: 9.7.rc2, trac/develop) Updated SageMath version to 
> 9.7.rc2 
> > 4f225f4cc66 (origin/develop) Trac #34533: OS X 12.6 "chained fixups" 
> warning 
> > e421c55fafd Trac #34506: Override the arbitrary limit on number of 
> digits 
> > printed (Python 3.10.7) 
> > 08202bc1ba7 (tag: 9.7.rc1) Updated SageMath version to 9.7.rc1 
> > 
> > 
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/abfb8851-3171-43d7-999b-91cd3d06852en%40googlegroups.com.

Reply via email to