Apache-HBase commented on pull request #75:
URL: https://github.com/apache/hbase-connectors/pull/75#issuecomment-733005091


   :broken_heart: **-1 overall**
   
   
   
   
   
   
   | Vote | Subsystem | Runtime | Comment |
   |:----:|----------:|--------:|:--------|
   | +0 :ok: |  reexec  |   1m  8s |  Docker mode activated.  |
   ||| _ Prechecks _ |
   | +1 :green_heart: |  dupname  |   0m  0s |  No case conflicting files 
found.  |
   | +0 :ok: |  markdownlint  |   0m  0s |  markdownlint was not available.  |
   | +1 :green_heart: |  @author  |   0m  0s |  The patch does not contain any 
@author tags.  |
   | -0 :warning: |  test4tests  |   0m  0s |  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.  |
   ||| _ master Compile Tests _ |
   | +0 :ok: |  mvndep  |   0m 16s |  Maven dependency ordering for branch  |
   | +1 :green_heart: |  mvninstall  |   1m 24s |  master passed  |
   | -1 :x: |  compile  |   0m 24s |  spark in master failed.  |
   | +1 :green_heart: |  scaladoc  |   0m 17s |  master passed  |
   ||| _ Patch Compile Tests _ |
   | +0 :ok: |  mvndep  |   0m  4s |  Maven dependency ordering for patch  |
   | +1 :green_heart: |  mvninstall  |   0m 44s |  the patch passed  |
   | -1 :x: |  compile  |   0m 23s |  spark in the patch failed.  |
   | -1 :x: |  scalac  |   0m 23s |  spark in the patch failed.  |
   | -1 :x: |  whitespace  |   0m  0s |  The patch has 2 line(s) that end in 
whitespace. Use git apply --whitespace=fix <<patch_file>>. Refer 
https://git-scm.com/docs/git-apply  |
   | +1 :green_heart: |  scaladoc  |   0m 17s |  the patch passed  |
   ||| _ Other Tests _ |
   | -1 :x: |  unit  |   0m 27s |  spark in the patch failed.  |
   | +1 :green_heart: |  unit  |   3m 55s |  hbase-spark in the patch passed.  |
   |  |   |  10m 40s |   |
   
   
   | Subsystem | Report/Notes |
   |----------:|:-------------|
   | Docker | ClientAPI=1.40 ServerAPI=1.40 base: 
https://ci-hadoop.apache.org/job/HBase/job/HBase-Connectors-PreCommit/job/PR-75/1/artifact/yetus-precommit-check/output/Dockerfile
 |
   | GITHUB PR | https://github.com/apache/hbase-connectors/pull/75 |
   | Optional Tests | dupname markdownlint scalac scaladoc unit compile |
   | uname | Linux 1e4cb11fc2f4 5.4.0-1025-aws #25~18.04.1-Ubuntu SMP Fri Sep 
11 12:03:04 UTC 2020 x86_64 GNU/Linux |
   | Build tool | hb_maven |
   | Personality | dev-support/jenkins/hbase-personality.sh |
   | git revision | master / b9706c8 |
   | compile | 
https://ci-hadoop.apache.org/job/HBase/job/HBase-Connectors-PreCommit/job/PR-75/1/artifact/yetus-precommit-check/output/branch-compile-spark.txt
 |
   | compile | 
https://ci-hadoop.apache.org/job/HBase/job/HBase-Connectors-PreCommit/job/PR-75/1/artifact/yetus-precommit-check/output/patch-compile-spark.txt
 |
   | scalac | 
https://ci-hadoop.apache.org/job/HBase/job/HBase-Connectors-PreCommit/job/PR-75/1/artifact/yetus-precommit-check/output/patch-compile-spark.txt
 |
   | whitespace | 
https://ci-hadoop.apache.org/job/HBase/job/HBase-Connectors-PreCommit/job/PR-75/1/artifact/yetus-precommit-check/output/whitespace-eol.txt
 |
   | unit | 
https://ci-hadoop.apache.org/job/HBase/job/HBase-Connectors-PreCommit/job/PR-75/1/artifact/yetus-precommit-check/output/patch-unit-spark.txt
 |
   |  Test Results | 
https://ci-hadoop.apache.org/job/HBase/job/HBase-Connectors-PreCommit/job/PR-75/1/testReport/
 |
   | Max. process+thread count | 917 (vs. ulimit of 12500) |
   | modules | C: spark spark/hbase-spark U: spark |
   | Console output | 
https://ci-hadoop.apache.org/job/HBase/job/HBase-Connectors-PreCommit/job/PR-75/1/console
 |
   | versions | git=2.20.1 |
   | Powered by | Apache Yetus 0.12.0 https://yetus.apache.org |
   
   
   This message was automatically generated.
   
   


----------------------------------------------------------------
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:
[email protected]


Reply via email to