MantisBT - CDash
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0009174CDashpublic2009-06-17 13:082010-02-21 12:31
ReporterMatthias Brantner 
Assigned ToJulien Jomier 
PrioritynormalSeverityminorReproducibilityN/A
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version1.6 
Summary0009174: tracing regressions
DescriptionIt would be great if CDash could provide a regression tracing functionality. For instance, we want to know if a commit makes particular tests fail. Although, CDash does report an de-/increase of failing/passing tests in the "Fail" and "Pass" columns this is unfortunately not good enough for us because CDash doesn't tell us if we had a regression. For instance, a commit could break one test but make two others pass.

The main page should immediately tell if a commit caused regressions (e.g. no pro- and regressions). If yes, those could be traced down to the commit making a particular test/regression fail.
Steps To Reproduce
Additional InformationAlso see the thread "tracing regressions in cdash" on the cdash mailinglist (date: June 17th 2009)
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-06-17 13:08Matthias BrantnerNew Issue
2010-01-15 14:20Julien JomierStatusnew => assigned
2010-01-15 14:20Julien JomierAssigned To => Julien Jomier
2010-01-15 14:20Julien JomierNote Added: 0019152
2010-01-15 14:20Julien JomierStatusassigned => resolved
2010-01-15 14:20Julien JomierFixed in Version => 1.6
2010-01-15 14:20Julien JomierResolutionopen => fixed
2010-02-21 12:31Julien JomierStatusresolved => closed

Notes
(0019152)
Julien Jomier   
2010-01-15 14:20   
CDash now shows + and - for tests, errors and warnings meaning what has been fixed and what has been broken.