There's something fishy about the following test - it likes to fail when CPU is on full or computer is stalling.


Run test org.exoplatform.services.cache.impl.jboss.TestAbstractExoCache

********************************************************
                   BEGIN TEST CASE
                testMultiThreading
********************************************************

Tests run: 11, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 18.631 sec <<< FAILURE!
Running org.exoplatform.services.cache.impl.jboss.TestExoCacheCreator
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.023 sec
Running org.exoplatform.services.cache.impl.jboss.TestExoCacheConfig
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.617 sec
Running org.exoplatform.services.cache.impl.jboss.TestLRUCache
log4j:WARN No appenders could be found for logger (org.exoplatform.container.RootContainer).
log4j:WARN Please initialize the log4j system properly.
Run test org.exoplatform.services.cache.impl.jboss.TestLRUCache


Surefire report:

-------------------------------------------------------------------------------
Test set: org.exoplatform.services.cache.impl.jboss.TestAbstractExoCache
-------------------------------------------------------------------------------
Tests run: 11, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 18.626 sec <<< FAILURE!
testMultiThreading(org.exoplatform.services.cache.impl.jboss.TestAbstractExoCache)  Time elapsed: 11.333 sec  <<< FAILURE!
junit.framework.AssertionFailedError: expected:<100> but was:<74>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:280)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:198)
at junit.framework.Assert.assertEquals(Assert.java:204)
at org.exoplatform.services.cache.impl.jboss.TestAbstractExoCache.testMultiThreading(TestAbstractExoCache.java:518)



Cheers,

- marko