Created attachment 556414 [details] build.log (2.0.34) [...] not ok 2 - Resolve IPv4 hostname - no exception # Failed test 'Resolve IPv4 hostname - no exception' # at t/munin_node_configure_hostenumeration.t line 26. not ok 3 - Resolve IPv4 hostname - got a value # Failed test 'Resolve IPv4 hostname - got a value' # at t/munin_node_configure_hostenumeration.t line 27. ok 4 - Resolve IPv4 numeric address - no exception ok 5 - Resolve IPv4 numeric address - got a value ok 6 - Class C is expanded correctly ok 7 - Single IP ok 8 - No netmask ok 9 - Single IP ok 10 - IP-based CIDR range ok 11 - Single hostname ok 12 - Hostname-based CIDR range ok 13 - Single FQDN ok 14 - FQDN-based CIDR range ok 15 - Multiple specifications # Looks like you failed 2 tests of 15. [...] Test Summary Report ------------------- t/munin_node_configure_hostenumeration.t (Wstat: 512 Tests: 15 Failed: 2) Failed tests: 2-3 Non-zero exit status: 2 Files=22, Tests=523, 7 wallclock secs ( 0.12 usr 0.06 sys + 1.16 cusr 0.35 csys = 1.69 CPU) Result: FAIL Failed 1/22 test programs. 2/523 subtests failed. make: *** [Makefile:474: test-node] Error 255
Created attachment 556416 [details] build.log (2.0.38)
Created attachment 556418 [details] build.log (2.0.43)
Created attachment 556420 [details] emerge --info
It looks like these may fail due to lack of network access and/or DNS service. Can you confirm that that is the case in your test environment? Upstream made some changes to these tests so this should be fixed in the next upstream release (2.0.44). I'll wait for that version to come out before making any changes.
*** This bug has been marked as a duplicate of bug 624026 ***
