On Fri, Mar 13, 2015 at 10:16 AM, Jeroen Demeyer <[email protected]> wrote:
> On 2015-03-13 18:10, William Stein wrote:
>>
>> On 64-bit Ubuntu 14.10, make ptestlong yields one doctest failure.
>> Since it's something that I think absolutely anybody who ran the
>> doctest on any system would see, I guess that means that the buildbots
>> and/or other tests you run before making a beta release do not include
>> the #long doctests? Would it make sense to always run the #long
>> doctests at least once on one platform before cutting a beta release?
>
>
>> Got:
>> [snip]
>> AlarmInterrupt: FLINT exception
>
> I would guess that's done, so maybe the failure does not occur on every
> system.
In general, sure, but given this particular failure, it seems to me
that it would occur somewhere if and only if it occurs everywhere?
It's a long-only doctest verifying that this line of code
raise AlarmInterrupt(msg)
raises an appropriate error. The difference between the given output
and what is actually produced is
AlarmInterrupt
versus
AlarmInterrupt: FLINT exception
So it could be that msg is "" on some platforms by "FLINT exception"
on others? It seems unlikely.
> What's the [snip]?
Here's the snip. It involves code you re-wrote (the sig_str stuff).
sage -t --long src/sage/matrix/matrix_integer_dense.pyx
**********************************************************************
File "src/sage/matrix/matrix_integer_dense.pyx", line 4240, in
sage.matrix.matrix_integer_dense.Matrix_integer_dense._solve_flint
Failed example:
alarm(2); A._solve_flint(B) # long time
Expected:
Traceback (most recent call last):
...
AlarmInterrupt
Got:
<BLANKLINE>
Traceback (most recent call last):
File
"/scratch/wstein/sage-6.6.beta5/local/lib/python2.7/site-packages/sage/doctest/forker.py",
line 492, in _run
self.compile_and_execute(example, compiler, test.globs)
File
"/scratch/wstein/sage-6.6.beta5/local/lib/python2.7/site-packages/sage/doctest/forker.py",
line 854, in compile_and_execute
exec(compiled, globs)
File "<doctest
sage.matrix.matrix_integer_dense.Matrix_integer_dense._solve_flint[19]>",
line 1, in <module>
alarm(Integer(2)); A._solve_flint(B) # long time
File "sage/matrix/matrix_integer_dense.pyx", line 4272, in
sage.matrix.matrix_integer_dense.Matrix_integer_dense._solve_flint
(build/cythonized/sage/matrix/mat
rix_integer_dense.c:34400)
M = self._new_uninitialized_matrix(self._ncols,B._ncols)
File "sage/matrix/matrix_integer_dense.pyx", line 706, in
sage.matrix.matrix_integer_dense.Matrix_integer_dense._new_uninitialized_matrix
(build/cythonized/sag
e/matrix/matrix_integer_dense.c:8995)
cdef Matrix_integer_dense ans =
Matrix_integer_dense.__new__(Matrix_integer_dense, P, None, None,
None)
File "sage/matrix/matrix_integer_dense.pyx", line 216, in
sage.matrix.matrix_integer_dense.Matrix_integer_dense.__cinit__
(build/cythonized/sage/matrix/matrix_
integer_dense.c:5937)
sig_str("FLINT exception")
File "sage/ext/c_lib.pyx", line 77, in
sage.ext.c_lib.sig_raise_exception
(build/cythonized/sage/ext/c_lib.c:918)
raise AlarmInterrupt(msg)
AlarmInterrupt: FLINT exception
**********************************************************************
1 item had failures:
1 of 23 in
sage.matrix.matrix_integer_dense.Matrix_integer_dense._solve_flint
[554 tests, 1 failure, 26.36 s]
--
William (http://wstein.org)
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.