It is my subjective observation that timeouts on patchbots have become more
frequent. For instance, for ticket
https://patchbot.sagemath.org/ticket/22340/
two patchbots failed due to timeout,
quasar times out with
sage: ls = J0(46)._calculate_endomorphism_generators() ; ls ## line 213 ##
**********************************************************************
----------------------------------------------------------------------
sage -t --long src/sage/modular/abvar/abvar_ambient_jacobian.py # Timed out
whereas pbua times out with
sage: maxima._batch('10003;',batchload=False) ## line 869 ##
**********************************************************************
----------------------------------------------------------------------
sage -t --long --warn-long 255.7 src/sage/interfaces/maxima.py # Timed out
Do we have any idea how this can happen at all? (Naively, one would believe that
either the test works or it does not, I do not understand this quite random
behaviour here).
I know about the recommendation to avoid high system load; but this is somewhat
hard to control. On "my" two patchbots, I restrict myself to one or two
processes although sometimes I could volunteer more CPU time, but then, timeouts
get more likely.
Can we do anything about that? Usefullness of patchbots is somewhat limited with
that many false positives.
Regards,
Clemens
--
You received this message because you are subscribed to the Google Groups
"sage-devel" 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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
