Bug 1204870 - perl-Gearman-Client-Async-0.94-19.fc23 FTBFS: t/async.t fails randomly
Summary: perl-Gearman-Client-Async-0.94-19.fc23 FTBFS: t/async.t fails randomly
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Gearman-Client-Async
Version: 23
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Petr Pisar
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2015-03-23 16:27 UTC by Petr Pisar
Modified: 2016-12-20 13:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2016-12-20 13:23:53 UTC
Type: Bug

Attachments (Terms of Use)

Description Petr Pisar 2015-03-23 16:27:40 UTC
perl-Gearman-Client-Async-0.94-19.fc23 sometimes fails to build in F23:

+ make test
PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
Use of "goto" to jump into a construct is deprecated at /usr/share/perl5/vendor_perl/Gearman/Util.pm line 164.
Use of "goto" to jump into a construct is deprecated at /usr/share/perl5/vendor_perl/Gearman/Util.pm line 164.
t/allinone.t ...... ok
Use of "goto" to jump into a construct is deprecated at /usr/share/perl5/vendor_perl/Gearman/Util.pm line 164.
Use of "goto" to jump into a construct is deprecated at /usr/share/perl5/vendor_perl/Gearman/Util.pm line 164.
#   Failed test 'alternating status'
#   at t/async.t line 75.
#                   '21211221122222'
#     doesn't match '(?^:1212)'
# Looks like you failed 1 test of 2.
t/async.t ......... 
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/2 subtests 

This looks like a race in the test because it expects that tasks complete regularly in time which does not have to be true if CPU scheduler delays some processes.

See Koschei <http://koschei.cloud.fedoraproject.org/package/perl-Gearman-Client-Async> for the failure frequency.

Unfortunately I cannot reproduce the failure.

Comment 1 Jan Kurik 2015-07-15 14:22:18 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:

Comment 2 Fedora End Of Life 2016-11-24 11:36:10 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Petr Pisar 2016-11-24 12:55:46 UTC
I saw last failure on 2016-08-09 in F26. I have no idea if this issue still exhibits.

Comment 4 Fedora End Of Life 2016-12-20 13:23:53 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.

Note You need to log in before you can comment on or make changes to this bug.