Sage 8.3.beta1 released

203 views
Skip to first unread message

Volker Braun

unread,
May 14, 2018, 2:10:54 PM5/14/18
to sage-release
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

6fc1e20c66 (tag: 8.3.beta1) Updated SageMath version to 8.3.beta1
8c327b9901 Trac #25258: Gurobi breaks lots of doctests in make ptestlong
47a7327e12 Trac #25248: py3: fix sage.parallel.map_reduce
7feb4d298c Trac #25244: LatticePoset: Add is_interval_dismantlable
3e6075d57b Trac #25236: Deprecate various functions from old coercion model
c4b415fa9f Trac #25235: q-Stirling numbers of the second kind
2c90815686 Trac #25224: Mismatch in the definition of dilog() between fricas and sympy
3ab97b15d3 Trac #25223: Cleaning of the usage of BFS
bf0beabf6a Trac #25220: fix definite fricas integration
88e1ed6d0e Trac #25216: py3: fix bytes handling bugs in sage.plot.animate
deae517486 Trac #25211: code should not depend ordering of codegrees
eb2f271af2 Trac #25203: Speed up FiniteField.zeta()
22b8be8a05 Trac #25201: Use super() in MatrixSpace.__getitem__
9a7f40d097 Trac #25200: Incorrect long element for signed permutations
eba77d3f14 Trac #25195: py3: fix segfault in element wrapper on Python 3
f5527d2184 Trac #25192: primitivity test for integral matrices
b3b4f75048 Trac #25186: Use ZZ.random_element for random_prime
7e6c6ab9e5 Trac #25182: coherent output type for polynomial.degree()
6a2222afae Trac #25174: conversion of I to fricas is wrong
6a34919efb Trac #25169: py3: fixing print in sage-starts script
80d4a17edc Trac #25161: Sphinx build hangs when a BaseException occurs
6f130ae999 Trac #25146: Cleanup of AbstractPartitionDiagram
41c9fffbe1 Trac #24966: package primecount 4.3
72980a10a1 Trac #24890: Tensor product of lattices
951fa49129 Trac #24460: py3: fixes to sage.libs.gap
e5af4884cc Trac #15508: Implement Fock space
4756f04cbe Trac #25335: Missing imports in src/sage/geometry/polyhedron/base.py
faad356119 Trac #25133: Implement WQSym
b593af3371 Trac #25132: Define the class of SuperPartitions
c1a36a02ee Trac #25131: FQSym: add G basis
ad72cec5b8 Trac #25128: Have py_scalar_to_element convert gmpy2 numbers
81f7d7a341 Trac #25121: fix edge color format in graphviz_string
8821bb1454 Trac #25120: dot2tex edge coloring is broken
80fa1be913 Trac #25117: some pyflakes cleanup for unused variables
fd8c5d4676 Trac #25112: perl_term_readline_gnu: Upgrade to 1.35 and patch away ncurses problem
bf6cbafbed Trac #25109: Upgrade cmake to 3.11.0
07ce7c88bf Trac #25105: ell_number_field.py takes a long time to test
bb996e69ec Trac #25098: Fix LaTeX usage in Rings documentation
eecf07e8c7 Trac #25095: polygon3d ignores the "alpha" (and equivalent "opacity") argument
15b5aa2b60 Trac #25081: The polar of a polyhedron should carry the backend used.
62a893aba3 Trac #25080: code for Cartesian factorization of posets
89ec1fb5c2 Trac #25075: pyflakes cleanup in combinat
329c579bac Trac #25074: upgrade to ipywidgets 7.2.0
a5122d141e Trac #25067: Implement quantum group q-numbers
054122ae77 Trac #25065: partition input is ignored when casting DiGraph as BipartiteGraph
09f6b467c5 Trac #25064: more conversions from http to https
7f5a1dad2b Trac #25063: py3: get rid of __cmp__ in interfaces
430abb3957 Trac #25062: another typo ticket, yet
ae77a27f60 Trac #25061: Replace MatrixFactory.__call__ by an ordinary function
920bfc0f16 Trac #25060: py3: more rich comparison for multivariate polynomials
eec16d96bd Trac #25059: py3: get rid of some  __cmp__ in string monoids
d7b39179bc Trac #25058: corrections to input for posets
7993a2d1d3 Trac #25053: py3: remove __cmp__ in free monoids
6513b621f8 Trac #25052: Add DESTDIR support for openblas
ab02054314 Trac #25042: Add DESTDIR support for freetype
bc875efff0 Trac #15597: Quasi-shuffle product
670713abd7 Trac #25129: Fix "offline" viewing of threejs plots on Cygwin
6cfeb59db4 Trac #25038: Use sage-dist-helpers for curl and gc
235703c6da Trac #25037: Add destdir support and other cleanup for ntl
fbcf50432c Trac #25036: Code cleanup in plot3d
a698014552 Trac #25023: Adds function to compute quadratic defect
1f7f75b42f Trac #25022: change_ring broken on polynomials
f997efffd1 Trac #25018: Bug in shuffle product `ShuffleProduct_w1w2`
1c38098666 Trac #25016: Add PyCygwin as a standard package
8e27ccc8b4 Trac #25014: Twist of a TorsionQuadraticModule
05f9233d0b Trac #25008: Additional method "matrix" / "_matrix_" for the element class of ClassicalMatrixLieAlgebra
dd67e2ab57 Trac #25007: Bug in to_vector-method of ClassicalMatrixLieAlgebra class
414df4185c Trac #25002: Ear Decomposition
2482fdfa30 Trac #24998: py3: incorporate a tab completion function from sagenb
bee19a8a90 Trac #24985: py3: some fixes in designs
f38ace4016 Trac #24969: Upgrade to R 3.4.4
f6b90f97f0 Trac #24957: make Expect._before() wrap bytes_to_str
6c423c10af Trac #24954: Stronger references in CachedRepresentation
a2aaf421a8 Trac #24952: Speed up SR(Integer/Rational)
65738dfe7c Trac #24951: Use nauty as the default generator for graphs
3d4ac5219b Trac #24948: enhanced sage-list-packages
a590345172 Trac #24925: Ford Fulkerson algorithm does not handle unconnected vertices correctly + unclear error message + lacks tests
8bdc326ba5 (tag: 8.3.beta0) Updated SageMath version to 8.3.beta0

