Source: sbuild Version: 0.87.0 Control: affects -1 src:util-linux Dear sbuild Maintainers!
util-linux' upstream test suite tests very specific behaviours that involve the kernel and the underlying filesystem. To avoid broken tests, the testcases check for the filesystem they run on and skip tests if they are not prepared to run on a specific filesystem. The most problematic filesystem appears to be tmpfs, which is also the filesystem employed the Debian buildds. util-linux' test suite employs findmnt -T $PWD to check the filesystem. Unfortunately, in sbuild+unshare, this returns nothing. Apparently, this is because /proc/mounts has no entry for the directory in which the build runs. It would be good if we could a) not duplicate work done already upstream (f.e. by hunting for these test failures and disabling them in Debian), and b) not introduce strange cases into the upstream test suite (building in a directory that has no mount point in /proc/mounts is certainly "strange"). Please see what can be done about this. I'll note that in schroot this "just works". This bug report was triggered by an IRC discussion in #debian-buildd involving aurel32, josch, jochensp and me. The specific instance started as https://github.com/util-linux/util-linux/issues/3266 aka Debian bug #1086706. A previous instance of this is the "fadvise/count" test, which I've previously marked as known-failing in unshare, without realizing what the problem was - but it's the same problem really. Thanks, Chris
