this is now https://trac.sagemath.org/ticket/21719#ticket
Am Dienstag, 4. Oktober 2016 22:13:50 UTC+2 schrieb Volker Braun:
>
> I've seen that time out often on the buildbot, too. Please, somebody
> replace the test in there by something more reasonable.
>
>
>
> On Tuesday, October 4, 2016 at 9:5
I'm not confident that there is no issue, maybe I could take a look.
I suspect that the implementation is optimized for or runs best on specific
harware/environment, which is not a priori bad.
In addition I think that REALLY GOOD TIMING TESTS will need some extra
effort, namely:
(multiple) (com
On Tue, Oct 04, 2016 at 01:13:49PM -0700, Volker Braun wrote:
> I've seen that time out often on the buildbot, too. Please, somebody
> replace the test in there by something more reasonable.
Just to be sure, are you confident that this is not pointing some issue ?
Ciao,
Thierry
>
> On Tuesday
I've seen that time out often on the buildbot, too. Please, somebody
replace the test in there by something more reasonable.
On Tuesday, October 4, 2016 at 9:53:13 PM UTC+2, Jakob Kroeker wrote:
>
> on my machine (fedora 23, 32 Bit) the test
>
> sage -t --long --warn-long 127.3 src/sage/rings/n
