[isabelle-dev] Nonterminating AFP build
lp15 at cam.ac.uk
Thu May 12 12:39:55 CEST 2016
It has no timeout, sorry, that was my fault. Now set to 300 seconds.
We don’t need a global timeout, but why not a default timeout? We could set up to the median runtime. Actually I think our typical value of 600 seconds is much too high, considering that a loop in a common library could make dozens of entries run forever.
> On 11 May 2016, at 23:58, Gerwin Klein <Gerwin.Klein at nicta.com.au> wrote:
> If it doesn’t have a timeout set, then that’s a mistake and should be fixed. It’d be good to have protection for all builds, not only through Jenkins.
> We’ve avoided a global timeout so far, because it’d have to be fairly long, i.e. if you have a few entries that don’t terminate because of a change in Isabelle for instance, you might very quickly be looking at multiple days.
> Might still be a good idea to add one anyway as an additional safety net.
>> On 12.05.2016, at 06:58, Lars Hupel <hupel at in.tum.de> wrote:
>> We appear to have an issue with nonterminating builds. See here:
>> I had to manually kill the running poly process. I'm not quite sure
>> which session causes it, but it's possibly Randomised_Social_Choice. I
>> was under the assumption that all AFP sessions had timeouts set –
>> apparently this is not the case.
>> In order to avoid these problems in the future, I'll implement job
>> timeouts in Jenkins.
>> isabelle-dev mailing list
>> isabelle-dev at in.tum.de
> The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.
> isabelle-dev mailing list
> isabelle-dev at in.tum.de
More information about the isabelle-dev