Same error on Ubuntu 12.04 and the following Java version: java version "1.7.0_25" OpenJDK Runtime Environment (IcedTea 2.3.10) (7u25-2.3.10-1ubuntu0.12.04.2) OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
I'm trying what suggested by Martijn. > Running with T < 21s causes consistent failures in the test (fails on > first test run). Running with T=21 makes the test succeed consistently > (i.e. 4 times in a row successful). So it appears to be a starvation > issue. > > Martijn > > On Mon, Dec 9, 2013 at 9:07 AM, Emond Papegaaij > <[email protected]> wrote: >> This testcase only failed (prior to fixing the bug) when a large number of >> threads was used to acquire and release locks. Do you hit a deadlock or is >> it starvation? Perhaps we need to increase the timeout. If you do hit a >> deadlock, it should not matter what the timeout is. We can even give it 1 >> hour if needed. >> >> Emond >> >> On Sunday 08 December 2013 20:14:59 Martijn Dashorst wrote: >>> The PageAccessSynchronizerTest#ReleaseUnderLoad() test fails when >> run >>> on OS X Mavericks on a Hasswell generation core i7 using OS X supplied >>> Java 6: >>> >>> java version "1.6.0_65" >>> Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609) >>> Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode) >>> >>> Unfortunately this breaks the release process considerably. Some >>> testing showed that for N=20 (I guess the number of threads is the >>> number of concurrent simulated requests) makes the tests run >> smoothly. >>> N=25 intermittently fails the test with 1-2 errors, N=100 shows 5, 56 >>> or more errors. >>> >>> Is testing with N=100 necessary or are we then just testing the >>> locking/unlocking speed of the JVM? >>> >>> (also trying to comment on issue >>> https://issues.apache.org/jira/browse/WICKET-5316) >>> >>> Martijn >>> >>> >>> On Sun, Dec 8, 2013 at 6:29 PM, Martijn Dashorst >>> >>> <[email protected]> wrote: >>>> Of course it works running java 7, but I'd rather not use that to cut >>>> our release. >>>> >>>> Martijn >>>> >>>> On Sun, Dec 8, 2013 at 6:25 PM, Martijn Dashorst >>>> >>>> <[email protected]> wrote: >>>>> I'm unable to run the maven release process to its conclusion due to >> a >>>>> failing test: >>>>> >>>>> Tests in error: >>>>> >> failToReleaseUnderLoad(org.apache.wicket.page.PageAccessSynchronizerT >> est): >>>>> Could not lock page 0. Attempt lasted 10 seconds >>>>> >>>>> >>>>> Relevant information for the stuff used in the release: >>>>> >>>>> $ mvn --version >>>>> Apache Maven 3.1.1 >> (0728685237757ffbf44136acec0402957f723d9a; >>>>> 2013-09-17 17:22:22+0200) >>>>> Maven home: /usr/local/Cellar/maven/3.1.1/libexec >>>>> Java version: 1.6.0_65, vendor: Apple Inc. >>>>> Java home: >>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home >>>>> Default locale: en_US, platform encoding: MacRoman >>>>> OS name: "mac os x", version: "10.9", arch: "x86_64", family: "mac" >>>> -- >>>> Become a Wicket expert, learn from the best: >> http://wicketinaction.com >> > >
