It was noted that the issue might be related with that discussed in
https://groups.google.com/forum/#!searchin/sage-devel/linbox$2064-bit$20charpoly%7Csort:relevance/sage-devel/TLcYb4z7jyI/SsW02-5mBwAJ
--
You received this message because you are subscribed to the Google Groups
"sage-devel" gro
+1
This seems the best workaround for now as it would take some time to fix
the root cause of these timeouts.
On Monday, July 10, 2017 at 11:57:19 AM UTC+2, Erik Bray wrote:
>
> On Fri, Jul 7, 2017 at 4:25 PM, Kwankyu Lee > wrote:
> > Hi,
> >
> > Nowadays, it seems frequent that patchbots re
On Fri, Jul 7, 2017 at 4:25 PM, Kwankyu Lee wrote:
> Hi,
>
> Nowadays, it seems frequent that patchbots report "Timed out" failures. The
> files "plot.py" and "test.py" are often to blame. These patchbot reports are
> false in the sense that the ticket that is tested is not the cause of the
> fail
I've recently added code to print enhanced tracebacks when we kill a test
due to timeout (#23208), if you have gdb installed then you'll get some
idea of what it was doing when it timed out. I've seen a few cases on the
buildbot that point to FFPACK::CharPoly. This might be a bug in linbox that
HI,
Le samedi 8 juillet 2017 19:34:16 UTC+2, Kwankyu Lee a écrit :
>
> I observed another "Timed out" on a patchbot:
>
> sage -t --long src/sage/graphs/matchpoly.pyx
> Timed out
>
I've just got the same issue on a patchbot run on my computer, launched
with the command
python -m sage_patchb
I observed another "Timed out" on a patchbot:
sage -t --long src/sage/graphs/matchpoly.pyx
Timed out
On my laptop, this takes just less than 5 seconds. Strange...
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this grou
>
> (4) Actually investigate why the tests time out so often
>
Ok. For example,
sage -t --long src/sage/plot/plot.py
takes about 90 seconds on my laptop machine, but strangely the same testing
apparently takes more than 30 minutes on some patchbot machine. This is not
fully explained by the
On 2017-07-07 16:25, Kwankyu Lee wrote:
(1) Leave it as it is and live with it.
(2) Increase default "Timed out" time limits by
SAGE_TIMEOUT, SAGE_TIMEOUT_LONG variables.
(3) Split the files that take long to be tested.
(4) Actually investigate why the tests time out so often
--
You received t
Hi,
Nowadays, it seems frequent that patchbots report "Timed out" failures. The
files "plot.py" and "test.py" are often to blame. These patchbot reports
are false in the sense that the ticket that is tested is not the cause of
the failure.
What should we do? I can think of three options
(1) L
