[
https://issues.apache.org/jira/browse/PROTON-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821447#comment-16821447
]
Chuck Rolke commented on PROTON-2033:
-------------------------------------
It looks like the python receive client starts getting confused during shutdown
in the face of incoming traffic. After further instrumenting the test a run
will fail:
{code:java}
50: ??? Receiver on_settled. remote: 0, local: RELEASED
50: Bad sender settlement: 0, n_accepted: 300, n_rel_or_mod: 0
50: MobileAddressTest fail: Timeout Expired
50: address test_12_19
50: n_sent = 350. Expected total:350 normal=300, extra=50
50: n_rcvd = 300. Expected 300
50: n_accepted = 300. Expected 300
50: n_rel_or_mod = 49. Expected 50
{code}
* The receiver should not receive settlements. A single receive settlement was
processed.
* The sender settlement of 0 arises at the test expects all settlements to be
sender settlements and this one was not.
* The test failed because the sender is missing one settlement.
The test code is available in branch DISPATCH-1318-2, repo
[https://github.com/ChugR/qpid-dispatch.git]
The test fails with command *ctest -VV -R edge*
> qpid-proton changes 0.27.x to master(9ff0a) break qpid-dispatch self test
> -------------------------------------------------------------------------
>
> Key: PROTON-2033
> URL: https://issues.apache.org/jira/browse/PROTON-2033
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c, python-binding
> Affects Versions: proton-c-0.28.0
> Environment: Fedora 29, python 3.7, proton and dispatch debug builds
> Reporter: Chuck Rolke
> Priority: Major
>
> While cleaning up qpid-dispatch for a 1.6 follow-on release an intermittent
> failure in one of the tests was exposed. Analysis of the failure is in
> https://issues.apache.org/jira/browse/DISPATCH-1322 in an attached text
> document
> https://issues.apache.org/jira/secure/attachment/12965891/DISPATCH-1322-analysis.txt
> Another part of the cleanup was fixing the failing test to better report what
> went wrong. See https://issues.apache.org/jira/browse/DISPATCH-1318
> These issues happened using qpid-proton master @9ff0a. Temporarily the
> qpid-proton version was reverted to branch 0.27.x @560ba. Using proton 0.27.x
> branch the qpid-dispatch self test does not fail. It passed several thousand
> times in a loop. Moving proton back to the master branch brought the dispatch
> failures back.
> From the qpid-dispatch perspective this issue is serious. If a receiver
> detaches a link while a sender is sending to it then the sender may lose a
> disposition.
> No attempt yet has been made to bisect proton to see where the different
> behavior starts showing up. That may be the next best avenue of research.
> Another theory for the error is that qpid-dispatch has been mishandling links
> all along.
> To help expose the problem one may clone
> [https://github.com/ChugR/qpid-dispatch] , or add it as a remote, and then
> check out branch DISPATCH-1318-cwip. Test system_tests_edge_router has been
> gutted to run only test_12 in a loop and to print details of the error(s).
> {{ cd build}}
> {{ make}}
> {{ ctest -VV -R edge}}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
