[ https://issues.apache.org/jira/browse/QPID-7422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15477064#comment-15477064 ]
ASF subversion and git services commented on QPID-7422: ------------------------------------------------------- Commit 1760016 from oru...@apache.org in branch 'java/trunk' [ https://svn.apache.org/r1760016 ] QPID-7422: Make test timeouts configurable via system properties > [Java Tests] Make test timeouts configurable via system properties > ------------------------------------------------------------------ > > Key: QPID-7422 > URL: https://issues.apache.org/jira/browse/QPID-7422 > Project: Qpid > Issue Type: Bug > Components: Java Tests > Reporter: Alex Rudyy > > A number of tests have failed on slow environments due to time spent on > operations exceeded the expected time hard-coded in the tests. > Here is the list of the tests and their timeouts which have failed recently > doe to bad environment performance: > * BDBHAVirtualHostNodeTest.testCreateAndActivateVirtualHostNode (failed due > to exceeding of waiting interval for node to became Master/Replica) > * DBHAVirtualHostNodeTest.testNodeCannotStartWithIntruder (failed due to > exceeding of waiting interval for node to became Master/Replica) > * SortedQueueTest.testReleaseForQueueWithMultipleConsumers (failed due to > exceeding of AbstractQueueTestBase.queueRunnerWaitTime as it is cannot be > overridden on runtime) > * TimeToLiveTest.testPassiveTTLWithPrefetch, > TimeToLiveTest.testPassiveTTLwithDurableSubscription, > TimeToLiveTest.testPassiveTT (failed due to exceeding of receive interval of > 5000ms) > The timeouts should be overriddable via run-time system properties -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org