busbey commented on pull request #2180: URL: https://github.com/apache/hbase/pull/2180#issuecomment-667624039
I do not know why the precommit job on ci-hadoop ran multiple jobs for this PR, but in run number 2 this was the failure: ``` [INFO] [ERROR] Errors: [ERROR] org.apache.hadoop.hbase.client.TestFromClientSideWithCoprocessor5.testScanMetrics[1] [ERROR] Run 1: TestFromClientSideWithCoprocessor5>TestFromClientSide5.testScanMetrics:989 Did not count the result bytes expected:<60> but was:<180> [ERROR] Run 2: TestFromClientSideWithCoprocessor5>TestFromClientSide5.testScanMetrics:922 » IO [ERROR] Run 3: TestFromClientSideWithCoprocessor5>TestFromClientSide5.testScanMetrics:922 » IO ``` in run number three there were no failures. Looking at [the test ouput for TestFromClientSideWithCoprocessor5](https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2180/2/artifact/yetus-jdk8-hadoop3-check/output/archiver/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.client.TestFromClientSideWithCoprocessor5-output.txt), I don't think there's enough detail to figure out what happened. It looks like the final two were loss of ZK under load: ``` ------------------------------------------------------------------------------- Test set: org.apache.hadoop.hbase.client.TestFromClientSideWithCoprocessor5 ------------------------------------------------------------------------------- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 332.892 s <<< FAILURE! - in org.apache.hadoop.hbase.client.TestFromClientSideWithCoprocessor5 org.apache.hadoop.hbase.client.TestFromClientSideWithCoprocessor5.testScanMetrics[1] Time elapsed: 33.18 s <<< ERROR! java.io.IOException: org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /hbase/hbaseid Caused by: org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /hbase/hbaseid ``` If I had to guess I'd say in the first case maybe we have a retry mechanism that can recount scan metrics? In any case I am reasonably certain these failures are not related to the test change here. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
