Single Mercurial push triggers multiple builds

I'm observing that pushing a large number of changes into a mercurial repo sometimes triggers multiple builds of the same build task. The first build will contain a small subset of the changes, and only eventually will all changesets be included by later builds.

This is very confusing behavior, as the intermediate builds will often fail due to being random intermediate states of the source tree.