The test SearchBeforeIndexSynchronizationJmsMasterSlaveIT
occasionally fails.
The test verifies that - having a a very long refresh period - a change performed on a JMS slave is not visible right after being performed.

Still this occasionally fails as both Master and Slave nodes perform a background synchronization of indexes at initialization time as well. I'm going to remove this test as it's slow and the important test anyway is SearchNewEntityJmsMasterSlaveIT: this one verifies proper functionality of the Master/Slave setup on AS7.