[
https://issues.apache.org/jira/browse/ARTEMIS-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039185#comment-18039185
]
Justin Bertram commented on ARTEMIS-3490:
-----------------------------------------
[~robbie], is this still relevant given all the work done on the test-suite
since this was created (e.g. moving to JUnit 5)?
> CI job run timed out after 6hrs due to client being blocked
> -----------------------------------------------------------
>
> Key: ARTEMIS-3490
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3490
> Project: ActiveMQ Artemis
> Issue Type: Test
> Components: Tests
> Affects Versions: 2.18.0
> Reporter: Robbie Gemmell
> Priority: Major
>
> The following CI run eventually timed out after the GHA 6hr limit. It shows
> some exceptions and several hours of log output warning about being blocked.
> The specific test isnt clear but it appears to be in the compatibility test
> module.
> https://github.com/apache/activemq-artemis/runs/3599382982?check_suite_focus=true
> Tests should have timeouts so that no one instance can ever do this, but
> instead fail after a suitably long time.
> If the tests also used a mode specific address/queue names (rather than
> "queue") it might also be more obvious which one it was specifically.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