Emmanuel Charpentier

unread,
May 15, 2018, 8:46:00 AM5/15/18
to sage-release
FWIW : on Debian testing running on Core i7 + 16 GB RAM, same results as for 8.3.beta0, i. e. one transient and two permanent errors (the same as before) :

----------------------------------------------------------------------
sage -t --long src/sage/rings/padics/padic_lattice_element.py  # Timed out
sage -t --long src/sage/groups/perm_gps/permgroup.py  # 1 doctest failed
sage -t --long src/sage/features/gap.py  # 1 doctest failed
----------------------------------------------------------------------

HTH,

--
Emmanuel Charpentier

Erik Bray

unread,
May 15, 2018, 10:13:17 AM5/15/18
to sage-r...@googlegroups.com
Thanks for the release.

On Ubuntu 14.04 I get LOTS of test timeouts that I didn't get
previously. It's possible though that the system is just uder heavy
load, but even re-running the tests with --failed keeps giving me
timeouts for some modules. So I'm concerned about a real performance
regression somewhere. I'm running ./sage -t -a --failed yet again,
but from my last run I got:

sage -t src/sage/libs/gap/all_documented_functions.py # Timed out
sage -t src/sage/libs/gap/assigned_names.py # Timed out
sage -t src/sage/manifolds/differentiable/affine_connection.py # Timed out
sage -t src/sage/manifolds/differentiable/euclidean.py # Timed out
sage -t src/sage/manifolds/differentiable/metric.py # Timed out
sage -t src/sage/manifolds/differentiable/multivectorfield.py # Timed out
sage -t src/sage/manifolds/differentiable/tensorfield.py # Timed out
sage -t src/sage/plot/plot.py # Timed out
sage -t src/sage/rings/padics/padic_base_leaves.py # Timed out
sage -t src/sage/rings/padics/padic_lattice_element.py # Timed out
(and interrupt failed)


Will try 16.04 (the current base for my Docker images) and 18.04 next.
> --
> 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 post to this group, send email to sage-r...@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

John Cremona

unread,
May 15, 2018, 11:12:53 AM5/15/18
to sage-r...@googlegroups.com
On 15 May 2018 at 15:13, Erik Bray <erik....@gmail.com> wrote:
Thanks for the release.

