On Thu, 3 Jul 2014, Greg Troxel wrote:
Is there an easy way to look for tests that take a lot longer? Perhaps running the tests on a checkout before the suspect change, and after, and loading both the csv formats in a spreadsheet, and looking at the ratio of execuation times? It would be interesting to have a database of historical norms for each test and some way to warn if a value is consistently outside them.
Yeah, this has been on my To-Do list for a long time. I just haven't had enough time to implement.
------------------------------------------------------------------------- | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | Customer Service | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com | | Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net | | Kernel Developer | | pgoyette at netbsd.org | -------------------------------------------------------------------------