Charles E. Rolke created DISPATCH-1772:
------------------------------------------

             Summary: Fallback destination test prints insufficient data when 
it fails
                 Key: DISPATCH-1772
                 URL: https://issues.apache.org/jira/browse/DISPATCH-1772
             Project: Qpid Dispatch
          Issue Type: Bug
          Components: Tests
    Affects Versions: 1.13.0
            Reporter: Charles E. Rolke
            Assignee: Charles E. Rolke


Occasionally the Switchover_mix test fails in CI. When this happens then the 
self test prints only a single line describing the failure such as:

{code:java}
        "63: 
======================================================================", 
        "63: FAIL: test_35_switchover_mix_1 
(system_tests_fallback_dest.RouterTest)", 
        "63: 
----------------------------------------------------------------------", 
        "63: Traceback (most recent call last):", 
        "63:   File 
\"/opt/qpid-dispatch-src/tests/system_tests_fallback_dest.py\", line 353, in 
test_35_switchover_mix_1", 
        "63:     self.assertEqual(None, test.error)", 
        "63: AssertionError: None != u'Timeout Expired - n_tx=0, n_rx=0, 
n_rel=1046, phase=1, local_rel=0'", 
        "63: ", 
        "63: 
----------------------------------------------------------------------", 
{code}

This error message says that (phase=1) all the messages were sent successfully 
before the switchover was initiated. Then 1046 messages were released by the 
locally connected router until the test timed out.

Class system_test/Logger could be used to generate a much more detailed 
narrative describing how the client test event stream played out. Further, the 
Logger log marks the client events with microsecond resolution so that when 
possible the log can be correlated with qdrouterd logs.



--
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