On Ubuntu 14.04 I get LOTS of test timeouts that I didn't get
previously.  It's possible though that the system is just uder heavy
load, but even re-running the tests with --failed keeps giving me
timeouts for some modules.  So I'm concerned about a real performance
regression somewhere.  I'm running ./sage -t -a --failed yet again,
but from my last run I got:

sage -t src/sage/libs/gap/all_documented_functions.py  # Timed out
sage -t src/sage/libs/gap/assigned_names.py  # Timed out
sage -t src/sage/manifolds/differentiable/affine_connection.py  # Timed out
sage -t src/sage/manifolds/differentiable/euclidean.py  # Timed out
sage -t src/sage/manifolds/differentiable/metric.py  # Timed out
sage -t src/sage/manifolds/differentiable/multivectorfield.py  # Timed out
sage -t src/sage/manifolds/differentiable/tensorfield.py  # Timed out
sage -t src/sage/plot/plot.py  # Timed out
sage -t src/sage/rings/padics/padic_base_leaves.py  # Timed out
sage -t src/sage/rings/padics/padic_lattice_element.py  # Timed out
(and interrupt failed)


Will try 16.04 (the current base for my Docker images) and 18.04 next.

I'm building on a machine also with ubuntu 14.04 and will report back.
 

> To post to this group, send email to sage-r...@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.

John H Palmieri

unread,
May 15, 2018, 11:44:03 AM5/15/18
to sage-release
For me on OS X, I get the same failures as in earlier versions (which may be related somehow to my system). But if I then do "sage -i database_gap" and run tests again, I get failures in permgroup.py and features/gap.py. For example:

sage -t --long src/sage/features/gap.py
**********************************************************************
File "src/sage/features/gap.py", line 41, in sage.features.gap.GapPackage._is_present
Failed example:
    GapPackage("prim", spkg="database_gap").is_present()  # optional: database_gap
Expected:
    FeatureTestResult('GAP package prim', True)
Got:
    FeatureTestResult('GAP package prim', False)
**********************************************************************
1 item had failures:
   1 of   3 in sage.features.gap.GapPackage._is_present
    [12 tests, 1 failure, 5.81 s]
----------------------------------------------------------------------

sage -t --long src/sage/features/gap.py  # 1 doctest failed
----------------------------------------------------------------------

Emmanuel, is this what you are seeing?

--
John

Dima Pasechnik

unread,
May 15, 2018, 12:34:16 PM5/15/18
to sage-release

Dima Pasechnik

unread,
May 15, 2018, 12:36:29 PM5/15/18
to sage-release
this is already fixed in https://trac.sagemath.org/ticket/25323
please review :-)


On Tuesday, May 15, 2018 at 4:44:03 PM UTC+1, John H Palmieri wrote:

Sébastien Labbé

unread,
May 15, 2018, 3:24:26 PM5/15/18
to sage-release
On Ubuntu 16.04, the command `./sage -t -p --all --long --optional=sage,optional,external` finishes with:

----------------------------------------------------------------------
sage -t --long src/sage/coding/code_constructions.py  # 1 doctest failed
----------------------------------------------------------------------
Total time for all tests: 1821.3 seconds
    cpu time: 11639.5 seconds
    cumulative wall time: 14059.4 seconds
External software detected for doctesting: gurobi,latex
Traceback (most recent call last):
  File "/home/slabbe/GitBox/sage/src/bin/sage-runtests", line 127, in <module>
    err = DC.run()
  File "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/doctest/control.py", line 1176, in run
    + ','.join(available_software.seen()))
  File "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/doctest/control.py", line 583, in log
    self.logger.write(s + end)
  File "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/doctest/control.py", line 250, in write
    f.write(x)
ValueError: I/O operation on closed file


The code_construction error is copied below (I can not reproduce it) :



sage -t --long src/sage/coding/code_constructions.py
**********************************************************************
File "src/sage/coding/code_constructions.py", line 624, in sage.coding.code_constructions.QuadraticResidueCodeOddPair
Failed example:
    codes.QuadraticResidueCodeOddPair(17, GF(13))
Exception raised:
    Traceback (most recent call last):
      File "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py", line 562, in _run
        self.compile_and_execute(example, compiler, test.globs)
      File "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py", line 972, in compile_and_execute
        exec(compiled, globs)
      File "<doctest sage.coding.code_constructions.QuadraticResidueCodeOddPair[0]>", line 1, in <module>
        codes.QuadraticResidueCodeOddPair(Integer(17), GF(Integer(13)))
      File "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/coding/code_constructions.py", line 666, in Quadratic
