Failed build using supplied Docker #77
Comments
|
I think I know why this is happening: bazelisk downloads a dynamically chosen bazel binary when run, and they recently pushed a new version of bazel by default. I don't know why we're doing a checksum in the dockerfile, and you could just delete that checksum as a temporary workaround. |
|
I tried the alternative version to download the code and build from scratch and manually updated the WORKSPACE file to point to the hash identified in the error. Ran again and had to update the remaining fields for strip_prefix and url based on new errors. It made it further in the build process but then could not find required functions when executing the demo code. I'm not overly familiar with Bazel /Bazalisk so I may have done something wrong. If there is a way we can update the code so it points to the correct dependencies versus the latest versions and make the build stable that would be greatly appreciated. |
|
To follow up with my efforts. I attempted to modify the WORKSPACE file on an Ubuntu VM before running the command: The first edit I did was to remove the reference to the SHA256 hash for com_grail_bazel_toolchain. bazel run //transpiler/examples/hangman:hangman_client This seems to indicate that the WORKSPACE entry also has a bad reference to the source file has been renamed from "bazel-toolchain-0.8" to "toolchains_llvm-0.8". ubuntu@ubun2004: I then modified the WORKSPACE file again to set the prefix to "toolchains_llvm-0.8" and ran again. It spent about an hour building and then failed. However I think the failure was due to running out out space on a partition on the VM I was using. I'll have to try again with a bigger allocation. It Failed after 10GB was added to the /home directory. Not sure how big the entire system is to adjust the size. |
|
Didn't mean to close with my last comment. The docker build still references the hard coded data and fails to build |
|
Ok this is a bit of a long log. I tried to build on an EC2 Ubnuntu instance just to test if the process worked. After editing the WORKSPACE as described above, I tired to build one of the examples. After about 2 hours it failed. Any idea why it failed? The error from the below logs is extracted here followed by the full logs: Generating IR... Configuration: 625532f7154e1e5cbaf1a4b5258178981d880ae5b5931cdec360902c2ad0c853Execution platform: @local_config_platform//:hostUse --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging ubuntu@ip-172-31-6-221: Configuration: 625532f7154e1e5cbaf1a4b5258178981d880ae5b5931cdec360902c2ad0c853Execution platform: @local_config_platform//:hostUse --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging Bazel external C/C++ Rules. Building library abc Environment:______________
Target //transpiler/examples/fibonacci:fibonacci_rs_main failed to build |
|
In the last comment, the https://tiswww.case.edu/php/chet/readline/rltop.html I will take a look at fixing this later this week, but if you're interested in using the transpiler, I'd recommend you try https://github.com/google/heir instead. The transpiler was a research prototype, and HEIR is our long-term plan for a production-ready compiler. If you provide some info in that repository about what you're trying to do with FHE, that can help us prioritize feature work there and/or guide you to how to use HEIR to achieve your goal. |
While using the supplied instructions to build the docker image, the process fails. There seems to be some checksum error with loading com_grail_bazel_toolchain
Error message log data is below:
debian-bullseye.Dockerfile:51
49 | # it's necessary for some reason, this will allow docker to cache the resulting
50 | # image and build failures unrelated to LLVM will not incur a rebuild of LLVM.
51 | >>> RUN bazel build @llvm_toolchain//:all
52 |
53 | # Build all targets.
ERROR: failed to solve: process "/bin/sh -c bazel build @llvm_toolchain//:all" did not complete successfully: exit code: 1
The text was updated successfully, but these errors were encountered: