Team Build taking 10-15 minutes to generate list of changesets?

The "Generating list of changesets" step is taking anywhere from 10-15 minutes for our build. This seems odd considering there's only 6 actual changesets associated with the build. Granted there are something like 100 files associated with all those changesets, but is that really the problem? I wouldn't think the number of physical files would play into the changeset report. Getting the entire source tree takes Team Build less than a minute. Both a failed build and a successful build with the same set of changesets took equally as long so, I ruled the success of the build out of the equation.

Soooo, any ideas on exactly is going on here?

TIA,
Drew

[682 byte] By [DrewMarsh] at [2008-2-4]