[Buildbot-devel] Send only one mail even when several builds fail

[Dustin J. Mitchell]

On Sun, Oct 24, 2010 at 8:22 PM, tom fogal <tfogal at sci.utah.edu> wrote:
> The aggregation information is already *in* my master config, by way of
> schedulers.  If I have to configure it somewhere else, they're going to
> get out of sync.

And a queue analyzer could look for a single "schedulername" property
across multiple builds.

> Even worse, some builder might not finish, or even start -- e.g.
> my osuse machine loses its net connection or something, the slave
> disconnects.. and then my client, which is waiting for all such
> builders to finish, just locks.  We could solve this by adding a way to
> query if slaves are up, but then I have to *do* that.

Yes, this is where things get bad.  If your builds are not
well-correlated in time, then your notification system has to maintain
an arbitrary number of partially-correlated event sets, which brings
about the need to ensure those result sets don't sit around forever -
for example, in the case of a downed slave, cancelled build, etc.

Dustin