Re: [sage-release] Sage 7.4.beta2 released
On 2016-08-26 19:51, Volker Braun 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 All tests passed with "make ptestlong" on Linux Mint 17.3. Daniel -- 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 post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Sage 7.4.beta2 released
Volker Braun wrote: > 5cd62cb Updated SageMath version to 7.4.beta2 Built from scratch (source tarball), Linux x86_64 (Haswells). With GCC 6.1.0: -- sage -t --long src/sage/libs/gap/assigned_names.py # 1 doctest failed sage -t --long src/sage/symbolic/function.pyx # 1 doctest failed -- The first is the usual failure, the second is new, and I don't know where it originates from (as the doctest itself hasn't changed): ** File "src/sage/symbolic/function.pyx", line 667, in sage.symbolic.function.Function._fast_float_ Failed example: ff(1.5) Expected: 0.9661051464753108 Got: 0.9661051464753109 ** With Sage's GCC 4.9.3: -- sage -t --long src/sage/homology/simplicial_complex.py # 1 doctest failed sage -t --long src/sage/libs/gap/libgap.pyx # Bad exit: 2 sage -t --long src/sage/libs/gap/assigned_names.py # 1 doctest failed -- The third is the usual failure as above, the first is ~ #15585 (random failures in different doctests of the same file [1]), the second (also) passes when rerun, log files gives: sage -t --long src/sage/libs/gap/libgap.pyx Bad exit: 2 ** Tests run before process (pid=5609) failed: sage: a = libgap(10) ## line 11 ## ** -leif [1] https://trac.sagemath.org/ticket/15585 -- 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 post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Sage 7.4.beta2 released
Builds and tests pass on Arch 4.6.3-1 x86_64, 16GB ram. I had to do make distclean: the Pari upgrade complained. Best, Johan -- 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 post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Sage 7.4.beta2 released
Builds and tests long pass on Ubuntu 14.04.5 LTS (gcc version 4.8.4). Vincent -- 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 post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Sage 7.4.beta2 released
On 2016-08-27 01:08, Johan S. H. Rosenkilde wrote: I had to do make distclean: the Pari upgrade complained. Do you have more details? -- 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 post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Sage 7.4.beta2 released
However, running the patchbot on the same computer I got one failing doctest
Failed example:
G.canonical_label(certify=True)
Expected:
doctest:...: DeprecationWarning: use the option 'certificate'
instead of 'certify'
See http://trac.sagemath.org/2 for details.
(Graph on 2 vertices, {'a': 0, 'b': 1})
Got:
doctest:warning
...
DeprecationWarning: use the option 'certificate' instead of 'certify'
See http://trac.sagemath.org/2 for details.
(Graph on 2 vertices, {'a': 1, 'b': 0})
On 27/08/16 00:11, Vincent Delecroix wrote:
Builds and tests long pass on Ubuntu 14.04.5 LTS (gcc version 4.8.4).
Vincent
--
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 post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Sage 7.4.beta2 released
Vincent Delecroix wrote:
> However, running the patchbot on the same computer I got one failing
> doctest
>
> Failed example:
> G.canonical_label(certify=True)
> Expected:
> doctest:...: DeprecationWarning: use the option 'certificate'
> instead of 'certify'
> See http://trac.sagemath.org/2 for details.
> (Graph on 2 vertices, {'a': 0, 'b': 1})
> Got:
> doctest:warning
> ...
> DeprecationWarning: use the option 'certificate' instead of 'certify'
> See http://trac.sagemath.org/2 for details.
> (Graph on 2 vertices, {'a': 1, 'b': 0})
... which shows that
a) the test doesn't make sense (after all, it's supposed to just test
the deprecation of "certify" I think)
b) as is, the representation returned for a vertex-labeled graph isn't
canonical... ;-)
-leif
P.S.: File src/sage/graphs/generic_graph.py, line 20930.
>
> On 27/08/16 00:11, Vincent Delecroix wrote:
>> Builds and tests long pass on Ubuntu 14.04.5 LTS (gcc version 4.8.4).
>>
>> Vincent
>
--
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 post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Sage 7.4.beta2 released
On 27/08/16 22:02, leif wrote: Vincent Delecroix wrote: > > [...] > b) as is, the representation returned for a vertex-labeled graph isn't canonical... ;-) It might if the graph has an automorphism! Vincent -- 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 post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Sage 7.4.beta2 released
#21357 needs review
On 27/08/16 22:02, leif wrote:
Vincent Delecroix wrote:
However, running the patchbot on the same computer I got one failing
doctest
Failed example:
G.canonical_label(certify=True)
Expected:
doctest:...: DeprecationWarning: use the option 'certificate'
instead of 'certify'
See http://trac.sagemath.org/2 for details.
(Graph on 2 vertices, {'a': 0, 'b': 1})
Got:
doctest:warning
...
DeprecationWarning: use the option 'certificate' instead of 'certify'
See http://trac.sagemath.org/2 for details.
(Graph on 2 vertices, {'a': 1, 'b': 0})
... which shows that
a) the test doesn't make sense (after all, it's supposed to just test
the deprecation of "certify" I think)
b) as is, the representation returned for a vertex-labeled graph isn't
canonical... ;-)
-leif
P.S.: File src/sage/graphs/generic_graph.py, line 20930.
On 27/08/16 00:11, Vincent Delecroix wrote:
Builds and tests long pass on Ubuntu 14.04.5 LTS (gcc version 4.8.4).
Vincent
--
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 post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Sage 7.4.beta2 released
Have you seen #21356 which already has positive review and is tested by Volker
right now?
> On 28/08/2016, at 13:09, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
>
> #21357 needs review
>
> On 27/08/16 22:02, leif wrote:
>> Vincent Delecroix wrote:
>>> However, running the patchbot on the same computer I got one failing
>>> doctest
>>>
>>> Failed example:
>>>G.canonical_label(certify=True)
>>> Expected:
>>>doctest:...: DeprecationWarning: use the option 'certificate'
>>> instead of 'certify'
>>>See http://trac.sagemath.org/2 for details.
>>>(Graph on 2 vertices, {'a': 0, 'b': 1})
>>> Got:
>>>doctest:warning
>>>...
>>>DeprecationWarning: use the option 'certificate' instead of 'certify'
>>>See http://trac.sagemath.org/2 for details.
>>>(Graph on 2 vertices, {'a': 1, 'b': 0})
>>
>> ... which shows that
>>
>> a) the test doesn't make sense (after all, it's supposed to just test
>> the deprecation of "certify" I think)
>>
>> b) as is, the representation returned for a vertex-labeled graph isn't
>> canonical... ;-)
>>
>>
>> -leif
>>
>>
>> P.S.: File src/sage/graphs/generic_graph.py, line 20930.
>>
>>
>>>
>>> On 27/08/16 00:11, Vincent Delecroix wrote:
Builds and tests long pass on Ubuntu 14.04.5 LTS (gcc version 4.8.4).
Vincent
>>>
>>
>
> --
> 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 post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
This email may be confidential and subject to legal privilege, it may
not reflect the views of the University of Canterbury, and it is not
guaranteed to be virus free. If you are not an intended recipient,
please notify the sender immediately and erase all copies of the message
and any attachments.
Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
information.
--
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 post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Sage 7.4.beta2 released
Francois Bissey wrote:
> Have you seen #21356 which already has positive review and is tested by
> Volker right now?
Well, if Jeroen had reported it where it belongs...
The solution on #21357 is more adequate though.
-leif
>> On 28/08/2016, at 13:09, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
>>
>> #21357 needs review
>>
>> On 27/08/16 22:02, leif wrote:
>>> Vincent Delecroix wrote:
However, running the patchbot on the same computer I got one failing
doctest
Failed example:
G.canonical_label(certify=True)
Expected:
doctest:...: DeprecationWarning: use the option 'certificate'
instead of 'certify'
See http://trac.sagemath.org/2 for details.
(Graph on 2 vertices, {'a': 0, 'b': 1})
Got:
doctest:warning
...
DeprecationWarning: use the option 'certificate' instead of 'certify'
See http://trac.sagemath.org/2 for details.
(Graph on 2 vertices, {'a': 1, 'b': 0})
>>>
>>> ... which shows that
>>>
>>> a) the test doesn't make sense (after all, it's supposed to just test
>>> the deprecation of "certify" I think)
>>>
>>> b) as is, the representation returned for a vertex-labeled graph isn't
>>> canonical... ;-)
>>>
>>>
>>> -leif
>>>
>>>
>>> P.S.: File src/sage/graphs/generic_graph.py, line 20930.
>>>
>>>
On 27/08/16 00:11, Vincent Delecroix wrote:
> Builds and tests long pass on Ubuntu 14.04.5 LTS (gcc version 4.8.4).
>
> Vincent
--
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 post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Sage 7.4.beta2 released
Jeroen, I ran into this error when I ran sage -b, but it went away when I ran make. I did not need to run make distclean. [163/362] Cythonizing sage/libs/pari/gen.pyx Error compiling Cython file: ... """ cdef GEN _L = L.g if not precision: precision = default_bitprec() sig_on() cdef long _ret = lfunorderzero(_L, precision) ^ sage/libs/pari/auto_gen.pxi:11038:38: Call with wrong number of arguments (expected 3, got 2) Error compiling Cython file: ... but not necessarily the lattice itself. In particular, if :math:`Q` is two-dimensional, then :math:`L` is always self-dual. """ cdef GEN _Q = Q.g sig_on() cdef GEN _ret = lfunqf(_Q) ^ sage/libs/pari/auto_gen.pxi:11052:30: Call with wrong number of arguments (expected 2, got 1) Traceback (most recent call last): File "/Users/Masson/Downloads/GitHub/sage/local/lib/python2.7/site-packages/Cython-0.24.1-py2.7-macosx-10.9-x86_64.egg/Cython/Build/Dependencies.py", line 1055, in cythonize_one_helper return cythonize_one(*m) File "/Users/Masson/Downloads/GitHub/sage/local/lib/python2.7/site-packages/Cython-0.24.1-py2.7-macosx-10.9-x86_64.egg/Cython/Build/Dependencies.py", line 1037, in cythonize_one raise CompileError(None, pyx_file) CompileError: sage/libs/pari/gen.pyx [164/362] Cythonizing sage/libs/pari/handle_error.pyx Traceback (most recent call last): File "setup.py", line 597, in run_cythonize() File "setup.py", line 589, in run_cythonize 'profile': profile, File "/Users/Masson/Downloads/GitHub/sage/local/lib/python2.7/site-packages/Cython-0.24.1-py2.7-macosx-10.9-x86_64.egg/Cython/Build/Dependencies.py", line 906, in cythonize result.get(9) # seconds File "/Users/Masson/Downloads/GitHub/sage/local/lib/python/multiprocessing/pool.py", line 567, in get raise self._value CompileError: sage/libs/pari/gen.pyx On Saturday, August 27, 2016 at 5:44:21 AM UTC-7, Jeroen Demeyer wrote: > > On 2016-08-27 01:08, Johan S. H. Rosenkilde wrote: > > I had to do make distclean: the Pari upgrade complained. > > Do you have more details? > -- 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 post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Sage 7.4.beta2 released
> On 2016-08-27 01:08, Johan S. H. Rosenkilde wrote: >> I had to do make distclean: the Pari upgrade complained. > > Do you have more details? I'll see if I can reproduce: I accidentally reverted to an old version by checking out a ticket, so after 2xrecompile I might see the same error again ;-) -- 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 post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Sage 7.4.beta2 released
On Monday, August 29, 2016 at 10:24:16 AM UTC+2, Johan S. R. Nielsen wrote: > > > On 2016-08-27 01:08, Johan S. H. Rosenkilde wrote: > >> I had to do make distclean: the Pari upgrade complained. > > > > Do you have more details? > > I'll see if I can reproduce: I accidentally reverted to an old version > by checking out a ticket, so after 2xrecompile I might see the same > error again ;-) > Nope, PARI didn't complain this time. So, yet another spurious compilation failure... -- 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 post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Sage 7.4.beta2 released
On 2016-08-29 04:09, Paul Masson wrote: Jeroen, I ran into this error when I ran sage -b, but it went away when I ran make. That's normal and *not* a bug. -- 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 post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Sage 7.4.beta2 released
Does anyone else get these segfaults in the kernel log? Aug 29 17:28:04 ark kernel: gentourng[1549]: segfault at 40065a02c ip 004018 1f sp 7ffce9d03520 error 4 in gentourng[40+19000] Aug 30 17:03:54 ark kernel: gentourng[20347]: segfault at 401d4402c ip 00401 81f sp 7ffe5bca7d60 error 4 in gentourng[40+19000] Aug 31 11:44:22 ark kernel: gentourng[1779]: segfault at 401f1502c ip 004018 1f sp 7fff9a7f4720 error 4 in gentourng[40+19000] Aug 31 15:09:49 ark kernel: gentourng[10162]: segfault at 401d8502c ip 00401 81f sp 7fff310eeea0 error 4 in gentourng[40+19000] I can associate them with patchbot or ptestlong runs. They go as far back as Apr 20 (limited by my kernel log). -- 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 post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Sage 7.4.beta2 released
Ralf Stephan wrote: > Does anyone else get these segfaults in the kernel log? Yup. But they seem to originate from builds, not testing. (I also do have segfaults in some conftests which always "immediately" precede the one in gentourng, although regarding the pids, the former apparently belong to different packages.) And I don't have them on every machine. -leif > Aug 29 17:28:04 ark kernel: gentourng[1549]: segfault at 40065a02c ip > 004018 > 1f sp 7ffce9d03520 error 4 in gentourng[40+19000] > Aug 30 17:03:54 ark kernel: gentourng[20347]: segfault at 401d4402c ip > 00401 > 81f sp 7ffe5bca7d60 error 4 in gentourng[40+19000] > Aug 31 11:44:22 ark kernel: gentourng[1779]: segfault at 401f1502c ip > 004018 > 1f sp 7fff9a7f4720 error 4 in gentourng[40+19000] > Aug 31 15:09:49 ark kernel: gentourng[10162]: segfault at 401d8502c ip > 00401 > 81f sp 7fff310eeea0 error 4 in gentourng[40+19000] > > I can associate them with patchbot or ptestlong runs. > They go as far back as Apr 20 (limited by my kernel log). -- 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 post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Sage 7.4.beta2 released
leif wrote: > Ralf Stephan wrote: >> Does anyone else get these segfaults in the kernel log? > > Yup. But they seem to originate from builds, not testing. Or not. I can produce them (a single one) with ./sage -t --long src/sage/graphs/digraph_generators.py (Without '--long' "works" as well.) -leif > (I also do have segfaults in some conftests which always "immediately" > precede the one in gentourng, although regarding the pids, the former > apparently belong to different packages.) > > And I don't have them on every machine. > > > -leif > >> Aug 29 17:28:04 ark kernel: gentourng[1549]: segfault at 40065a02c ip >> 004018 >> 1f sp 7ffce9d03520 error 4 in gentourng[40+19000] >> Aug 30 17:03:54 ark kernel: gentourng[20347]: segfault at 401d4402c ip >> 00401 >> 81f sp 7ffe5bca7d60 error 4 in gentourng[40+19000] >> Aug 31 11:44:22 ark kernel: gentourng[1779]: segfault at 401f1502c ip >> 004018 >> 1f sp 7fff9a7f4720 error 4 in gentourng[40+19000] >> Aug 31 15:09:49 ark kernel: gentourng[10162]: segfault at 401d8502c ip >> 00401 >> 81f sp 7fff310eeea0 error 4 in gentourng[40+19000] >> >> I can associate them with patchbot or ptestlong runs. >> They go as far back as Apr 20 (limited by my kernel log). > -- 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 post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Sage 7.4.beta2 released
On 2016-08-31 17:03, Ralf Stephan wrote: Does anyone else get these segfaults in the kernel log? I think that's pretty normal. Some doctests intentionally segfault. And maybe some build tests also do that. -- 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 post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Sage 7.4.beta2 released
leif wrote: > Volker Braun wrote: >> 5cd62cb Updated SageMath version to 7.4.beta2 > > Built from scratch (source tarball), Linux x86_64 (Haswells). > > With GCC 6.1.0: > > -- > sage -t --long src/sage/libs/gap/assigned_names.py # 1 doctest failed > sage -t --long src/sage/symbolic/function.pyx # 1 doctest failed > -- > > The first is the usual failure, the second is new, and I don't know > where it originates from (as the doctest itself hasn't changed): > > ** > File "src/sage/symbolic/function.pyx", line 667, in > sage.symbolic.function.Function._fast_float_ > Failed example: > ff(1.5) > Expected: > 0.9661051464753108 > Got: > 0.9661051464753109 > ** Trivial patch for the numerical noise (just adding '#tol') needs review: https://trac.sagemath.org/ticket/21411 -leif -- 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 post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Sage 7.4.beta2 released: Nauty's naughty
leif wrote:
> leif wrote:
>> Ralf Stephan wrote:
>>> Does anyone else get these segfaults in the kernel log?
>>
>> Yup. But they seem to originate from builds, not testing.
>
> Or not. I can produce them (a single one) with
>
> ./sage -t --long src/sage/graphs/digraph_generators.py
>
> (Without '--long' "works" as well.)
Rebuilt nauty with debug info:
Starting program: ${SAGE_ROOT}/local/bin/gentourng -c 2
>A ${SAGE_ROOT}/local/bin/gentourng -cd1D0 n=2
Program received signal SIGSEGV, Segmentation fault.
makeleveldata () at gentourng.c:488
488 d->xstart[xcard[nxsets-1]+1] = nxsets;
(gdb) print nxsets
$1 = 0
So apparently array index out of bounds (xcard[-1] and/or d->xstart[...]).
Note that already the parameters get "echoed" wrong (same if one
explicitly passes '-d0 -D1', which Sage does).
Incidentally(?), that's exactly the case where no tournaments exist at
all (i.e., strongly connected ones on two vertices, which is a
contradiction by itself).
The corresponding doctest lists the counts of tournaments on up to eight
vertices (silently but also not explicitly ignoring the error):
sage: tournaments = digraphs.tournaments_nauty
[...]
sage: [len(list(tournaments(x, strongly_connected = True)))
for x in range(1,9)]
[1, 0, 1, 1, 6, 35, 353, 6008]
tournaments_nauty() is implemented as a generator using Popen() and
PIPE. I so far failed to get any returncode from the Popen subprocess;
poll() keeps returning None.
(Haven't opened a ticket [yet], nor reported anything upstream.)
-leif
>>> Aug 29 17:28:04 ark kernel: gentourng[1549]: segfault at 40065a02c ip
>>> 004018
>>> 1f sp 7ffce9d03520 error 4 in gentourng[40+19000]
>>> Aug 30 17:03:54 ark kernel: gentourng[20347]: segfault at 401d4402c ip
>>> 00401
>>> 81f sp 7ffe5bca7d60 error 4 in gentourng[40+19000]
>>> Aug 31 11:44:22 ark kernel: gentourng[1779]: segfault at 401f1502c ip
>>> 004018
>>> 1f sp 7fff9a7f4720 error 4 in gentourng[40+19000]
>>> Aug 31 15:09:49 ark kernel: gentourng[10162]: segfault at 401d8502c ip
>>> 00401
>>> 81f sp 7fff310eeea0 error 4 in gentourng[40+19000]
>>>
>>> I can associate them with patchbot or ptestlong runs.
>>> They go as far back as Apr 20 (limited by my kernel log).
--
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 post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.
