[ARTEMIS-3458] CuratorDistributedLockTest fails a lot in CI

• Type: Test
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.18.0
• Fix Version/s: 2.19.0
• Component/s: Tests
• Assignee: Francesco Nigro
• Reporter: Robbie Gemmell
• Created: 03/Sep/21 14:31
• Updated: 12/Oct/21 00:50
• Resolved: 12/Oct/21 00:50

Description

CuratorDistributedLockTest was added in ARTEMIS-2716 / PR #3680. In addition to creating a lot of log output which made the Travis build error and required some changes, it fails a lot in CI.

E.g perhaps most often with:

org.apache.curator.test.FailedServerStartException: quorumPeer never got set
 at org.apache.activemq.artemis.quorum.zookeeper.CuratorDistributedLockTest.setupEnv(CuratorDistributedLockTest.java:84)

https://github.com/apache/activemq-artemis/runs/3496677873?check_suite_focus=true#step:5:58742

 

Or I also saw:

 java.lang.AssertionError: expected:<1> but was:<0>
 at org.apache.activemq.artemis.quorum.zookeeper.CuratorDistributedLockTest.beNotifiedOfUnavailabilityWhileBlockedOnTimedLock(CuratorDistributedLockTest.java:309)

https://github.com/apache/activemq-artemis/runs/3495287001?check_suite_focus=true#step:5:56488

 

Finally, today I saw it fail a completely new way, taking down the test JVM:

[QuorumPeerListener] 09:43:44,204 ERROR [org.apache.zookeeper.util.ServiceUtils] Exiting JVM with code 14

https://github.com/apache/activemq-artemis/runs/3504709670?check_suite_focus=true#step:5:35957