Marked @RF but in fact seems to always fail for me:
junit.framework.AssertionFailedError: expected:<0> but was:<2>
Well, we have traded speed for accuracy, see issue #166408. So I guess this test is obsolete.
Then either delete it, or fix it to e.g. wait for EQ to be done processing outstanding events before continuing with the test.