ResidueCodeOddPair
        return DuadicCodeOddPair(F,Q,N)
      File "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/coding/code_constructions.py", line 425, in DuadicCod
eOddPair
        gg1 = P2(coeffs1)
      File "sage/structure/parent.pyx", line 920, in sage.structure.parent.Parent.__call__ (build/cythonized/sage/structure/paren
t.c:9734)
        return mor._call_(x)
      File "sage/structure/coerce_maps.pyx", line 145, in sage.structure.coerce_maps.DefaultConvertMap_unique._call_ (build/cytho
nized/sage/structure/coerce_maps.c:4555)
        raise
      File "sage/structure/coerce_maps.pyx", line 140, in sage.structure.coerce_maps.DefaultConvertMap_unique._call_ (build/cytho
nized/sage/structure/coerce_maps.c:4423)
        return C._element_constructor(x)
      File "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/rings/polynomial/polynomial_ring.py", line 404, in _e
lement_constructor_
        return C(self, x, check=check, is_gen=False, construct=construct)
      File "sage/rings/polynomial/polynomial_zmod_flint.pyx", line 100, in sage.rings.polynomial.polynomial_zmod_flint.Polynomial
_zmod_flint.__init__ (build/cythonized/sage/rings/polynomial/polynomial_zmod_flint.cpp:14358)
        lst = [k(i) for i in x]
      File "sage/structure/parent.pyx", line 920, in sage.structure.parent.Parent.__call__ (build/cythonized/sage/structure/paren
t.c:9734)
        return mor._call_(x)
      File "sage/rings/finite_rings/hom_prime_finite_field.pyx", line 46, in sage.rings.finite_rings.hom_prime_finite_field.Secti
onFiniteFieldHomomorphism_prime._call_ (build/cythonized/sage/rings/finite_rings/hom_prime_finite_field.c:3457)
        raise ValueError("%s is not in the image of %s" % (x, self._inverse))
    ValueError: 3*z^3 + 2*z^2 + 8*z + 1 is not in the image of (map internal to coercion system -- copy before use)
    Ring morphism:
      From: Finite Field of size 13
      To:   Finite Field in z of size 13^4

**********************************************************************
1 item had failures:
   1 of  13 in sage.coding.code_constructions.QuadraticResidueCodeOddPair
    [146 tests, 1 failure, 2.56 s]

Justin C. Walker

unread,
May 15, 2018, 4:36:52 PM5/15/18
to sage-r...@googlegroups.com

> On May 14, 2018, at 11:10 , Volker Braun <vbrau...@gmail.com> wrote:
>
> 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

Built from a fresh clone/update of the develop branch on macOS 10.11.6 (Quad-core Core i7) w/o problems,. As for B0, there was one problem in testing (‘ptestlong’):

sage -t --warn-long 89.1 src/sage/rings/complex_arb.pyx # 1 dockets failed

Again, running stand-alone showed the same failure as in B0.

Justin

--
Justin C. Walker, Curmudgeon at Large
Institute for the Absorption of Federal Funds
-----------
Like the ski resort full of girls hunting for husbands
and husbands hunting for girls, the situation is not
as symmetrical as it might seem.
- Alan MacKay
--

Samuel Lelievre

unread,
May 15, 2018, 6:27:48 PM5/15/18
to sage-release
Under macOS 10.10.5, after downloading the cysignals patch


    build/pkgs/cysignals/patches

both the build+docbuild of Python2-based Sage
and the build+nodocbuild of Python3-based Sage
were successful. I have not run the tests.

Henri Girard

unread,
May 16, 2018, 3:44:25 AM5/16/18
to sage-r...@googlegroups.com

Bionic 18.04 AMD x8 64 bits, compile perfect. I started from fresh git sage because upgrading from 8.2 failed. It couldn't find many libs. By the way I found my crash problem while compiling : I had to config the bios allowing warmer processing.

--
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.

John Cremona

unread,
May 16, 2018, 3:56:58 AM5/16/18
to sage-r...@googlegroups.com
I started to build this yesterday after pulling from trac into a place where beta0 had already built OK.  This morning I find the lines

