On Wed, Jul 24, 2019 at 02:09:35PM -0400, Boyuan Yang wrote: > 在 2019-07-24三的 19:44 +0200，Simon Richter写道： >... > > This is an error caused by network environment. The "find" test runs both > > an Avahi lookup and an USB scan (but largely ignores the results, as none > > of the devices found during that scan matches the "DUMMY" filter), > > depending on the autobuilder configuration that triggers a security policy, > > which makes the test fail. > > > > I have no really good idea how to keep the test meaningful and stop it from > > failing in more restricted environments.
At least in Debian it shouldn't be run. >... > In this case I guess we could make tests optional so that the whole build will > not fail even if there's some test failures. In this way at lease we could > have some usable libraries in the archive. >... That's bad for two reasons: 1. Ignoring all test results makes the whole tests rather useless since noone will notice when other tests regress. 2. It still keeps a release critical bug, policy says[1]: For packages in the main archive, required targets **must not attempt** network access, except, via the loopback interface, to services on the build host that have been started by the build. I noticed right now due to the maintainer upload missing the NMUs, but this should really be fixed properly by disabling this specific test. > Thanks, > Boyuan Yang cu Adrian [1] https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules
