Kitware
Multiple Projects with Same Site and Build Names Append Submissions to Single Project
I have a CDash 2.5.0 server that I have set up with three projects being tracked on it. All of the testing is done on the server, so they all have the same site name, and two of the three use gfortran 5.4.0, while one uses gfortran 4.8.5. All of the projects have the same naming convention for the build name which is OperatingSystem-Compiler-CompilerVersion-ShortCompilerVersion_[SERIAL|MPI]_[DEBUG|RELEASE] (e.g. Linux-GCC-4.8.5-GNU48_SERIAL_DEBUG). Because the two projects have the same name, the first project that is run nightly creates the correct entry for the correct project name at the correct project url. The second project runs and the submission ends up being appended onto the first project name's/url's nightly entry, while leaving the second project's url empty. The project that uses gfortran 4.8.5 creates the correct entry for the correct project name and url as well.
I tested that the naming convention was the issue by creating a gfortran 5.4.0 build for the project that uses version 4.8.5 and ran the new ctest script. Sure enough, the project submission was placed in the first project name's/url's nightly entry as well.
It appears that even though the submission names and url addresses are different for all three projects, the location to submit the nightly test results does not account for the project name and only looks at the site name and build name, or perhaps just the build name. I looked over the fixes of your recent releases, and didn't find anything that appeared to match what I am seeing.
Let me know if this issue was fixed in a later version or if you need any other information to reproduce the issue.
In the mean time, a workaround I can implement is to make all of the build names unique. Annoying, but effective.
Confirmation that renaming the build name for the project that was displaying empty results has fixed the issue and is now properly displaying the nightly runs as expected.
@djabaay
I think this is a special property of "Nightly" builds. "Experimental" builds do not have this property. I assume that is because "Nightly" builds are not expected to run more than once a day, and if they do, then you either have something to add, or you have a bug in your setup.
Although I personally also do not really understand what is the practical motivation behind this logic. I have never had a set up that would need appending tests.
