Bug 833315 - "Failed to find expected message" error.
"Failed to find expected message" error.
Status: NEW
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp (Show other bugs)
2.1.2
s390x Unspecified
medium Severity medium
: ---
: ---
Assigned To: Ken Giusti
MRG Quality Engineering
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-06-19 04:33 EDT by Leonid Zhaldybin
Modified: 2015-11-15 20:18 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Leonid Zhaldybin 2012-06-19 04:33:54 EDT
Description of problem:
The test federation.FederationTests.test_pull_from_queue_recovery (from source rpm qpid-cpp-0.14-16.el6.src.rpm) fails somtimes with error message "Failed to find expected message containing 'Message 6'". During my testing it was failing at least once out of five testruns.

Version-Release number of selected component (if applicable):
python-qpid-0.14-8.el6.noarch
python-qpid-qmf-0.14-7.el6_2.s390x
qpid-cpp-client-0.14-16.el6.s390x
qpid-cpp-client-devel-0.14-16.el6.s390x
qpid-cpp-client-ssl-0.14-16.el6.s390x
qpid-cpp-debuginfo-0.14-16.el6.s390x
qpid-cpp-server-0.14-16.el6.s390x
qpid-cpp-server-devel-0.14-16.el6.s390x
qpid-cpp-server-ssl-0.14-16.el6.s390x
qpid-cpp-server-store-0.14-16.el6.s390x
qpid-java-client-0.14-3.el6.noarch
qpid-java-common-0.14-3.el6.noarch
qpid-java-example-0.14-3.el6.noarch
qpid-qmf-0.14-7.el6_2.s390x
qpid-qmf-debuginfo-0.14-7.el6_2.s390x
qpid-qmf-devel-0.14-7.el6_2.s390x
qpid-tests-0.14-1.el6_2.noarch
qpid-tools-0.14-2.el6_2.noarch

How reproducible:
about 20%

Steps to Reproduce:
1. Run unit test federation.FederationTests.test_pull_from_queue_recovery
2.
3.
  
Actual results:
The test sometimes fails.

Expected results:
The test always passes.

Additional info:

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