Hi, On Tue, Oct 09, 2018 at 09:59:29PM +0200, Paul Gevers wrote: > With a recent upload of munin the autopkgtest of munin fails in testing > when that autopkgtest is run with the binary packages of munin from > unstable. It passes when run with only packages from testing. In tabular > form: > debian/tests/munin-node/02.plugins.t .. > not ok 1 - request list of configured plugins > # > # all_plugins=$(printf "%s\n" list quit | nc localhost munin | grep -v > "^#") > # # ignore non-predictable names (e.g. related to the network > interfaces of the environment) > # all_without_network_interfaces=$(echo "$all_plugins" | sed "s/ > if_\w\+//g") > # [ "$all_without_network_interfaces" = "cpu df df_inode entropy forks > fw_packets interrupts irqstats load memory netstat open_files > open_inodes proc_pri processes swap threads uptime users vmstat" ] > # > # failed 1 among 1 test(s) > 1..1 > Dubious, test returned 1 (wstat 256, 0x100) > Failed 1/1 subtests
I did a manual test in a chroot, and it seems the 'netstat' plugin is missing in the list of plugins. This is because the 'netstat' command isn't available when munin-node is installed (the list of plugins in initialised in postinst). An easy fix would probably be to have the test depend on net-tools. Changing the test to show the difference between both lists of plugins would probably be nice. This is a bug in the test, not in the package. The list of plugins is the same in testing, but this test isn't in the old version of the package. Cheers, Ivo