This is really weird... I am wondering if there are issues caused by concurrent threads accessing the cache but the JUnit tests should be all executed in the same thread... so this should not be the case.
Jacopo On Apr 23, 2012, at 3:47 PM, Adrian Crum wrote: > The tests failed intermittently in the OFBiz buildbot (back when it was > running). They always fail on my development machine. > > I tried experimenting with the sleep timing and I also replaced the > Thread.sleep call with a safer version, but the tests still failed. > > -Adrian > > On 4/23/2012 2:40 PM, Jacopo Cappellato wrote: >> Adrian, >> >> the issue you are experiencing is interesting and I had a look at it; I was >> only able to recreate the same failures by changing the timeouts in >> UtilCacheTests.java at line 302 and 308; instead of: >> >> cache.setExpireTime(100); // line 302 >> Thread.sleep(200); // line 308 >> >> I set: >> >> cache.setExpireTime(100); // line 302 >> Thread.sleep(99); // line 308 >> >> and (of course) I got the error. >> It is kind of weird that you are getting the error with the current settings >> (100 and 200): is this consistent? I mean, are you able to recreate the >> issue frequently? did you try to increase the time for sleep: >> >> Thread.sleep(300); // line 308 >> >> ? >> >> Regards, >> >> Jacopo >> >> >> On Apr 22, 2012, at 10:53 AM, Adrian Crum wrote: >> >>> On 4/20/2012 9:00 PM, Adam Heath wrote: >>>> On 04/20/2012 12:13 PM, Jacques Le Roux wrote: >>>>> Not sure you noticed but Builbot is no longer running >>>>> http://ci.apache.org/waterfall?show_events=false&branch=&builder=ofbiz-trunk&reload=none >>>> Yeah, noticed that buildbot wasn't emailing. Looking at that link, it >>>> appears that isis_ubuntu is offline. >>>> >>>> I always run all my changes thru a full clean/test run before >>>> committing(even when I commit> 10 at a time). >>> Adam, >>> >>> If it's not too much trouble, could you look at >>> >>> https://issues.apache.org/jira/browse/OFBIZ-4239 ? >>> >>> Buildbot was failing the framework/base tests intermittently. I think I >>> tracked the problem down to a timing issue in the UtilCache tests - see the >>> attached test report and my comments for details. >>> >>> -Adrian >>>
