[
https://issues.apache.org/jira/browse/BOOKKEEPER-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15230819#comment-15230819
]
ASF GitHub Bot commented on BOOKKEEPER-914:
-------------------------------------------
GitHub user dlg99 opened a pull request:
https://github.com/apache/bookkeeper/pull/32
BOOKKEEPER-914 testBookieShouldTurnWritableFromReadOnly flapping
BOOKKEEPER-914 fixed testBookieShouldTurnWritableFromReadOnly flapping.
Now test waits for bookie to transition to read-only.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dlg99/bookkeeper bugfix/BOOKKEEPER-914
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/bookkeeper/pull/32.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #32
----
commit 7ea874051ac7ff81883a9b33f74e71f22ad78e82
Author: Andrey Yegorov <[email protected]>
Date: 2016-04-07T18:52:44Z
BOOKKEEPER-914 fixed testBookieShouldTurnWritableFromReadOnly flapping. Now
test waits for bookie to transition to read-only.
----
> 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
> Assignee: Andrey Yegorov
> 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)
