hrsgn removed a comment on issue #3600:
URL: 
https://github.com/apache/incubator-heron/issues/3600#issuecomment-669940943


   
   
   
   > Hi,
   > 
   > It looks like you are using Bazel version 0.26.0. At this time Heron needs 
to be built with Bazel 3.4.1.
   > 
   > I found where the documentation is incorrect. We will get this fixed ASAP.
   
   Thank you very much, and there is a new problem as below:
   
   [zw@centos01 incubator-heron]$ bazel build --config=centos heron/...
   DEBUG: 
/home/zw/.cache/bazel/_bazel_zw/0d94d7c020c06b4f73081720ff5e8130/external/bazel_tools/tools/cpp/lib_cc_configure.bzl:118:10:
 
   Auto-Configuration Warning: CC with -fuse-ld=gold returned 0, but its -v 
output didn't contain 'gold', falling back to the default linker.
   INFO: SHA256 
(https://archive.apache.org/dist/zookeeper/zookeeper-3.5.8/apache-zookeeper-3.5.8.tar.gz)
 = bafc0abe7da696a2020ba11b8ce7d06f6e28e9bf1e5504de09be25b8b589777d
   DEBUG: Rule 'org_apache_zookeeper' indicated that a canonical reproducible 
form can be obtained by modifying arguments sha256 = 
"bafc0abe7da696a2020ba11b8ce7d06f6e28e9bf1e5504de09be25b8b589777d"
   DEBUG: Repository org_apache_zookeeper instantiated at:
     no stack (--record_rule_instantiation_callstack not enabled)
   Repository rule http_archive defined at:
     
/home/zw/.cache/bazel/_bazel_zw/0d94d7c020c06b4f73081720ff5e8130/external/bazel_tools/tools/build_defs/repo/http.bzl:336:31:
 in <toplevel>
   INFO: Repository io_bazel_rules_scala_scalatest instantiated at:
     no stack (--record_rule_instantiation_callstack not enabled)
   Repository rule jvm_import_external defined at:
     
/home/zw/.cache/bazel/_bazel_zw/0d94d7c020c06b4f73081720ff5e8130/external/io_bazel_rules_scala/scala/scala_maven_import_external.bzl:207:38:
 in <toplevel>
   WARNING: Download from 
https://repo.maven.apache.org/maven2/org/scalatest/scalatest_2.12/3.0.5/scalatest_2.12-3.0.5.jar
 failed: class 
com.google.devtools.build.lib.bazel.repository.downloader.UnrecoverableHttpException
 Checksum was 978e7c4cb797f5d17e4cd8b928eda0c56d98d786537ed0917c409268888b9921 
but wanted b416b5bcef6720da469a8d8a5726e457fc2d1cd5d316e1bc283aa75a2ae005e5
   ERROR: An error occurred during the fetch of repository 
'io_bazel_rules_scala_scalatest':
      java.io.IOException: Error downloading 
[https://repo.maven.apache.org/maven2/org/scalatest/scalatest_2.12/3.0.5/scalatest_2.12-3.0.5.jar]
 to 
/home/zw/.cache/bazel/_bazel_zw/0d94d7c020c06b4f73081720ff5e8130/external/io_bazel_rules_scala_scalatest/scalatest_2.12-3.0.5.jar:
 Checksum was 978e7c4cb797f5d17e4cd8b928eda0c56d98d786537ed0917c409268888b9921 
but wanted b416b5bcef6720da469a8d8a5726e457fc2d1cd5d316e1bc283aa75a2ae005e5
   **ERROR**: 
/home/zw/.cache/bazel/_bazel_zw/0d94d7c020c06b4f73081720ff5e8130/external/io_bazel_rules_scala/scala/scalatest/BUILD:5:13:
 @io_bazel_rules_scala//scala/scalatest:scalatest depends on 
@io_bazel_rules_scala_scalatest//:io_bazel_rules_scala_scalatest in repository 
@io_bazel_rules_scala_scalatest which failed to fetch. no such package 
'@io_bazel_rules_scala_scalatest//': java.io.IOException: Error downloading 
[https://repo.maven.apache.org/maven2/org/scalatest/scalatest_2.12/3.0.5/scalatest_2.12-3.0.5.jar]
 to 
/home/zw/.cache/bazel/_bazel_zw/0d94d7c020c06b4f73081720ff5e8130/external/io_bazel_rules_scala_scalatest/scalatest_2.12-3.0.5.jar:
 Checksum was 978e7c4cb797f5d17e4cd8b928eda0c56d98d786537ed0917c409268888b9921 
but wanted b416b5bcef6720da469a8d8a5726e457fc2d1cd5d316e1bc283aa75a2ae005e5
   ERROR: Analysis of target '//heron/api/tests/scala:api-scala-test' failed; 
build aborted: Analysis failed
   INFO: Elapsed time: 2757.191s
   INFO: 0 processes.
   FAILED: Build did NOT complete successfully (418 packages loaded, 5422 
targets configured)


----------------------------------------------------------------
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