You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Arun M. Krishnakumar (JIRA)" <ji...@apache.org> on 2016/04/07 05:46:25 UTC
[jira] [Commented] (BOOKKEEPER-914)
ReadOnlyBookieTest.testBookieShouldTurnWritableFromReadOnly is
intermettently failing
[ https://issues.apache.org/jira/browse/BOOKKEEPER-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229620#comment-15229620 ]
Arun M. Krishnakumar commented on BOOKKEEPER-914:
-------------------------------------------------
[~mmerli] I believe [~ayegorov] has a fix for this. Could you please add him as a contributor so that it can be assigned to him ?
> ReadOnlyBookieTest.testBookieShouldTurnWritableFromReadOnly is intermettently failing
> -------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-914
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-914
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Matteo Merli
> Priority: Minor
> Fix For: 4.4.0
>
>
> I've seen it failing a few times and it seems different that BOOKKEEPER-774.
> https://builds.apache.org/job/bookkeeper-master-git-pullrequest/57/testReport/junit/org.apache.bookkeeper.test/ReadOnlyBookieTest/testBookieShouldTurnWritableFromReadOnly/
> {noformat}
> Error Message
> Should fail to create a ledger since there isn't enough bookies alive.
> Stacktrace
> java.lang.AssertionError: Should fail to create a ledger since there isn't enough bookies alive.
> at org.junit.Assert.fail(Assert.java:88)
> at org.apache.bookkeeper.test.ReadOnlyBookieTest.testBookieShouldTurnWritableFromReadOnly(ReadOnlyBookieTest.java:137)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
> at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)