It dropped back down to 10 minutes and has slowly crept back up to 17 minutes.

UnitTest stage is guaranteed to increase over time.  we want that as it indicates people are writing more unittests, and we have more packages with new unittests.

of course that's not a guarantee that's the reason for a lot of these increase in times.  i think we need finer grained metrics here before trying to make decisions.

We took a look at this as a group in the training today. This graph shows where we are over the last 36 weeks: http://shortn/_etAHaGBpxL . There's some really strange things going on. In particular, we had a 2 weeks in April where everything was wonderful and then we go worse again. Over the last few weeks, things have gotten better but not as low as they were 36W ago.

Generally, unit test times should be going up because people are writing more tests. We shouldn't be seeing big swings like this, though.

I think we should have someone on the Build team take a look at what's going on in the package corpus. Mike, can you delegate to someone to investigate?