Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

//docs tests are broken in MacOS #138

Open
jjmaestro opened this issue Dec 11, 2024 · 0 comments · May be fixed by #139
Open

//docs tests are broken in MacOS #138

jjmaestro opened this issue Dec 11, 2024 · 0 comments · May be fixed by #139

Comments

@jjmaestro
Copy link
Contributor

Whilw working on #136 I saw that the //docs/ tests are broken in MacOS:

% bazel test //docs/... --cache_test_results=no
WARNING: Ignoring JAVA_HOME, because it must point to a JDK, not a JRE.
WARNING: /private/var/tmp/_bazel_jjmaestro/be9c074a2171a3cb6c673d10113bd570/external/stardoc~/src/main/java/com/google/devtools/build/stardoc/rendering/BUILD:14:13: in java_library rule @@stardoc~//src/main/java/com/google/devtools/build/stardoc/rendering:rendering: target '@@stardoc~//src/main/java/com/google/devtools/build/stardoc/rendering:rendering' depends on deprecated target '@@stardoc~//stardoc/proto:stardoc_output_java_proto': Use java_proto_library from com_google_protobuf
WARNING: /private/var/tmp/_bazel_jjmaestro/be9c074a2171a3cb6c673d10113bd570/external/stardoc~/src/main/java/com/google/devtools/build/stardoc/renderer/BUILD:29:13: in java_library rule @@stardoc~//src/main/java/com/google/devtools/build/stardoc/renderer:renderer_lib: target '@@stardoc~//src/main/java/com/google/devtools/build/stardoc/renderer:renderer_lib' depends on deprecated target '@@stardoc~//stardoc/proto:stardoc_output_java_proto': Use java_proto_library from com_google_protobuf
INFO: Analyzed 10 targets (76 packages loaded, 1440 targets configured).
ERROR: /private/var/tmp/_bazel_jjmaestro/be9c074a2171a3cb6c673d10113bd570/external/abseil-cpp~/absl/log/internal/BUILD.bazel:236:11: Compiling absl/log/internal/nullguard.cc [for tool] failed: (Exit 1): cc_wrapper.sh failed: error executing CppCompile command (from target @@abseil-cpp~//absl/log/internal:nullguard) external/bazel_tools~cc_configure_extension~local_config_cc/cc_wrapper.sh -U_FORTIFY_SOURCE -fstack-protector -Wall -Wthread-safety -Wself-assign -Wunused-but-set-parameter -Wno-free-nonheap-object ... (remaining 78 arguments skipped)

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
external/abseil-cpp~/absl/log/internal/nullguard.cc:17:10: error: module abseil-cpp~//absl/log/internal:nullguard does not depend on a module exporting 'array'
   17 | #include <array>
      |          ^
1 error generated.
Use --verbose_failures to see the command lines of failed build steps.
ERROR: /private/var/tmp/_bazel_jjmaestro/be9c074a2171a3cb6c673d10113bd570/external/stardoc~/src/main/java/com/google/devtools/build/stardoc/renderer/BUILD:29:13 Building external/stardoc~/src/main/java/com/google/devtools/build/stardoc/renderer/librenderer_lib.jar (4 source files) [for tool] failed: (Exit 1): cc_wrapper.sh failed: error executing CppCompile command (from target @@abseil-cpp~//absl/log/internal:nullguard) external/bazel_tools~cc_configure_extension~local_config_cc/cc_wrapper.sh -U_FORTIFY_SOURCE -fstack-protector -Wall -Wthread-safety -Wself-assign -Wunused-but-set-parameter -Wno-free-nonheap-object ... (remaining 78 arguments skipped)

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
INFO: Elapsed time: 0.816s, Critical Path: 0.52s
INFO: 28 processes: 28 internal.
ERROR: Build did NOT complete successfully
//docs:update_0_test                                                  NO STATUS
//docs:update_1_test                                                  NO STATUS
//docs:update_2_test                                                  NO STATUS

Executed 0 out of 3 tests: 3 were skipped.
jjmaestro added a commit to jjmaestro/rules_distroless that referenced this issue Dec 11, 2024
@jjmaestro jjmaestro linked a pull request Dec 11, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant