You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2023/01/10 20:30:00 UTC

[jira] [Commented] (AMQ-9192) Fix flaky AdvisoryTests causing CI failures

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

ASF subversion and git services commented on AMQ-9192:
------------------------------------------------------

Commit 044f5346e93d9b133fcecccb6000d16967aa0f1e in activemq's branch refs/heads/main from Christopher L. Shannon (cshannon)
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=044f5346e ]

AMQ-9192 - Fix flaky AdvisoryTests

Properly shutdown broker for each test and speed up tests by sending
less messages


> 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)