You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2011/08/12 13:43:09 UTC

Jenkins build became unstable: Jackrabbit-trunk » Jackrabbit Core #1611

See <https://builds.apache.org/job/Jackrabbit-trunk/org.apache.jackrabbit$jackrabbit-core/1611/>

Jenkins build is back to stable : Jackrabbit-trunk » Jackrabbit Core #1612

Posted by Apache Jenkins Server <je...@builds.apache.org>.

See <https://builds.apache.org/job/Jackrabbit-trunk/org.apache.jackrabbit$jackrabbit-core/1612/>

Re: Jenkins build became unstable: Jackrabbit-trunk » Jackrabbit Core #1611

Posted by Michael Dürig <mi...@gmail.com>.

> On Fri, Aug 12, 2011 at 1:46 PM, Michael Dürig<mi...@gmail.com>  wrote:
>> This seems to be happening from time to time and seems to be a timing issue.
>> Giving the lock a bit more time to time out fixed it on my machine. Should
>> we change the test case accordingly?
>
> I guess we should do that. The downside is some extra delay to the
> test suite, but a few seconds shouldn't be too much of a problem.

Created https://issues.apache.org/jira/browse/JCR-3051

Michael

Re: Jenkins build became unstable: Jackrabbit-trunk » Jackrabbit Core #1611

Posted by Jukka Zitting <ju...@gmail.com>.

Hi,

On Fri, Aug 12, 2011 at 1:46 PM, Michael Dürig <mi...@gmail.com> wrote:
> This seems to be happening from time to time and seems to be a timing issue.
> Giving the lock a bit more time to time out fixed it on my machine. Should
> we change the test case accordingly?

I guess we should do that. The downside is some extra delay to the
test suite, but a few seconds shouldn't be too much of a problem.

BR,

Jukka Zitting

Re: Jenkins build became unstable: Jackrabbit-trunk » Jackrabbit Core #1611

Posted by Michael Dürig <mi...@gmail.com>.

This seems to be happening from time to time and seems to be a timing 
issue. Giving the lock a bit more time to time out fixed it on my 
machine. Should we change the test case accordingly?

Michael

junit.framework.AssertionFailedError: A released lock must return a 
negative number of seconds, was: 1
	at junit.framework.Assert.fail(Assert.java:47)
	at junit.framework.Assert.assertTrue(Assert.java:20)
	at 
org.apache.jackrabbit.test.api.lock.AbstractLockTest.testLockExpiration(AbstractLockTest.java:277)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:592)
	at junit.framework.TestCase.runTest(TestCase.java:154)
	at junit.framework.TestCase.runBare(TestCase.java:127)
	at junit.framework.TestResult$1.protect(TestResult.java:106)
	at junit.framework.TestResult.runProtected(TestResult.java:124)
	at junit.framework.TestResult.run(TestResult.java:109)
	at junit.framework.TestCase.run(TestCase.java:118)
	at org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:456)
	at junit.framework.TestSuite.runTest(TestSuite.java:208)
	at junit.framework.TestSuite.run(TestSuite.java:203)
	at junit.framework.TestSuite.runTest(TestSuite.java:208)
	at junit.framework.TestSuite.run(TestSuite.java:203)
	at junit.framework.TestSuite.runTest(TestSuite.java:208)
	at 
org.apache.jackrabbit.test.ConcurrentTestSuite.access$001(ConcurrentTestSuite.java:29)
	at 
org.apache.jackrabbit.test.ConcurrentTestSuite$2.run(ConcurrentTestSuite.java:67)
	at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown 
Source)
	at java.lang.Thread.run(Thread.java:595)


On 12.8.11 12:43, Apache Jenkins Server wrote:
> See<https://builds.apache.org/job/Jackrabbit-trunk/org.apache.jackrabbit$jackrabbit-core/1611/>
>
>