[scipy-0.19.1] Skipping scipy as it is not installed.
[scipy-0.19.1] Skipping scipy as it is not installed.
[scipy-0.19.1] Skipping scipy as it is not installed.
[scipy-0.19.1] Skipping scipy as it is not installed.
[scipy-0.19.1] Skipping scipy as it is not installed.
[scipy-0.19.1] Skipping scipy as it is not installed.
[scipy-0.19.1] Skipping scipy as it is not installed.
[scipy-0.19.1] Skipping scipy as it is not installed.
[scipy-0.19.1] Skipping scipy as it is not installed.
[scipy-0.19.1] Skipping scipy as it is not installed.
[scipy-0.19.1] Skipping scipy as it is not installed.
[scipy-0.19.1] Skipping scipy as it is not installed.
[scipy-0.19.1] Skipping scipy as it is not installed.
[scipy-0.19.1] Skipping scipy as it is not installed.
[scipy-0.19.1] Skipping scipy as it is not installed.
[scipy-0.19.1] Skipping scipy as it is not installed.
[scipy-0.19.1] Skipping scipy as it is not installed.
[scipy-0.19.1] Skipping scipy as it is not installed.
[scipy-0.19.1] Skipping scipy as it is not installed.
[scipy-0.19.1] Skipping scipy as it is not installed.
[scipy-0.19.1] Skipping scipy as it is not installed.
[scipy-0.19.1] Skipping scipy as it is not installed.
[scipy-0.19.1] Skipping scipy as it is not installed.
[scipy-0.19.1] Skipping scipy as it is not installed.
[scipy-0.19.1] Skipping scipy as it is not installed.

being repeated for ever.  I have left that going in case someone wants to see any log files.

To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscribe@googlegroups.com.

To post to this group, send email to sage-r...@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.

Erik Bray

unread,
May 16, 2018, 11:26:13 AM5/16/18
to sage-r...@googlegroups.com
I'm not sure, but I think this might be pip-related. I think Jeroen
mentioned something about this to me a couple weeks ago. Is it
possible you upgraded the pip in your Sage install?
>> email to sage-release...@googlegroups.com.
>> To post to this group, send email to sage-r...@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-release.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> 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 post to this group, send email to sage-r...@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-release.
>> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> 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.

John Cremona

unread,
May 16, 2018, 11:33:50 AM5/16/18
to sage-r...@googlegroups.com
Yes I did!  I had installed some stuff needed for LMFDB using sage -i pip instal ...  and it told me my pip was not the most recent and should be upgraded, so I did.

What should I do?

Maarten Derickx

unread,
May 16, 2018, 12:39:43 PM5/16/18
to sage-release
pip should be able to uninstall itself so

sage -pip uninstall pip
sage -i pip

should give you the standard sage version of pip back. I did not test this, so use at your own risk.

Jeroen Demeyer

unread,
May 16, 2018, 5:15:57 PM5/16/18
to sage-r...@googlegroups.com
On 2018-05-16 17:26, Erik Bray wrote:
> I'm not sure, but I think this might be pip-related. I think Jeroen
> mentioned something about this to me a couple weeks ago. Is it
> possible you upgraded the pip in your Sage install?

Indeed, I guess you are using pip 10 by accident.

It might be a good idea to upgrade the pip in Sage and fix this issue.

Vincent Delecroix

unread,
May 17, 2018, 2:46:29 AM5/17/18
to sage-r...@googlegroups.com
On 15/05/2018 21:24, Sébastien Labbé wrote:
> On Ubuntu 16.04, the command `./sage -t -p --all --long
> --optional=sage,optional,external` finishes with:
>
> sage -t --long src/sage/coding/code_constructions.py
> **********************************************************************
> File "src/sage/coding/code_constructions.py", line 624, in
> sage.coding.code_constructions.QuadraticResidueCodeOddPair
> Failed example:
> codes.QuadraticResidueCodeOddPair(17, GF(13))
> Exception raised:
> Traceback (most recent call last):
> Ring morphism:
> From: Finite Field of size 13
> To: Finite Field in z of size 13^4
> **********************************************************************
> 1 item had failures:
> 1 of 13 in sage.coding.code_constructions.QuadraticResidueCodeOddPair
> [146 tests, 1 failure, 2.56 s]

Same error at

https://patchbot.sagemath.org/log/24783/Ubuntu/16.04/x86_64/4.4.0-124-generic/quasar/2018-05-16%2012:29:14?short

I opened ticket #25379

Vincent

John Cremona

