Control: tags -1 +moreinfo +unreproducible Control: retitle -1 Bug#929715: strace: FTBFS: failure in lstat tests
Hi Lucas, On Wed, May 29, 2019 at 04:30:05PM +0200, Lucas Nussbaum wrote: >Source: strace >Version: 4.26-0.2 >Severity: serious >Tags: buster sid >User: debian...@lists.debian.org >Usertags: qa-ftbfs-20190529 qa-ftbfs >Justification: FTBFS in buster on amd64 > >Hi, > >During a rebuild of all packages in buster (in a buster chroot, not a >sid chroot), your package failed to build on amd64. Hmmm, that's odd. I've just built the current package in fresh amd64 and i386 chroots here, with no errors. Checking your log, the /dev/kvm error is not fatal and some tests are skipped without KVM access. The actual failures that you're seeing are from 4 stat functions, reported several times due to the build setup: $ grep ^FAIL: strace_4.26-0.2_testing.log | less FAIL: lstat.gen.test FAIL: stat.gen.test FAIL: lstat.gen.test FAIL: trace_lstat.gen.test FAIL: stat.gen.test FAIL: trace_stat.gen.test FAIL: trace_lstat.gen.test FAIL: trace_stat.gen.test FAIL: lstat.gen FAIL: stat.gen FAIL: trace_lstat.gen FAIL: trace_stat.gen FAIL: lstat.gen FAIL: stat.gen FAIL: trace_lstat.gen FAIL: trace_stat.gen so I've updated the bug title. Checking the log for more details, I'm just seeing what *looks* like whitespace differences in the test output. But I don't see it here on my system, which is surprising. Is there anything at all special about your test setup that I should ba aware of? I'm pondering if there's maybe a locale setup difference or something, but that's just a guess OTTOMH...! -- Steve McIntyre, Cambridge, UK. st...@einval.com Google-bait: http://www.debian.org/CD/free-linux-cd Debian does NOT ship free CDs. Please do NOT contact the mailing lists asking us to send them to you.
