Hi Holger, On 10/19/18 20:40, Holger Levsen wrote: > On Fri, Oct 19, 2018 at 08:29:34PM +0200, Paul Gevers wrote: >> The issue doesn't seem to be fixed with your previous upload. > > yes, I noticed.
O, good. >> https://ci.debian.net/data/autopkgtest/testing/amd64/m/munin/1173542/log.gz >> >> 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 don't understand this output and thus I dont find it helpful at all. Neither do I. But I try to always copy/paste these messages in case they do make sense to the maintainer. (and also because our logs are cleaned up after a couple of months). > Do you see something in it (which I'm missing)? No. > I also don't understand debian/tests/munin-node/02.plugins.t at all, eg > how to make generate more output, to tell which plugin failed > testing... Sorry, but I can't help you with this (ENOTIME). I can only suggest that if this is a NEW test you could disable it until you understand it. I mean a new test doesn't count as a regression. Paul
signature.asc
Description: OpenPGP digital signature