unread,
May 17, 2018, 3:33:36 AM5/17/18
to sage-r...@googlegroups.com
On 16 May 2018 at 22:15, Jeroen Demeyer <J.De...@ugent.be> wrote:
On 2018-05-16 17:26, Erik Bray wrote:
I'm not sure, but I think this might be pip-related.  I think Jeroen
mentioned something about this to me a couple weeks ago.  Is it
possible you upgraded the pip in your Sage install?

Indeed, I guess you are using pip 10 by accident.

I think so.  I killed that build, downgraded pip, and restarted make.  Something was confused enough that I then just did "make distclean && make" and now all is well.
 

It might be a good idea to upgrade the pip in Sage and fix this issue.

I myself have no idea what the implications of that might be!

John

Sébastien Labbé

unread,
May 17, 2018, 5:58:35 AM5/17/18
to sage-release


On Tuesday, May 15, 2018 at 9:24:26 PM UTC+2, Sébastien Labbé wrote:
On Ubuntu 16.04, the command `./sage -t -p --all --long --optional=sage,optional,external` finishes with:

----------------------------------------------------------------------
sage -t --long src/sage/coding/code_constructions.py  # 1 doctest failed
----------------------------------------------------------------------
Total time for all tests: 1821.3 seconds
    cpu time: 11639.5 seconds
    cumulative wall time: 14059.4 seconds
External software detected for doctesting: gurobi,latex
Traceback (most recent call last):
  File "/home/slabbe/GitBox/sage/src/bin/sage-runtests", line 127, in <module>
    err = DC.run()
  File "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/doctest/control.py", line 1176, in run
    + ','.join(available_software.seen()))
  File "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/doctest/control.py", line 583, in log
    self.logger.write(s + end)
  File "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/doctest/control.py", line 250, in write
    f.write(x)
ValueError: I/O operation on closed file



I created  https://trac.sagemath.org/ticket/25378 for the ValueError: I/O operation on closed file

Eric Gourgoulhon

unread,
May 17, 2018, 9:28:43 AM5/17/18
to sage-release
On Ubuntu 16.04 x86_64 Xeon E5-2623 + 16 GB RAM, from a fresh git clone + pull develop, parallel (-j16) build OK and make ptestlong failed with 4 transient doctests. 3 of them are  due to "Jmol failed to create file", as usual on this computer (race error?), but the 4th one is a different type:

sage -t --long --warn-long 51.8 src/sage/schemes/elliptic_curves/padics.py
**********************************************************************
File "src/sage/schemes/elliptic_curves/padics.py", line 878, in sage.schemes.elliptic_curves.padics.padic_height_via_multiply
Failed example:
    for prec in range(2, max_prec):                 # long time
        assert E.padic_height_via_multiply(5, prec)(P) == full   # long time
