วันจันทร์ที่ 10 กรกฎาคม พ.ศ. 2560

Re: [sage-devel] What to do with the "Timed out" failures of patchbots?

+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 <ekwa...@gmail.com> 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
> failure.
>
> What should we do? I can think of three options
>
> (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.

This is also an attempt to address this issue:
https://github.com/sagemath/sage-patchbot/pull/107

In fact, I already merged it so if whoever has access to the main
patchbot server wants to install this update then people can configure
their patchbots to add retries=1 or retries=2.  For me that works
quite nicely--tests that failed due to timeout will usually succeed on
a second attempt.  If it fails even on a second attempt that might
indicate a real problem.

--
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 sage-devel+unsubscribe@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

ไม่มีความคิดเห็น:

แสดงความคิดเห็น