MantisBT - CDash
View Issue Details
0011037CDashpublic2010-07-26 11:582010-07-26 17:46
Mathieu Malaterre 
 
normalminoralways
newopen 
 
 
0011037: Computation of path to cvsweb for generated files
Hi there,

  We have had a report from a user where cdash incorrectly tries to compute path for generated file. For example on this page you can see a cvsweb link to gdcmConfigure.h which is a generated file from gdcmConfigure.h.in:

http://www.cdash.org/CDash/viewBuildError.php?type=1&buildid=672214 [^]

  CDash attempts to compute it's cvsweb URL into:

http://gdcm.svn.sourceforge.net/viewvc/gdcm/trunk//Source/Common/gdcmConfigure.h?view=log [^]

  Which is of course wrong.

It would be nice if CDash would properly handle the fact that the file is generated by looking at the full path, in this case:

  "GDCM-clang-dbg-i386/Source/Common/gdcmConfigure.h"

  to detect that file underneath the binary "GDCM-clang-dbg-i386" might not be located in the cvs/svn repository.

Thanks !
No tags attached.
Issue History
2010-07-26 11:58Mathieu MalaterreNew Issue
2010-07-26 12:00Mathieu MalaterreNote Added: 0021482
2010-07-26 17:46Niels DekkerNote Added: 0021488

Notes
(0021482)
Mathieu Malaterre   
2010-07-26 12:00   
BTW I am not asking to compute the path to gdcmConfigure.h.in.

I am solely asking that the cvsweb path should not be computed at all.
(0021488)
Niels Dekker   
2010-07-26 17:46   
Mathieu Malaterre wrote:
> I am not asking to compute the path to gdcmConfigure.h.in.

Why not? I think it would be very convenient if CDash would provide the full path to the input file of a CONFIGURE_FILE(<input> <output>) call, if the output file triggers a compile error.

In this particular case, can't CDash possibly figure out that gdcmConfigure.h is generated based on gdcmConfigure.h.in? The correct link should be http://gdcm.svn.sourceforge.net/viewvc/gdcm/trunk//Source/Common/gdcmConfigure.h.in?view=log [^]

My 2 cents, Niels