[Buildbot-devel] Build is triggered for Build with 60-seconds tree-stable-trimer while still reporting a commits

[Mikhail Gusarov]

Hello.

I have observed an interesting issue: while getting ~4600 changes in 14
minutes (I know, it's not a typical workload, but I'm just setting
everything up), BuildBot happened to trigger a build with
tree-stable-timer set to 1 minute, after ~1000 changes. Changes were
supplied quite in linear fashion, 5 commits per second (apparently
bottleneck here was PBChangeListener itself, not commit processing script).

Another builder, which has 10 minutes tree-stable-timer, correctly has
not been triggered until all commits were pushed to buildmaster.

This happened two times in a row.

Environment: BuildBot 0.8.3p1, Debian Squeeze.

P.S: It's obviously a corner case, so I just wonder out of curiosity why
it might happen.