[ 
https://issues.apache.org/jira/browse/DISPATCH-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894509#comment-13894509
 ] 

Ted Ross commented on DISPATCH-27:
----------------------------------

The platforms this is failing on have older versions of CTest which do not 
support setUpClass and tearDownClass.  The tests therefore revert to using the 
per-test setUp and tearDown.  This means that the pair of routers used in the 
test are started and stopped for each individual test.

The management test is failing in the case where the remote (not directly 
connected) router is being queried by the test client.  I suspect that there is 
a race condition whereby the routing is not ready to forward the message to the 
distant container by the time the test runs.


> Intermittent test failures on RHEL platforms
> --------------------------------------------
>
>                 Key: DISPATCH-27
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-27
>             Project: Qpid Dispatch
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: 0.1
>            Reporter: Ted Ross
>
> =====================================================================
> ERROR: test_09_management (__main__.RouterTest)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File 
> "/home/jenkins/workspace/qpid-dispatch-trunk/label/master/install/lib/qpid-dispatch/tests/system_tests_two_routers.py",
>  line 556, in test_09_management
>     M.recv()
>   File "/usr/lib64/python2.6/site-packages/proton.py", line 534, in recv
>     self._check(pn_messenger_recv(self._mng, n))
>   File "/usr/lib64/python2.6/site-packages/proton.py", line 267, in _check
>     raise exc("[%s]: %s" % (err, 
> pn_error_text(pn_messenger_error(self._mng))))
> Timeout: [-7]: None



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to