search

tweag / inline-java

Haskell/Java interop via inline Java code in Haskell modules.
BSD 3-Clause "New" or "Revised" License
229 stars 15 forks source link

cpp:hello-success-test fails on macOS Monterey (aarch64) #190

Closed johannes-riecken closed 1 year ago

johannes-riecken commented 1 year ago

Describe the bug

During build of inline-java, the test cpp:hello-success-test fails.

To Reproduce

nix-shell --pure --run "bazel build //..."

Expected behavior Successfull build.

Environment

Additional context Full logs. The logs don't seem to give away much. I'd gladly provide more info, but I would need instructions for that, as I haven't used nix before.

facundominguez commented 1 year ago

Thanks @johannes-riecken.

The logs reference this file

/private/tmp/nix-build-bazel-3.7.2.drv-0/_bazel__nixbld1/0db12c2eee7edde9deccb427b5753c61/execroot/io_bazel/bazel-out/darwin-fastbuild/testlogs/examples/cpp/hello-success_test/test.log

I wonder if it might contain other clues.

I don't have a Monterrey system to test this, but adding a github action to run tests in darwin would improve the chances to study this issue.

johannes-riecken commented 1 year ago

Hmm, the temp directory doesn't contain any nix files after running the command. Any idea how I can keep them or how else we can get more info about the error? I tried to add additional command options to the command in the hopes of keeping temp files, but they're still gone.

nix-shell --keep-outputs --pure --run "bazel --sandbox_debug build //..."
facundominguez commented 1 year ago

I discovered that I don't know where to find the failing test. After having a second look at the log, it seems that nix is failing to build some dependency rather than inline-java. It confused me a bit because it also uses bazel.

facundominguez commented 1 year ago

@johannes-riecken, I'm closing this because it refers to a test in a dependency. But please, feel free to reach out if you find something we can do to help on the inline-java side.