View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
0015383 | CDash | (No Category) | public | 2015-01-30 06:04 | 2015-02-01 18:18 | ||||||||
Reporter | Vincent Hobeïka | ||||||||||||
Assigned To | |||||||||||||
Priority | normal | Severity | minor | Reproducibility | always | ||||||||
Status | new | Resolution | open | ||||||||||
Platform | x86_64 | OS | debian | OS Version | Debian 7.8 | ||||||||
Product Version | |||||||||||||
Target Version | Fixed in Version | ||||||||||||
Summary | 0015383: CDash report spanning over two rows due to a / in the CTEST_SITE | ||||||||||||
Description | When adding a / in a CTEST_SITE inside a CDash dashboard script it seems that CDash is doing weird trimming things when dealing with the uploaded xml files. For instance, having a CTEST_SITE named GNU/Hurd will produce two rows in the CDash project page. One row will have the correct CTEST_SITE GNU/Hurd and will only show the results of the update command. The other row will have a wrong CTEST_SITE with its / trimmed off GNUHurd. It will display the remaining results (configure, build and tests) An example is visible at http://my.cdash.org/index.php?project=vera%2B%2B&date=2015-01-29 [^] | ||||||||||||
Steps To Reproduce | Put a slash in the CTEST_SITE. Run a nightly build and look at the results. | ||||||||||||
Additional Information | Don't pay attention at the Hurd thing. I have tested this on a regular Debian 7.8 with linux too. The problem remains. vincent@hal:~$ ctest --version ctest version 3.0.2 CDashPro 2.3.0 (my.cdash.org) | ||||||||||||
Tags | No tags attached. | ||||||||||||
Attached Files | |||||||||||||
Relationships | |
Relationships |
Notes | |
(0037869) David Cole (manager) 2015-01-30 12:32 |
This is because CTEST_SITE is used directly without any substitution as a component of a filename on the server. So if you put "/" in it, the filename generation does not work properly because there is most likely no directory with the name that comes before the "/"... The easiest "solution" for this is for you to not use a "/" in the CTEST_SITE value. (Can you just use "-" or "_" instead? Or must you use "/"?) It could be fixed in the code to automatically escape it to something before constructing a filename, but it might be hard to convince yourself you've found all of the places it needs to happen. Hopefully, it's only one, but I suspect there may be a handful of places throughout the code building filenames using the site as a piece... |
(0037875) Vincent Hobeïka (reporter) 2015-02-01 18:11 |
Hi! Thanks for your hints and light over this issue. Indeed, I thought it would be some path management related error and a missing escape somewhere. I have already reported that kind of error in the past and it was fixed. Regarding my site I have already changed to something else than a "/". Yet, I think an un-escaped string which can affect a path on a server is a kind of issue that might need to be reported. Hence my bug report. Since that kind of error has already been fixed in the past I thought it was legit to report it. Thanks for your concern. Best regards |
(0037876) Vincent Hobeïka (reporter) 2015-02-01 18:18 |
For the record, it seems a very close defective behavior was fixed in version 2.0: http://public.kitware.com/Bug/view.php?id=12913 [^] Best regards |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
2015-01-30 06:04 | Vincent Hobeïka | New Issue | |
2015-01-30 12:32 | David Cole | Note Added: 0037869 | |
2015-02-01 18:11 | Vincent Hobeïka | Note Added: 0037875 | |
2015-02-01 18:18 | Vincent Hobeïka | Note Added: 0037876 |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |