perl-Net-Statsd-Server-0.17-1.fc22 can fails to build like this:
2014-07-18 16:52:50.000000 +0200 note Net::Statsd::Server: Initializing Net::Statsd::Server::Backend::Console backend
2014-07-18 16:52:50.000000 +0200 note Net::Statsd::Server: Initializing Net::Statsd::Server::Backend::Graphite backend
2014-07-18 16:52:50.000000 +0200 info AnyEvent: Autoloaded model 'AnyEvent::Impl::Perl', using it.
2014-07-18 16:52:50.319436 +0200 note Net::Statsd::Server: statsd server started on 0.0.0.0:40001 (v0.17)
2014-07-18 16:52:50.319499 +0200 note Net::Statsd::Server: manager interface started on 0.0.0.0:40002
2014-07-18 16:52:50.319549 +0200 note Net::Statsd::Server: metrics flush will happen every 1s
2014-07-18 16:52:51.319011 +0200 note Net::Statsd::Server: flushing metrics
Flushing stats at Fri Jul 18 16:52:51 2014
# Failed test 'Backend recognised our bad message bumping 'bad_lines_seen''
# at t/integration-tests/bad-message.t line 31.
# got: '0'
# expected: '1'
# Looks like you failed 1 test of 4.
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/4 subtests
This is a race in tests (or Test::Statsd module) and can be reproduced easily by inserting "sleep 10;" into t/integration-tests/bad-message.t between send_udp() and wait_and_collect_flush_data() invocations:
# Will wait until it receives the graphite flush
my $stats = $t->wait_and_collect_flush_data();
Such test is unreliable and fails randomly, especially on a loaded host.
Investigation of the CPAN Testers results at
show that this is a known issue.
All the tests under the integration-test directory seem prone to this type of failure.
I've temporarily removed the integration-test directory to allow builds to work again and notified upstream of the issue.
f22 has been built successfully using 0.17-2 at http://koji.fedoraproject.org/koji/taskinfo?taskID=7176906
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.
More information and reason for this action is here:
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.