[ https://issues.apache.org/jira/browse/HBASE-12684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14260184#comment-14260184 ]
Jurriaan Mous commented on HBASE-12684: --------------------------------------- I keep having problems with TestHCM. The relaxed timing does not seem to help so it is not a timing issue. Then the only probable thing that happened is that it failed to do a Get and escaped that thread. But because the xml failed for TestHCM I can't inspect the log to see on what error it escaped the Thread. On my machine the test always succeeds. https://builds.apache.org/job/PreCommit-HBASE-Build/12246//testReport/TEST-org.apache.hadoop.hbase.client.TestHCM/ bq. Failed to read test report file /home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-server/target/surefire-reports/TEST-org.apache.hadoop.hbase.client.TestHCM.xml org.dom4j.DocumentException: Error on line 5142 of document file:///home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-server/target/surefire-reports/TEST-org.apache.hadoop.hbase.client.TestHCM.xml : XML document structures must start and end within the same entity. {code:title=TestHCM.java:378} } catch (Throwable t) { failed.set(t); LOG.error(t); } {code} Is it possible to get that log in any other way on the build server? Or is there a way to run the test in the same way as Jenkins so I can see for myself what fails? It is the last test holding this new client back... > Add new AsyncRpcClient > ---------------------- > > Key: HBASE-12684 > URL: https://issues.apache.org/jira/browse/HBASE-12684 > Project: HBase > Issue Type: Improvement > Components: Client > Reporter: Jurriaan Mous > Assignee: Jurriaan Mous > Attachments: HBASE-12684-v1.patch, HBASE-12684-v10.patch, > HBASE-12684-v11.patch, HBASE-12684-v12.patch, HBASE-12684-v13.patch, > HBASE-12684-v14.patch, HBASE-12684-v15.patch, HBASE-12684-v16.patch, > HBASE-12684-v17.patch, HBASE-12684-v2.patch, HBASE-12684-v3.patch, > HBASE-12684-v4.patch, HBASE-12684-v5.patch, HBASE-12684-v6.patch, > HBASE-12684-v7.patch, HBASE-12684-v8.patch, HBASE-12684-v9.patch, > HBASE-12684.patch > > > With the changes in HBASE-12597 it is possible to add new RpcClients. This > issue is about adding a new Async RpcClient which would enable HBase to do > non blocking protobuf service communication. > Besides delivering a new AsyncRpcClient I would also like to ask the question > what it would take to replace the current RpcClient? This would enable to > simplify async code in some next issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)