tree bb01e4cb29266c9a025d7dc1d40e2d8dc97ad596
parent 6f35f5b537bad5e7ad5d75eb58c203d18998de45
author Saša Živkov <sasa.zivkov@sap.com> 1697118317 +0200
committer Saša Živkov <sasa.zivkov@sap.com> 1697123014 +0200

IndexEventHandlerTest: fix flakiness in concurrent indexing tests

The usage of CyclicBarrier to synchronize two concurrent tasks was not
coded correctly. The assumption that when both concurrent tasks pass the
`await()` point, which occurred before attempting to acquire a lock,
ensures concurrency was wrong: it can happen that one task acquires a
lock and releases it before the other task even tries to acquire the
lock. In the end both tasks succeed in acquiring the lock.

To fix the flakiness, the `await()` on the CyclicBarrier has to be
called after a lock was successfully acquired but before it is released
and also when failing to acquire the lock. This way the two `await()`
calls from two concurrent tasks ensure real concurrency.

Change-Id: I4dd4faec5e94eecdefed4729e241ef174428bba1