We'll need to build timeouts into our own reporting infrastructure - it shouldn't be too bad but we just need to script it. Unfortunately the Jenkins plug-in is either "all or nothing" in what it reports, so we can't have it report timeouts unless we want all the other fairly noisy messages from it.
On Fri, Aug 15, 2014 at 11:44 AM, Nicholas Chammas < [email protected]> wrote: > Shivaram, > > Can you point us to an example of that happening? The Jenkins console > output, that is. > > Nick > > > On Fri, Aug 15, 2014 at 2:28 PM, Shivaram Venkataraman < > [email protected]> wrote: > >> Also I think Jenkins doesn't post build timeouts to github. Is there >> anyway >> we can fix that ? >> On Aug 15, 2014 9:04 AM, "Patrick Wendell" <[email protected]> wrote: >> >> > Hi All, >> > >> > I noticed that all PR tests run overnight had failed due to timeouts. >> The >> > patch that updates the netty shuffle I believe somehow inflated to the >> > build time significantly. That patch had been tested, but one change was >> > made before it was merged that was not tested. >> > >> > I've reverted the patch for now to see if it brings the build times back >> > down. >> > >> > - Patrick >> > >> > >
