Performance Data Collection - part 3

Below is an excerpt of the data being generated by the unit tests and collected by the Tinderbox scripts:

Chandler|ahukini-full-osx|20041230|031501|Load pack                      |      2 | 1.27061 | 0.63531
Chandler|ahukini-full-osx|20041230|031501|application.TestAllParcels     |      1 | 43.77684 | 43.77684
Chandler|ahukini-full-osx|20041230|031501|Totals:                        |      3 | 45.04746 | 15.01582
Chandler|ahukini-full-osx|20041230|031501|Load pack                      |      2 | 0.46807 | 0.23403
Chandler|ahukini-full-osx|20041230|031501|application.TestAllParcels     |      1 | 15.33679 | 15.33679
Chandler|ahukini-full-osx|20041230|031501|Totals:                        |      3 | 15.80486 | 5.26829

The first thing I noticed was that each test appears twice, but then I remembered that the unit tests are run twice: once for debug and once for release IIRC. I will have to figure out a way to flag which is which since the values are very different.

Note: The "Totals:" line will be gone from subsequent runs as I've added a verbose parameter to the tools.timings.result() routine

The next step you ask? Now to collect the information into a database so it can be queried and mined for information.