[Buildbot-devel] RFC: more flexible web status display

Neal Norwitz nnorwitz at gmail.com
Wed Apr 12 08:07:37 UTC 2006

On 4/12/06, Brian Warner <warner-buildbot at lothar.com> wrote:
> If you see a specific build that didn't pick up all the changes you thought
> it should, give me the build number and I'll take a look. While the Waterfall
> may not be able to show much historical data, the just-one-build URLs *do*
> make it each to look into the past, and those pages (linked from the "Build
> #NNN" text in the yellow box that starts each build) show all the Changes
> that went into each build.

It's quite possible I'm asking for something that's not part of the
design.  Here's an example:

For the first build column:  sparc solaris10 gcc trunk.

06:44  	tim.peters happened during build 366.
06:56  	neal.norwitz happened during the same build 366.

build 367 started at 06:57 with only tim's changelist, not mine.  I
would like both of the changes to be consolidated.  If I understand
you correctly, the current impl puts them in separate builds by
design.  If the next build started at 07:51 (ie 5 miinutes after my
checkin) the changes should have been consolidated?

I think 5 minutes is a reasonable stable-timer for us.  But since our
tests take over an hour to run, if our changes were 6 minutes apart,
bb would get further and further behind, unless there is some
consolidation.  I realize this means the blamelist become less
effective.  But it means we don't have wait several hours for a

Hope this makes sense.  Are there any other config options besides the


More information about the devel mailing list