Last modified: 2014-05-19 15:20:24 UTC
I planned to be bold :-) (cf. Gerrit change #104748), but looking at the console log it's too complicated for a quick fix. Premise: In case the testsuite fails for labs/toollabs, the generated tests/testsuite.log needs to be available for debugging. On Travis CI, I used: | dpkg-buildpackage -b -rfakeroot -uc || cat tests/testsuite.log as a test; in Jenkins, "artifacts" are probably the better way to go. However, artifacts are apparently archived at the end of the job (cf. https://integration.wikimedia.org/ci/job/labs-toollabs-debian-glue/lastBuild/console, 14:00:49), while tests/testsuite.log seems to be deleted directly after the build fails ("DEB_KEEP_BUILD_ENV is not set to 'true', not keeping build environment", 14:00:45). I'm not sure what options Jenkins offers to solve this.
Change 104964 had a related patch set uploaded by Tim Landscheidt: Define labs-toollabs-debbuild and dump tests/testsuite.log on failure https://gerrit.wikimedia.org/r/104964
Change 104964 had a related patch set uploaded by Tim Landscheidt: Define labs-toollabs-debbuild separately https://gerrit.wikimedia.org/r/104964
Asked at https://github.com/mika/jenkins-debian-glue/issues/79.
Change 104964 abandoned by Tim Landscheidt: Define labs-toollabs-debbuild separately Reason: In favour of https://gerrit.wikimedia.org/r/#/c/106295/. https://gerrit.wikimedia.org/r/104964
Tim, the tests are being run in a more or less isolated environment (cowbuilder) which is discarded at the end of the build. It might be possible to have some kind write access back to the host but I have no idea how to handle it. I think the easiest would be to have the test suite to dump the content of the file holding the tests results. Would that be an acceptable workaround for you?
