[
https://issues.apache.org/jira/browse/BOOKKEEPER-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504565#comment-13504565
]
Hadoop QA commented on BOOKKEEPER-347:
--------------------------------------
Testing JIRA BOOKKEEPER-347
WARNING: Running test-patch on a dirty local svn workspace
Patch <a
href="/jira/secure/attachment/12553635/BOOKKEEPER-347.patch">/jira/secure/attachment/12553635/BOOKKEEPER-347.patch</a>
downloaded at Tue Nov 27 11:53:06 UTC 2012
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
. {color:green}+1{color} the patch does not introduce any @author tags
. {color:green}+1{color} the patch does not introduce any tabs
. {color:green}+1{color} the patch does not introduce any trailing spaces
. {color:red}-1{color} the patch contains 1 line(s) longer than 120
characters
. {color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
. {color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
. {color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
. {color:red}WARNING{color}: the current HEAD has 8 Javadoc warning(s)
{color:green}+1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:green}+1{color} the patch does not seem to introduce new javac
warnings
. {color:red}WARNING{color}: the current HEAD has 9 javac warning(s)
{color:green}+1 FINDBUGS{color}
. {color:green}+1{color} the patch does not seem to introduce new Findbugs
warnings
. {color:red}WARNING: the current HEAD has Findbugs warning(s), they should
be addressed ASAP{color}
{color:red}-1 TESTS{color}
. Tests run: 390
. Tests failed: 5
. Tests errors: 36
. The patch failed the following testcases:
.
testLedgerCreationShouldFailWithReadonlyBookie(org.apache.bookkeeper.test.ReadOnlyBookieTest)
.
testAsyncBookieRecoveryToRandomBookies[0](org.apache.bookkeeper.client.BookieRecoveryTest)
.
testAsyncBookieRecoveryToRandomBookies[1](org.apache.bookkeeper.client.BookieRecoveryTest)
.
testAsyncBookieRecoveryToRandomBookies[2](org.apache.bookkeeper.client.BookieRecoveryTest)
.
testAsyncBookieRecoveryToRandomBookies[3](org.apache.bookkeeper.client.BookieRecoveryTest)
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/bookkeeper-trunk-precommit-build/31/
> Provide mechanism to detect r-o bookie by the bookie clients
> -------------------------------------------------------------
>
> Key: BOOKKEEPER-347
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-347
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-client
> Affects Versions: 4.1.0
> Reporter: Rakesh R
> Assignee: Vinay
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-347.patch, BOOKKEEPER-347.patch,
> BOOKKEEPER-347.patch
>
>
> This jira to discuss, how the bookie client knows about the bookie running in
> r-o. This would be required by the client to choose writable bookies during
> add entries.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
