[
https://issues.apache.org/jira/browse/ARTEMIS-4250?focusedWorklogId=858733&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-858733
]
ASF GitHub Bot logged work on ARTEMIS-4250:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 24/Apr/23 15:06
Start Date: 24/Apr/23 15:06
Worklog Time Spent: 10m
Work Description: clebertsuconic merged PR #4446:
URL: https://github.com/apache/activemq-artemis/pull/4446
Issue Time Tracking
-------------------
Worklog Id: (was: 858733)
Time Spent: 20m (was: 10m)
> ShutdownOnCriticalIOErrorMoveNextTest failing
> ---------------------------------------------
>
> Key: ARTEMIS-4250
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4250
> Project: ActiveMQ Artemis
> Issue Type: Test
> Affects Versions: 2.28.0
> Reporter: Clebert Suconic
> Priority: Major
> Fix For: 2.29.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> ShutdownOnCriticalIOErrorMoveNextTest will simulate an IO failure, and some
> of the Executors are not being cleaned.
> This is an odd situation that would happen when the VM was coming down
> anyway. So the test should really use a spawned VM.
> The test is leaking threads, and spawning a VM would avoid these issues.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
