Test Timing and timeStats.txt

Alan Bateman Alan.Bateman at oracle.com
Sat May 11 01:39:44 PDT 2013

On 11/05/2013 03:36, Mike Duigou wrote:
> Hello;
> I discovered timeStats.txt just today and think that it is potentially quite useful. I couldn't find an exact definition but I assume the time quoted  is for all phases; @compile and @run.
> It would also be useful to see a version of summary.txt with the time information included. A CSV version of summary.txt with timing information would be potentially very useful for simple reporting.
> The task I was trying to accomplish was to script finding the slowest tests across a series of runs. Right now I would have to scrape the info out of the irregular form of output.txt or parse jtr files. Neither seems pleasant.
> Mike
timeStats.txt is useful, I've been using it since it was added to jtreg 
a few years ago.

For the slowest tests then my script uses this to report the slowest 50 

find JTwork -name "*.jtr" -exec grep elapsed= /dev/null {} \;|awk '{ 
print $1 }'|sed "s/elapsed=//g"|sort -t : -k 2 -n|tail -50

I think Jon has something too, I'm sure others do aswell. One thing to 
note is that the times can vary greatly across platforms, particularly 
tests for APIs/areas that have platform specific implementations or make 
use of platform specific facilities.


More information about the jtreg-use mailing list