Optional package 4ti2 test failures on Cygwin

[embray]

I get the following test failure on Cygwin when the 4ti2 optional package install:

sage -t --long --warn-long 151.0 /opt/sagemath-9.0/src/sage/interfaces/four_ti_2.py
**********************************************************************
File "/opt/sagemath-9.0/src/sage/interfaces/four_ti_2.py", line 314, in sage.interfaces.four_ti_2.FourTi2.zsolve
Failed example:
    four_ti_2.zsolve(A, rel, rhs, sign) # optional - 4ti2
Expected:
    [
             [ 1 -1  0]
             [ 0 -1  0]
    [0 0 1]  [ 0 -3  2]
    [1 1 0]  [ 1 -2  1]
    [0 1 0], [ 0 -2  1], []
    ]
Got:
    [[], [], []]
**********************************************************************
File "/opt/sagemath-9.0/src/sage/interfaces/four_ti_2.py", line 322, in sage.interfaces.four_ti_2.FourTi2.zsolve
Failed example:
    four_ti_2.zsolve(lat=[[1,2,3],[1,1,1]]) # optional - 4ti2
Expected:
    [
                 [1 2 3]
    [0 0 0], [], [1 1 1]
    ]
Got:
    [[], [], []]
**********************************************************************
File "/opt/sagemath-9.0/src/sage/interfaces/four_ti_2.py", line 377, in sage.interfaces.four_ti_2.FourTi2.hilbert
Failed example:
    four_ti_2.hilbert(four_ti_2._magic3x3()) # optional - 4ti2
Expected:
    [2 0 1 0 1 2 1 2 0]
    [1 0 2 2 1 0 0 2 1]
    [0 2 1 2 1 0 1 0 2]
    [1 2 0 0 1 2 2 0 1]
    [1 1 1 1 1 1 1 1 1]
Got:
    []
**********************************************************************
File "/opt/sagemath-9.0/src/sage/interfaces/four_ti_2.py", line 383, in sage.interfaces.four_ti_2.FourTi2.hilbert
Failed example:
    four_ti_2.hilbert(lat=[[1,2,3],[1,1,1]])   # optional - 4ti2
Expected:
    [2 1 0]
    [0 1 2]
    [1 1 1]
Got:
    []
**********************************************************************
File "/opt/sagemath-9.0/src/sage/interfaces/four_ti_2.py", line 400, in sage.interfaces.four_ti_2.FourTi2.graver
Failed example:
    four_ti_2.graver([1,2,3]) # optional - 4ti2
Expected:
    [ 2 -1  0]
    [ 3  0 -1]
    [ 1  1 -1]
    [ 1 -2  1]
    [ 0  3 -2]
Got:
    []
**********************************************************************
File "/opt/sagemath-9.0/src/sage/interfaces/four_ti_2.py", line 406, in sage.interfaces.four_ti_2.FourTi2.graver
Failed example:
    four_ti_2.graver(lat=[[1,2,3],[1,1,1]])  # optional - 4ti2
Expected:
    [ 1  0 -1]
    [ 0  1  2]
    [ 1  1  1]
    [ 2  1  0]
Got:
    []
**********************************************************************
File "/opt/sagemath-9.0/src/sage/interfaces/four_ti_2.py", line 478, in sage.interfaces.four_ti_2.FourTi2.groebner
Failed example:
    four_ti_2.groebner(A) # optional - 4ti2
Expected:
    [-5  0  2]
    [-5  3  0]
Got:
    /opt/sagemath-9.0/local/bin/groebner: line 64: 37007 Segmentation fault      (core dumped) "$DIR"/$EXECUTABLE $FUNCTION $@
    []
**********************************************************************
File "/opt/sagemath-9.0/src/sage/interfaces/four_ti_2.py", line 481, in sage.interfaces.four_ti_2.FourTi2.groebner
Failed example:
    four_ti_2.groebner(lat=[[1,2,3],[1,1,1]]) # optional - 4ti2
Expected:
    [-1  0  1]
    [ 2  1  0]
Got:
    /opt/sagemath-9.0/local/bin/groebner: line 64: 37121 Segmentation fault      (core dumped) "$DIR"/$EXECUTABLE $FUNCTION $@
    []
**********************************************************************
4 items had failures:
   2 of   4 in sage.interfaces.four_ti_2.FourTi2.graver
   2 of   5 in sage.interfaces.four_ti_2.FourTi2.groebner
   2 of   4 in sage.interfaces.four_ti_2.FourTi2.hilbert
   2 of   8 in sage.interfaces.four_ti_2.FourTi2.zsolve
    [54 tests, 8 failures, 35.30 s]

It looks like in some, possibly all cases it's segfaulting.

Component: porting: Cygwin

Keywords: 4ti2 cygwin windows

Issue created by migration from https://trac.sagemath.org/ticket/29193

[mkoeppe]

comment:1

Upstream 4ti2 has no CI infrastructure for cygwin but would accept a pull request that adds it.

[mkoeppe]

comment:5

Sage development has entered the release candidate phase for 9.3. Setting a new milestone for this ticket based on a cursory review of ticket status, priority, and last modification date.