[
https://issues.apache.org/jira/browse/ARTEMIS-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Daněk reopened ARTEMIS-2016:
---------------------------------
The
{{org.apache.activemq.artemis.tests.integration.management.QueueControlTest#assertMetrics}}
has been fixed.
The zero timeout in
{{org.apache.activemq.artemis.tests.integration.clientcrash.ClientTestBase#assertActiveConnections(int)}}
and
{{org.apache.activemq.artemis.tests.integration.clientcrash.ClientTestBase#assertActiveSession(int)}}
was not yet fixed.
> Wait.waitFor is sometimes called with zero timeout (durationMillis), or with
> durationMillis < sleepMillis
> ---------------------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-2016
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2016
> Project: ActiveMQ Artemis
> Issue Type: Test
> Affects Versions: 2.7.0
> Reporter: Jiri Daněk
> Priority: Major
> Fix For: 2.6.3
>
>
> {{timeout = 0}} happens in
> {{org.apache.activemq.artemis.tests.integration.clientcrash.ClientTestBase#assertActiveConnections(int)}}
> and
> {{org.apache.activemq.artemis.tests.integration.clientcrash.ClientTestBase#assertActiveSession(int)}}.
> {{durationMillis < sleepMillis}} happens in
> {{org.apache.activemq.artemis.tests.integration.management.QueueControlTest#assertMetrics}}
> I am not sure what the intent of the author of the test was, but the current
> state seems wrong. The test {{QueueControlTest#testRemoveAllWithPagingMode}}
> is flaky due to insufficient number of retry attempts in
> {{QueueControlTest#assertMetrics}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
