Bug 1136723

Summary: perl-Workflow-1.41-2.fc22 FTBFS randomly: 'One observation sent on workflow fetch to two observers' t/workflow.t test fails
Product: [Fedora] Fedora Reporter: Petr Pisar <ppisar>
Component: perl-WorkflowAssignee: Emmanuel Seyman <emmanuel>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: emmanuel, mmaslano, perl-devel
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-20 09:41:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Petr Pisar 2014-09-03 07:20:47 UTC 
perl-Workflow-1.41-2.fc22 fails to build randomly in F22. 'One observation sent on workflow fetch to two observers' t/workflow.t test sometimes fails:

t/validator_matches_date_format.t .. ok
#   Failed test 'One observation sent on workflow fetch to two observers'
#   at t/workflow.t line 80.
#          got: '4'
#     expected: '2'
# Looks like you failed 1 test of 37.
t/workflow.t .......................
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/37 subtests

First, I thought this was caused by upgrading perl-DateTime (from 1.10) and perl-DateTime-TimeZone. But the random failure occurs even with these old versions. So I conclude this is race in the test or in some of used modules.

It's reproducible with command:

Workflow-1.41$ (prove -b -v t/workflow.t); do :;done
Comment 1 Petr Pisar 2014-09-03 07:21:32 UTC 
Correct command:

Workflow-1.41$ while (prove -b -v t/workflow.t); do :; done
Comment 2 Emmanuel Seyman 2014-11-20 09:41:37 UTC 
Given that this issue is an upstream bug more than it is a packaging issue, I'll be keeping track of it in CPAN's RT. Accordingly, I'm closing this bug with the resolution of UPSTREAM.