[
https://issues.apache.org/jira/browse/HBASE-19102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16223170#comment-16223170
]
Hadoop QA commented on HBASE-19102:
-----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
12s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
1s{color} | {color:blue} Findbugs executables are not available. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 1m
32s{color} | {color:red} root in master failed. {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red} 0m
39s{color} | {color:red} hbase-server in master failed. {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
51s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
25s{color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} shadedjars {color} | {color:red} 2m
31s{color} | {color:red} branch has 348 errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
38s{color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 1m
31s{color} | {color:red} root in the patch failed. {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red} 0m
36s{color} | {color:red} hbase-server in the patch failed. {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red} 0m 36s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
49s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:red}-1{color} | {color:red} shadedjars {color} | {color:red} 1m
10s{color} | {color:red} patch has 348 errors when building our shaded
downstream artifacts. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 2m
4s{color} | {color:red} The patch causes 348 errors with Hadoop v2.6.1. {color}
|
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 2m
58s{color} | {color:red} The patch causes 348 errors with Hadoop v2.6.2.
{color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 3m
51s{color} | {color:red} The patch causes 348 errors with Hadoop v2.6.3.
{color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 4m
44s{color} | {color:red} The patch causes 348 errors with Hadoop v2.6.4.
{color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 5m
37s{color} | {color:red} The patch causes 348 errors with Hadoop v2.6.5.
{color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 6m
30s{color} | {color:red} The patch causes 348 errors with Hadoop v2.7.1.
{color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 7m
23s{color} | {color:red} The patch causes 348 errors with Hadoop v2.7.2.
{color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 8m
17s{color} | {color:red} The patch causes 348 errors with Hadoop v2.7.3.
{color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 9m
12s{color} | {color:red} The patch causes 348 errors with Hadoop v3.0.0-alpha4.
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
36s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 0m 36s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
10s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 19m 44s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-19102 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12894276/HBASE-19102.master.001.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs shadedjars
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux 50a3ac7283c0 3.13.0-129-generic #178-Ubuntu SMP Fri Aug 11
12:48:20 UTC 2017 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build@2/component/dev-support/hbase-personality.sh
|
| git revision | master / f6c2490b82 |
| Default Java | 1.8.0_141 |
| mvninstall |
https://builds.apache.org/job/PreCommit-HBASE-Build/9462/artifact/patchprocess/branch-mvninstall-root.txt
|
| compile |
https://builds.apache.org/job/PreCommit-HBASE-Build/9462/artifact/patchprocess/branch-compile-hbase-server.txt
|
| mvninstall |
https://builds.apache.org/job/PreCommit-HBASE-Build/9462/artifact/patchprocess/patch-mvninstall-root.txt
|
| compile |
https://builds.apache.org/job/PreCommit-HBASE-Build/9462/artifact/patchprocess/patch-compile-hbase-server.txt
|
| javac |
https://builds.apache.org/job/PreCommit-HBASE-Build/9462/artifact/patchprocess/patch-compile-hbase-server.txt
|
| unit |
https://builds.apache.org/job/PreCommit-HBASE-Build/9462/artifact/patchprocess/patch-unit-hbase-server.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/9462/testReport/ |
| modules | C: hbase-server U: hbase-server |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/9462/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> TestZooKeeperMainServer fails with KeeperException$ConnectionLossException
> --------------------------------------------------------------------------
>
> Key: HBASE-19102
> URL: https://issues.apache.org/jira/browse/HBASE-19102
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: stack
> Attachments: HBASE-19102.master.001.patch
>
>
> I'm trying to run test suite on a local machine. I never get to the second
> part because I fail on below test with below exception near every time (and
> an ipv6 test... will do that next).
> 1
> -------------------------------------------------------------------------------
> 2 Test set: org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
> 3
> -------------------------------------------------------------------------------
> 4 Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 16.161 s
> <<< FAILURE! - in org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer
> 5
> testCommandLineWorks(org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer)
> Time elapsed: 15.848 s <<< ERROR!
> 6 org.apache.zookeeper.KeeperException$ConnectionLossException:
> KeeperErrorCode = ConnectionLoss for /testCommandLineWorks
> 7 at
> org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer.testCommandLineWorks(TestZooKeeperMainServer.java:81)
> Looks like running the command before we are connected causes the above -- we
> pause 15 seconds and then throw the above. If I wait until connected before
> proceding, stuff seems to work reliably. I don't have access to the watcher
> on connections since we override the zk main class... so this seems only
> avenue available at mo (This zk main thing is all a hack around zk main
> because it had bugs ... but I think we have to keep the hack because folks
> use different versions of zk. My $workplace defaults to something that is
> years old, 3.4.5 for instance).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
