https://logs.opendaylight.org/releng/jenkins092/netvirt-verify-oxygen-mvn33-openjdk8/2245/vpnservice/aclservice/impl/target/surefire-reports/org.opendaylight.netvirt.aclservice.tests.AclServiceStatefulTest-output.txt.gz for https://jenkins.opendaylight.org/releng/job/netvirt-verify-oxygen-mvn33-openjdk8/2245/console for https://git.opendaylight.org/gerrit/#/c/64381/ illustrates a case of AclServiceStatefulTest failing on Jenkins (only), but passing locally, due to some what I suspect to be a timing issue / concurrency bug in JobCoordinator...

... basically, this kind of component test failure:

newInterfaceWithMultipleAcl(org.opendaylight.netvirt.aclservice.tests.AclServiceStatefulTest)  Time elapsed: 30.396 sec  <<< ERROR!
 org.awaitility.core.ConditionTimeoutException: Condition with alias 'TestableJobCoordinatorEventsWaiter' didn't complete within 30 seconds
 because lambda expression in org.opendaylight.genius.datastoreutils.testutils.TestableJobCoordinatorEventsWaiter: expected <0L> but was <3>.

is "just" telling us that the JobCoordinator still has 3 pending jobs that still did not execute, even after the test was waiting for it for 30 seconds. It's possible that Jenkins is slower than local builds, but 30s seems an awfully sufficiently long time for some thread to do do work.. more likely, somehow it got stuck?