MantisBT - CDash
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0010170CDashpublic2010-01-20 14:012010-01-20 14:22
ReporterLuis Ibanez 
Assigned To 
PrioritynormalSeverityfeatureReproducibilityhave not tried
StatusnewResolutionopen 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0010170: Automatic estimation of TIMEOUT times for test based on statistics of previous runs
DescriptionCDash currently stores statistics on the amount of time that it take to run a test in a particular machine. In this feature request, a machine (or its manager) could request from CDash a file with these time statistics in order to use them for computing TIMEOUT values on a test-by-test basis.
Steps To Reproduce
Additional InformationCurrently maintainer of dashboard machines do not have a clear reference for how to set up their TIMEOUT values. In most cases they are set up to generously large values in order to avoid problems, but when a machine administrator has to fine tune this values, it has to do so on a set of trial and error experiments that can take several days.

CDash already stores statistics on the actual time that it takes to run a tests in a given machine. If that data is made available to CTest (upon request), then CTest could be modified in order to fine tune the estimation of TIMEOUT ona test-by-test basis.
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-01-20 14:01Luis IbanezNew Issue
2010-01-20 14:22David ColeNote Added: 0019224

Notes
(0019224)
David Cole   
2010-01-20 14:22   
There is an easy way to gather this data by hand in the forthcoming CDash 1.6 using the "queryTests.php" page and filters. The following hyperlink shows the passing test results for a given test in VTKEdge on a given site/buildname combination for the last 30 days... :-)

https://www.kitware.com/CDash/queryTests.php?project=VTKEdge&filtercount=5&showfilters=1&filtercombine=and&field1=testname/string&compare1=61&value1=PaintbrushTest2&field2=status/string&compare2=61&value2=Passed&field3=site/string&compare3=61&value3=Cairparavel.kitware&field4=buildname/string&compare4=61&value4=all-release-VS8&field5=buildstarttime/date&compare5=83&value5=30%20days%20ago [^]

It may or may not be easily machine readable in this format, but you can easily scan it as a human being and get a fairly good idea about the timing of the test on that build for the number of days specified...