Someone has been running regression tests on develop with the name “Debian-sid”, I believe they have a space in the path to the regression suite, which is causing it to fail. The job gets run like clockwork, shame that it isn’t uploading any useful results. Either the operator of this builder should change the path so that it does not have a space, or the regression suite should be updated to tolerate it. I tried once to figure out where in the test suite the path got mangled, but was unsuccessful, maybe someone more familiar with it could take a look? - Thomas
On September 10, 2014 06:38:43 PM Suckow, Thomas J wrote:
Someone has been running regression tests on develop with the name “Debian-sid”,
That's me. I should put contact details in the config somewhere ...
I believe they have a space in the path to the regression suite, which is causing it to fail.
No, there are no spaces. The root directory contains hyphens and may be overly long (/var/lib/jenkins/jobs/Boost-Testing-develop-64). Could either of those cause a problem? The paths underneath are, I expect, the same as everyone else's.
The job gets run like clockwork, shame that it isn’t uploading any useful results.
Yeah, it is a shame.
Either the operator of this builder should change the path so that it does not have a space, or the regression suite should be updated to tolerate it. I tried once to figure out where in the test suite the path got mangled, but was unsuccessful, maybe someone more familiar with it could take a look?
- Thomas
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Someone has been running regression tests on develop with the name “Debian-sid”,
That's me. I should put contact details in the config somewhere ...
Ditto
I believe they have a space in the path to the regression suite, which is causing it to fail.
No, there are no spaces. The root directory contains hyphens and may be overly long (/var/lib/jenkins/jobs/Boost-Testing-develop-64). Could either of those cause a problem? The paths underneath are, I expect, the same as everyone else's.
I also run it under Jenkins, I had an issue that my job name had a space. This was apparent in the bjam.log that is created as a series of "Cannot find file bar/test_log.xml", "Cannot find file foo" in the console output.
The job gets run like clockwork, shame that it isn’t uploading any useful results.
Yeah, it is a shame.
Note that for me, develop appears to be failing ATM. - Thomas
On September 17, 2014 06:16:58 PM Suckow, Thomas J wrote:
No, there are no spaces. The root directory contains hyphens and may be overly long (/var/lib/jenkins/jobs/Boost-Testing-develop-64). Could either of those cause a problem? The paths underneath are, I expect, the same as everyone else's.
I also run it under Jenkins, I had an issue that my job name had a space. This was apparent in the bjam.log that is created as a series of "Cannot find file bar/test_log.xml", "Cannot find file foo" in the console output.
No, for me the build completes successfully. The xml results file locally seems intact: there are 8779 "<test-log>" entries covering presumably all the libraries, yet the web page [1] only contains entries for "build". Coincidentally (?) that is the first library in the xml file. I presume something has gone wrong on the receiving side, but it's curious to me that only my test results are affected. It's been like that ever since the switch to git. [1] http://www.boost.org/development/tests/develop/developer/summary.html -Steve
participants (2)
-
Steve M. Robbins -
Suckow, Thomas J