So from what I can tell the ttl works fine on the testExpire test case but the call to useAllMemory() doesn't successfully cause the cache to be cleared. I'm guessing it works fine locally because our systems are slower that the test server and the other startup threads running cause the ttl to expire the cache rather than the OOME condition. Haven't yet tested that theory by increasing the ttl on the memory portion of the test.
Questions, if anyone knows: 1. Does the cache actually support expiring entries when the heap space is running out? If not then this test seems a bit strange. 2. If it does support that, where can I find the code to debug it? I'd like to get this fixed or disable the test, the false(?) negatives coming from this isn't doing our CI reporting any good. Thanks Scott HotWax Media http://www.hotwaxmedia.com On 5/06/2011, at 5:31 AM, build...@apache.org wrote: > The Buildbot has detected a new failure on builder ofbiz-trunk while building > ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/ofbiz-trunk/builds/1857 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: isis_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch ofbiz/trunk] 1131416 > Blamelist: mrisaliti > > BUILD FAILED: failed compile_1 > > sincerely, > -The Buildbot >
smime.p7s
Description: S/MIME cryptographic signature