Heikki Toivonen wrote:
Alec Flett wrote:Yup, we have a bug on that. However, I also think that regressions that are large enough to notice immediately after checkin can and should be noticed and addressed in some manner that same day. I'm glad there's a bug, but I totally disagree with this assertion - I hope it doesn't delay the implementation of the bug. I think it completely believable that we have a 50% performance hit and have nobody notice it for a week - tinderbox only shows deltas between the last 2 builds so such a performance change may be visible for 2-3 hours. For instance, say I broke something yesterday at 5pm, and the delta shows up at 7pm and displays until 9pm. Nobody is going to notice that. We'll all come in in the next morning and see that some of the performance numbers are red... but aren't there always SOME numbers red? Only someone such as yourself, who knows the tests well enough to know what's normally red and whats not, will notice that something is amiss. Then, days later when you or someone else notices, its a huge effort to try to wade through the per-day performance data to try and figure out when/where this happened... Alec |
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
