[
https://issues.apache.org/jira/browse/PROTON-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16189283#comment-16189283
]
Andrew Stitcher commented on PROTON-1298:
-----------------------------------------
[~gemmellr] Are there any special or moticable things about the systems
experiencing this? I can't seem to reproduce on my fedora 25 laptop.
I notice that one thing this test does is to try to open a random listening
port, and that may take some time if thjere are very few ports available.
However many of the tests in the same test section do the same (in fact many
tests overall do it). So it can't easily explain the very specific slow down.
The other thing it does that is not specific to this test is wait for an echo
server to finish, so if this takes a long while just for this test for some
reason this could explain the slowdown.
> [proton-c] SyncRequestResponseTest.test_allowed_mechs_external is very slow
> ---------------------------------------------------------------------------
>
> Key: PROTON-1298
> URL: https://issues.apache.org/jira/browse/PROTON-1298
> Project: Qpid Proton
> Issue Type: Test
> Components: proton-c
> Affects Versions: 0.14.0
> Reporter: Robbie Gemmell
> Assignee: Andrew Stitcher
> Fix For: proton-c-0.18.0
>
>
> SyncRequestResponseTest.test_allowed_mechs_external is very slow, the tests
> seem to sit waiting for it to complete for a long time, to the extent it
> dominates the overall test run time.
> {noformat}
> 2: proton_tests.utils.SyncRequestResponseTest.test_allowed_mechs_external ..
> start
> 2: 2016-09-08 10:40:22,513 ERROR amqp:connection:framing-error: connection
> aborted
> 2: proton_tests.utils.SyncRequestResponseTest.test_allowed_mechs_external ..
> pass
> 2: proton_tests.utils.SyncRequestResponseTest.test_connection_properties ...
> pass
> 2: proton_tests.utils.SyncRequestResponseTest.test_request_response ........
> pass
> 2: Totals: 422 tests, 407 passed, 15 skipped, 0 ignored, 0 failed
> 2/20 Test #2: python-test ...................... Passed 102.36 sec
> {noformat}
> The proton-j run of the python tests skips that particular test, and takes 30
> seconds in total on the same system.
> The same delay appears to be present on Travis CI as well, with a run of
> similar commit taking 128ec on the proton-c python tests, so it doesnt seem
> to be environment specific.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
