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

Jiri Daněk commented on DISPATCH-2072:
--------------------------------------

Here it is on s390x, 
https://app.travis-ci.com/github/apache/qpid-dispatch/jobs/527168928#L3907

> [macOS] test_same_name_route_receivers_through_C timeout in 
> system_tests_link_routes
> ------------------------------------------------------------------------------------
>
>                 Key: DISPATCH-2072
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-2072
>             Project: Qpid Dispatch
>          Issue Type: Test
>    Affects Versions: 1.16.0
>            Reporter: Jiri Daněk
>            Priority: Minor
>             Fix For: Backlog
>
>
> {noformat}
> 14: ======================================================================
> 14: FAIL:  (system_tests_link_routes.LinkRouteTest)
> 14: ----------------------------------------------------------------------
> 14: Traceback (most recent call last):
> 14:   File 
> "/Users/travis/build/apache/qpid-dispatch/tests/system_tests_link_routes.py", 
> line 750, in test_same_name_route_receivers_through_C
> 14:     self._multi_link_send_receive(self.routers[0].addresses[0], 
> self.routers[2].addresses[0], "recv_through_C")
> 14:   File 
> "/Users/travis/build/apache/qpid-dispatch/tests/system_tests_link_routes.py", 
> line 741, in _multi_link_send_receive
> 14:     self.assertEqual(None, test.error)
> 14: AssertionError: None != 'Timeout Expired'
> 14: 
> 14: ----------------------------------------------------------------------
> 14: Ran 40 tests in 134.529s
> 14: 
> 14: FAILED (failures=1)
> 14/69 Test #14: system_tests_link_routes ..........................***Failed  
> 134.79 sec
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to