[
https://issues.apache.org/jira/browse/DISPATCH-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17388243#comment-17388243
]
ASF GitHub Bot commented on DISPATCH-2213:
------------------------------------------
asfgit closed pull request #1323:
URL: https://github.com/apache/qpid-dispatch/pull/1323
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
> Fallback test prints too much logging when addresses never stabilize
> --------------------------------------------------------------------
>
> Key: DISPATCH-2213
> URL: https://issues.apache.org/jira/browse/DISPATCH-2213
> Project: Qpid Dispatch
> Issue Type: Test
> Components: Tests
> Affects Versions: 1.16.1
> Reporter: Charles E. Rolke
> Assignee: Charles E. Rolke
> Priority: Major
>
> Travis-ci jobs get wedged when primary receiver never start receiving test
> Phase 0 messages.
> {code:java}
> 63: 2021-07-23 12:53:08.671191 FALLBACK_TEST dest.32 Released phase 0 over
> fallback: msg:'Msg dest.32 22602 232', n_rx=0, n_tx=233, n_rel=22603,
> local_rel=22603
> {code}
> This test has sent 22603 messages destined for the primary receiver but
> received them all over the fallback receiver. When the primary receiver
> attaches then the messages are supposed to be directed to it.
> Meanwhile the test generates so much log output that it consumes the CI
> overall quota and other tests never get to run at all.
> This jira does not attempt to fix the underlying issue of the why the primary
> receiver never connects but simply tries to back off the logging.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
