qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (PROTON-1298) [proton-c] SyncRequestResponseTest.test_allowed_mechs_external is very slow
Date Tue, 03 Oct 2017 09:29:00 GMT

     [ https://issues.apache.org/jira/browse/PROTON-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robbie Gemmell closed PROTON-1298.
----------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: proton-c-0.18.0)

No there was nothing particularly interesting about the systems.

Something has changed since, as I can still reproduce this (using a different system than
before) using 0.14.0 as reported against, but it isn't showing this on master for me, nor
is it showing in Travis CI any more.

Either the test code or the proton behaviour causing it has has changed in a way that resolved
this at some point so I'll just close this out (without a fix-version as its not important
enough to track down).

> [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
>
> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message