Exception raised:

    Traceback (most recent call last):
      File "/home/eric/sage/8.3.beta1/local/lib/python2.7/site-packages/sage/doctest/forker.py", line 562, in _run
        self.compile_and_execute(example, compiler, test.globs)
      File "/home/eric/sage/8.3.beta1/local/lib/python2.7/site-packages/sage/doctest/forker.py", line 972, in compile_and_execute
        exec(compiled, globs)
      File "<doctest sage.schemes.elliptic_curves.padics.padic_height_via_multiply[13]>", line 2, in <module>
        assert E.padic_height_via_multiply(Integer(5), prec)(P) == full   # long time
      File "/home/eric/sage/8.3.beta1/local/lib/python2.7/site-packages/sage/schemes/elliptic_curves/padics.py", line 908, in padic_height_via_multiply
        sigma = self.padic_sigma_truncated(p, N=adjusted_prec, E2=E2, lamb=lamb)
      File "/home/eric/sage/8.3.beta1/local/lib/python2.7/site-packages/sage/schemes/elliptic_curves/padics.py", line 1285, in padic_sigma_truncated
        E2 = self.padic_E2(p, N-2, check_hypotheses=False)
      File "/home/eric/sage/8.3.beta1/local/lib/python2.7/site-packages/sage/schemes/elliptic_curves/padics.py", line 1506, in padic_E2
        frob_p = self.matrix_of_frobenius(p, prec, check, check_hypotheses, algorithm).change_ring(Integers(p**prec))
      File "/home/eric/sage/8.3.beta1/local/lib/python2.7/site-packages/sage/schemes/elliptic_curves/padics.py", line 1657, in matrix_of_frobenius
        Q, p, adjusted_prec, trace)
      File "/home/eric/sage/8.3.beta1/local/lib/python2.7/site-packages/sage/schemes/hyperelliptic_curves/monsky_washnitzer.py", line 1659, in matrix_of_frobenius
        F1_reduced = reduce_all(Q, p, F1_coeffs, offset)
      File "/home/eric/sage/8.3.beta1/local/lib/python2.7/site-packages/sage/schemes/hyperelliptic_curves/monsky_washnitzer.py", line 1024, in reduce_all
        exact_form = reduce_negative(Q, p, coeffs, offset, exact_form)
      File "/home/eric/sage/8.3.beta1/local/lib/python2.7/site-packages/sage/schemes/hyperelliptic_curves/monsky_washnitzer.py", line 800, in reduce_negative
        a[1] = base_ring(lift(a[1]) / (j+1))
      File "sage/structure/parent.pyx", line 920, in sage.structure.parent.Parent.__call__ (build/cythonized/sage/structure/parent.c:9734)
        return mor._call_(x)
      File "sage/structure/coerce_maps.pyx", line 145, in sage.structure.coerce_maps.DefaultConvertMap_unique._call_ (build/cythonized/sage/structure/coerce_maps.c:4555)

        raise
      File "sage/structure/coerce_maps.pyx", line 140, in sage.structure.coerce_maps.DefaultConvertMap_unique._call_ (build/cythonized/sage/structure/coerce_maps.c:4423)
        return C._element_constructor(x)
      File "/home/eric/sage/8.3.beta1/local/lib/python2.7/site-packages/sage/rings/finite_rings/integer_mod_ring.py", line 1168, in _element_constructor_
        return integer_mod.IntegerMod(self, x)
      File "sage/rings/finite_rings/integer_mod.pyx", line 197, in sage.rings.finite_rings.integer_mod.IntegerMod (build/cythonized/sage/rings/finite_rings/integer_mod.c:4557)
        return t(parent, value)
      File "sage/rings/finite_rings/integer_mod.pyx", line 350, in sage.rings.finite_rings.integer_mod.IntegerMod_abstract.__init__ (build/cythonized/sage/rings/finite_rings/integer_mod.c:5738)
        z = value % self.__modulus.sageInteger
      File "sage/rings/rational.pyx", line 2867, in sage.rings.rational.Rational.__mod__ (build/cythonized/sage/rings/rational.c:25746)
        d = d.inverse_mod(other)
      File "sage/rings/integer.pyx", line 6607, in sage.rings.integer.Integer.inverse_mod (build/cythonized/sage/rings/integer.c:41598)
        raise ZeroDivisionError("Inverse does not exist.")
    ZeroDivisionError: Inverse does not exist.

**********************************************************************
1 item had failures:
   1 of  15 in sage.schemes.elliptic_curves.padics.padic_height_via_multiply
    [199 tests, 1 failure, 15.26 s]

Again, the error is transient: all doctests in that file are passed when run standalone:

./sage -t --long --warn-long 51.8 src/sage/schemes/elliptic_curves/padics.py
Running doctests with ID 2018-05-17-15-21-32-76509919.
Git branch: develop
Using --optional=mpir,python2,sage
Doctesting 1 file.
sage -t --long --warn-long 51.8 src/sage/schemes/elliptic_curves/padics.py
    [199 tests, 11.03 s]
----------------------------------------------------------------------
All tests passed!
----------------------------------------------------------------------
Total time for all tests: 11.2 seconds
    cpu time: 11.0 seconds
    cumulative wall time: 11.0 seconds

Eric.

John Cremona

unread,
May 17, 2018, 12:28:30 PM5/17/18
to sage-r...@googlegroups.com
Built 8.3.beta1 from scratch (after make distclean at least after previously reported pip version issues).  Two failing files both complaining that lrslib is not found:

sage -t --long src/sage/game_theory/normal_form_game.py  # 2 doctests failed
sage -t --long src/sage/game_theory/catalog_normal_form_games.py  # 15 doctests failed        

all failures report "   PackageNotFoundError: the package 'lrslib' was not found. You can install it by running 'sage -i lrslib' in a shell      "

That looks like some optional doctests have not been marked #optional, perhaps?

--
Reply all
Reply to author
Forward
0 new messages