MantisBT - CDash
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0009991CDashpublic2009-12-02 10:362010-02-21 12:31
ReporterDave DeMarle 
Assigned ToJulien Jomier 
PrioritynormalSeverityfeatureReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version1.6 
Summary0009991: show which failures are new
DescriptionOn the failures pages, can we now indicate which failures are new?

Since, 0006841 the main page shows how many new errors there are. This is a great help in figuring out that I've caused regressions. Especially once 0008965 propagates in and I can see which submissions include my changes. Now I want to see which regressions are my fault. This is problematic if there are already lots of failures.

For instance http://www.cdash.org/CDash/viewTest.php?onlyfailed&buildid=484270 [^] shows that 30 tests failed. I know from the front page that 2 of these are new, but to find out what those two are, I have to use the previous link and then manually compare line by line.

Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-12-02 10:36Dave DeMarleNew Issue
2009-12-02 10:39Julien JomierStatusnew => assigned
2009-12-02 10:39Julien JomierAssigned To => Julien Jomier
2009-12-02 10:40Julien JomierNote Added: 0018644
2009-12-02 10:47Dave DeMarleNote Added: 0018645
2009-12-02 10:49Julien JomierNote Added: 0018646
2009-12-23 22:03Julien JomierNote Added: 0018993
2009-12-23 22:03Julien JomierStatusassigned => resolved
2009-12-23 22:03Julien JomierFixed in Version => 1.6
2009-12-23 22:03Julien JomierResolutionopen => fixed
2010-02-21 12:31Julien JomierStatusresolved => closed

Notes
(0018644)
Julien Jomier   
2009-12-02 10:40   
If we are talking about tests failures, this is already implemented (will be in 1.6). For errors and warnings this is tricky because there is no real way to know if the error is different just by looking at the logs. Let me know.
(0018645)
Dave DeMarle   
2009-12-02 10:47   
I was thinking of problems in general. As a user it doesn't matter to me if I've broken a test, a compile or introduces a compilation warning. I've got to fix it in any case. The problem is usually recognizing that I've broken it. Any additional help that cdash can give me is worthwhile from the my perspective.
(0018646)
Julien Jomier   
2009-12-02 10:49   
Definitely understand your point and with 1.6 we aim to fix this issue. I'll see if there is a way to detect new errors and warnings as well. Thanks for the report!
(0018993)
Julien Jomier   
2009-12-23 22:03   
Fixed for tests and build errors