On 2024-07-24 09:11, Jochen Sprickerhof wrote:
While you are correct that the buildd did succeed but please note that
the bug is not fixed and can still be reproduced with sbduild
--chroot-mode=unshare and on the reproducible builds infrastructure, as
noted by Santiago above. Please also note that the buildds started
switching to the sbuild unshare backend so this package will FTBFS in
future.
Thanks,
I've taken a closer look at the tests, and am able to reproduce them
with
unshare -nr go test ./...
Looking closer at the tests, it appears that they are iterating over all
installed network interfaces, and try to query them for statistics. In
that 'unshare -nr' context, they still find a loopback interface, but
commands to query fail with "operation not supported".
Clearly, those tests don't make sense in such an environment.
Jochen, what's the best way to detect this situation in a test, so that
it can decide to do a "t.Skip(...)" instead of failing? I'm looking for
a way to avoid having to disable the tests altogether to not loose test
coverage on machines that don't run in unshare mode.
on a side note, I'd like to express concerns with having the buildds
enable unshare mode becaues it evidently reduces test coverage, as shown
in this context.
-rt
