Control: retitle -1 fix apts tests failing on ci.debian.net Hi, On Thu, Jul 17, 2014 at 08:02:46AM +0200, Niels Thykier wrote: > Your package includes a DEP-8 test, but currently it fails with a[1]: > > """ > checking for gtest/gtest.h... no > configure: error: failed: I need gtest to build tests > buildlib/configure.mak:58: recipe for target 'build/config.status' failed > """ Sorry that this took so long… The missing depenency was added quickly, but that wasn't the problem causing the failures since the dawn of time… (The stuff needing this dependency isn't actually build by the tests run on debci, our homegrown buildsystem is just not clever enough…) I finally managed to work on this and would subsequently like to raise some questions/remarks regarding debci/ci.d.n to Antonio as I am stuck. First an observation I should probably report as a bug against debci instead, but I will mention it anyhow: debci (and/or the stuff below) seems to not "protect" itself against an agressive umask. I have 027 on my test system so I get various permission issues for files created by 'debci setup' in the chroot like the config files for apt/dpkg. Following the documentation to the letter gives me as the configured normal user even with a less agressive umask setup of 022 a python traceback anyhow, but it runs as root so enough "complaining" for now: The problem is that the tests pass on my system, while they fail on ci.d.n. Specifically just one testcase: >>>> Run Testcase (13/141) test-apt-get-changelog […] Test for correctness of file apt.changelog … -:::::::::::::: -/tmp/apt-changelog-xnLT3Schangelog -:::::::::::::: apt (1.0) stable; urgency=low * Initial release FAIL […] <<<< What the test does is redirecting the output of "apt-get changelog" to a file and compare that file with what should have been downloaded. The command uses the sensible-pager to display the file and in the ci.d.n tests the configured pager seems to issue this "helpful" header while it doesn't if you run the tests at home. I was told that on the ubuntu instance this works as well (beside that it works on travis-ci and my buildbot instance), so while we could workaround this of course, I wonder if this shouldn't "just work" and there is something wrong in the setup of ci.d.n or am I just not seeing the elephant in the room… After all, I doubt apt is the only command which runs stuff through a pager at times. Thanks for your help, debci & best regards David Kalnischkies
Attachment:
signature.asc
Description: Digital signature