You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Robbie Gemmell (Jira)" <ji...@apache.org> on 2021/09/17 14:27:00 UTC

[jira] [Created] (ARTEMIS-3490) CI job run timed out after 6hrs due to client being blocked

Robbie Gemmell created ARTEMIS-3490:
---------------------------------------

             Summary: 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


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.3.4#803005)