[ 
https://issues.apache.org/jira/browse/AMQ-9192?focusedWorklogId=838438&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-838438
 ]

ASF GitHub Bot logged work on AMQ-9192:
---------------------------------------

                Author: ASF GitHub Bot
            Created on: 10/Jan/23 20:29
            Start Date: 10/Jan/23 20:29
    Worklog Time Spent: 10m 
      Work Description: cshannon merged PR #951:
URL: https://github.com/apache/activemq/pull/951




Issue Time Tracking
-------------------

    Worklog Id:     (was: 838438)
    Time Spent: 40m  (was: 0.5h)

> Fix flaky AdvisoryTests causing CI failures
> -------------------------------------------
>
>                 Key: AMQ-9192
>                 URL: https://issues.apache.org/jira/browse/AMQ-9192
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.17.3
>            Reporter: Christopher L. Shannon
>            Assignee: Christopher L. Shannon
>            Priority: Major
>             Fix For: 5.18.0, 5.17.4
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> I noticed in Jenkins that the advisory tests are flaky for two reasons. One 
> is on stop the connection.stop() call can cause an error and prevent the 
> broker from being stopped which leads to future tests failing due to the 
> broker instance still running in memory. The other issue is some of the tests 
> are sending way too many messages (way more than needed) and is causing slow 
> tests and timeouts.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to