[DISPATCH-2213] Fallback test prints too much logging when addresses never stabilize

• Type: Test
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.16.1
• Fix Version/s: 1.17.0
• Component/s: Tests
• Assignee: Charles E. Rolke
• Reporter: Charles E. Rolke
• Created: 26/Jul/21 14:56
• Updated: 23/Aug/21 15:02
• Resolved: 27/Jul/21 18:30

Description

Travis-ci jobs get wedged when primary receiver never start receiving test Phase 0 messages.

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

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.