← Back to team overview

dolfin team mailing list archive

Re: Buildbot trouble

 

On Thu, Nov 10, 2011 at 02:55:26PM +0100, Johannes Ring wrote:
> On Thu, Nov 10, 2011 at 2:43 PM, Anders Logg <logg@xxxxxxxxx> wrote:
> > On Thu, Nov 10, 2011 at 02:41:57PM +0100, Martin Sandve Alnæs wrote:
> >> On 10 November 2011 14:37, Anders Logg <logg@xxxxxxxxx> wrote:
> >> > On Thu, Nov 10, 2011 at 02:14:18PM +0100, Johannes Ring wrote:
> >> >> On Thu, Nov 10, 2011 at 1:58 PM, Anders Logg <logg@xxxxxxxxx> wrote:
> >> >> > On Thu, Nov 10, 2011 at 11:36:56AM +0100, Johannes Ring wrote:
> >> >> >> On Thu, Nov 10, 2011 at 10:33 AM, Anders Logg <logg@xxxxxxxxx> wrote:
> >> >> >> > Some new unit tests are failing on the buildbot. My personal buildbot
> >> >> >> > is timing out as usual so I haven't been able to test there.
> >> >> >>
> >> >> >> It is the chapter_1 unit test from the book that is timing out. I
> >> >> >> tried to run this on the buildbot now (after running instant-clean)
> >> >> >> and it took almost five minutes to complete this test. The buildbot is
> >> >> >> set to time out if there is no output for 20 minutes and I would
> >> >> >> imagine that the chapter_1 unit test could run for 20 minutes or more
> >> >> >> when the buildbot is busy during the nightly builds. In fact, your
> >> >> >> buildbot did not time out last night when the force build button was
> >> >> >> clicked and the buildbot was less busy.
> >> >> >
> >> >> > I've reduced the mesh sizes now, but it's strange that it takes 5
> >> >> > minutes on the buildbot. It takes 44 seconds on my 2 year old laptop.
> >> >> > It's down to 3 seconds now.
> >> >>
> >> >> Yes, but I guess you didn't run instant-clean first? Without
> >> >> instant-clean it took 51 seconds on the buildbot.
> >> >
> >> > Aha... It takes 5 min for me now even after the reduction in mesh
> >> > sizes if I run instant-clean.
>
> It would help to split the test into smaller tests.

It's possible, but I'd like to avoid it. It's complex enough as it is.

> >> > Would it be a good idea not to run instant-clean on the buildbots when
> >> > pressing Force build?
> >>
> >> Or even with commit-triggered builds. Nightly full rebuilds is good,
> >> but I think there's value in faster faster incremental builds also.
> >> If it succeeds on an incremental build and fails in the nightly build
> >> we have a critical bug in the build system or instant cache system.
> >
> > Sounds reasonable.
>
> I don't have a way to differentiate between a nightly build, a
> commit-triggered build or a forced build in the current buildbot
> setup. I can take a look later to see how hard it would be to add.

ok.

--
Anders


References