Most of the Gump errors are due to timeout (exceeded 1 hour). We should understand why the Gump tests are taking longer (slower computer, slower code, more test coverage or corpus).
In the mean time, we should increase the Gump timeout so that it can run to completion. On Sep 8, 2016 2:00 PM, "Andreas Beeker" <[email protected]> wrote: > I'm currently on vacation ... if nobody else jumps in, I'll roll the > release on the 14.09.2016. > As I'm not closely paying attention whats happening, could someone please > have a look > at the gump errors, i.e. if those are relevant for the release ... > > Andi > > On 06.09.2016 22:25, David North wrote: > > Sorry, you're quite right - I am unable to get this done at the moment - > > somebody else, please take over if you can. > > > > Thanks, > > David > > > > On 05/09/16 21:16, Dominik Stadler wrote: > >> Hi, > >> > >> David, please let someone else step in if you cannot run the next > >> release-build yourselves anytime soon. > >> > >> Dominik. > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
