[jira] [Created] (ARTEMIS-4509) ActiveMQTestBase leak check should identify state clearly without need of logs

["Robbie Gemmell (Jira)" <ji...@apache.org>]

Robbie Gemmell created ARTEMIS-4509:
---------------------------------------

             Summary: ActiveMQTestBase leak check should identify state clearly without need of logs
                 Key: ARTEMIS-4509
                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4509
             Project: ActiveMQ Artemis
          Issue Type: Task
    Affects Versions: 2.31.2
            Reporter: Robbie Gemmell
            Assignee: Robbie Gemmell
             Fix For: 2.32.0


The ActiveMQTestBase class does some leak checking on the LibaioContext resource usage during the test suite. There is a pre-class check that logs when it first detects a leak happened before the (typically in a non-ActiveMQTestBase test class), or fails immediately if a previous class has detected the leak and failed (after), and a post-class check that fails if things dont hit 0-usage within 30 seconds.

This is fine for local usage but is a bit of a pain for cases where the pre-class foul happens in a CI env, as it isnt always so easy to find, get, and examine the full specific class logs to determine the precise status of when the issue occurred. It would be more useful if the pre-class foul detection actually just failed immediately (as will already happen after) and created an error that explicitly identifies the status from the test fail without needing to examine the logs at all.



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