Great !!! CCing storm dev community.
Thanks Anna. On Tue, Sep 27, 2016 at 12:06 PM, Anna Nagy <supp...@travis-ci.com> wrote: > Perfect! Thanks again, Raghav. I just confirmed the custom timeout should > be all set - it's set at 90 minutes. Once the container-based infra timeout > is respected, builds will be automatically terminated after 90 mins. > > Please feel free to let us know if you need anything else! > > Best, > Anna > > > How would you rate my reply? > Great > <https://secure.helpscout.net/satisfaction/96425415/record/682392650/1/> > Okay > <https://secure.helpscout.net/satisfaction/96425415/record/682392650/2/> > Not Good > <https://secure.helpscout.net/satisfaction/96425415/record/682392650/3/> > > -- > Anna Nagy > Customer Support Engineer > supp...@travis-ci.com > > Visit https://www.traviscistatus.com/ for service status and uptime > details > > Travis CI GmbH, Rigaer Str.8, 10247 Berlin, Germany | GF/CEO: Mathias > Meyer, Joshua Kalderimis | Contact: cont...@travis-ci.org > <cont...@travis-ci.com> > Amtsgericht Charlottenburg, Berlin, HRB 140133 B | Umsatzsteuer-ID gemäß > §27 a Umsatzsteuergesetz: DE282002648 > {#HS:256251341-35921#} > On Tue, Sep 27, 2016 at 19:04:22 UTC, Raghav Kumar Gautam < > rag...@apache.org> wrote: >> >> Hi Anna, >> >> It will be great if you can set it to 90 mins for Apache Storm. For other >> projects I don't have the information. >> >> Thanks, >> Raghav. >> >> >> >> On Tue, Sep 27, 2016 at 18:53:14 UTC, Anna Nagy <supp...@travis-ci.com> >> wrote: >>> >>> Hey Raghav - >>> >>> Thanks for your reply! My apologies for my lack of clarity. >>> >>> We can set the custom timeouts only from within our internal tools. That >>> said, it's not a problem at all to bump up some of your projects to the >>> 90-minute timeout. They're handled on a repository-by-repository basis. Do >>> you know which repos need the 90-min timeout? I believe we just have it for >>> apache/storm at the moment. >>> >>> All that said, the bug with container-based builds' timeouts not being >>> respected still stands. I know our infrastructure team is working on it >>> though, so I'm hoping that check should be working again soon. >>> >>> Thanks again! >>> Anna >>> >>> -- >>> Anna Nagy >>> Customer Support Engineer >>> supp...@travis-ci.com >>> >>> Visit https://www.traviscistatus.com/ for service status and uptime >>> details >>> >>> Travis CI GmbH, Rigaer Str.8, 10247 Berlin, Germany | GF/CEO: Mathias >>> Meyer, Joshua Kalderimis | Contact: cont...@travis-ci.org >>> <cont...@travis-ci.com> >>> Amtsgericht Charlottenburg, Berlin, HRB 140133 B | Umsatzsteuer-ID gemäß >>> §27 a Umsatzsteuergesetz: DE282002648 >>> >>> >>> On Tue, Sep 27, 2016 at 17:39:47 UTC, Raghav Kumar Gautam < >>> raghavgau...@gmail.com> wrote: >>>> >>>> Hi Anna, >>>> >>>> How can I set a timeout of 90 minutes for my builds, they get >>>> terminated after 50 mins. >>>> >>>> Thanks, >>>> Raghav. >>>> >>>> >>>> Raghav Kumar Gautam >>>> http://www.linkedin.com/in/raghavg >>>> >>>> >>>> >>>> On Tue, Sep 27, 2016 at 15:47:52 UTC, Anna Nagy <supp...@travis-ci.com> >>>> wrote: >>>>> >>>>> Hey Raghav - >>>>> >>>>> Thanks so much for reaching out about the long build! Really >>>>> appreciate the heads-up. >>>>> >>>>> I checked our system to see what happened and confirmed the same thing >>>>> - looks like the build definitely went over your (custom) 90 minute >>>>> timeout: >>>>> Started 2016-07-14 01:28:54 UTC >>>>> Finished 2016-07-14 03:11:18 UTC >>>>> Duration 1 hrs 42 min 24.0 sec >>>>> >>>>> After a little more investigating, however, I found that builds >>>>> running over their timeout currently is an issue on the container-based >>>>> infrastructure. We're working on fixing this bug, but it is ongoing at the >>>>> moment. Do you know if you'd be able to cancel builds that run long, or >>>>> are >>>>> you relying on the timeout to end bad processes? I'd love to help come up >>>>> with a workaround, as needed. >>>>> >>>>> Thanks again! >>>>> Anna >>>>> >>>>> >>>>> -- >>>>> Anna Nagy >>>>> Customer Support Engineer >>>>> supp...@travis-ci.com >>>>> >>>>> Visit https://www.traviscistatus.com/ for service status and uptime >>>>> details >>>>> >>>>> Travis CI GmbH, Rigaer Str.8, 10247 Berlin, Germany | GF/CEO: Mathias >>>>> Meyer, Joshua Kalderimis | Contact: cont...@travis-ci.org >>>>> <cont...@travis-ci.com> >>>>> Amtsgericht Charlottenburg, Berlin, HRB 140133 B | Umsatzsteuer-ID >>>>> gemäß §27 a Umsatzsteuergesetz: DE282002648 >>>>> >>>>> >>>>> On Mon, Sep 26, 2016 at 22:22:36 UTC, Raghav Kumar Gautam < >>>>> rag...@apache.org> wrote: >>>>>> >>>>>> I have seen that there are apache projects that take almost 2 hrs for >>>>>> builds and they go through. For e.g. >>>>>> >>>>>> https://travis-ci.org/apache/incubator-quickstep/jobs/144623355 >>>>>> >>>>>> >>>>>> >>>>>>
