Closed giordano closed 9 months ago
Alright, I finally managed to get some more useful error messages, for the failure at https://github.com/JuliaPackaging/BinaryBuilderBase.jl/blob/8d1eca1e3a63a2de30d9a9eee7381c9ca999ea60/test/runners.jl#L446
rustc -o /tmp/testsuite/x86_64-linux-gnu/rust/hello_world/hello_world hello_world.rs
Installing cargo_build v0.1.0 (/usr/share/testsuite/rust/cargo_build)
error: failed to compile `cargo_build v0.1.0 (/usr/share/testsuite/rust/cargo_build)`, intermediate artifacts can be found at `/usr/share/testsuite/rust/cargo_build/target`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.
Caused by:
Cross-device link (os error 18)
make[1]: *** [Makefile:7: /tmp/testsuite/x86_64-linux-gnu/rust/cargo_build/cargo_build] Error 101
make: *** [Makefile:48: install-project-rust-cargo_build] Error 2
Sounds like a problem in the sandbox code, which perhaps only arises on the CI setup.
My diagnosis, reported in https://github.com/JuliaPackaging/BinaryBuilderBase.jl/pull/325#issuecomment-1793450297, is that we're running out of disk in the non-squashfs jobs, using Julia v1.9 was useful as it prints a more informative error message when a download fails.
@gbaraldi now here I'm getting a new error (https://github.com/JuliaPackaging/BinaryBuilderBase.jl/actions/runs/6754524952/job/18362088675?pr=346#step:8:131):
It's with clang and it's a linker error involving lld, but the problem is that I can't reproduce it locally. The failing test is https://github.com/JuliaPackaging/BinaryBuilderBase.jl/blob/8d1eca1e3a63a2de30d9a9eee7381c9ca999ea60/test/runners.jl#L207
Edit: ~this still appears after rebasing on top of #345.~ Sorry, I was looking at the wrong log, this goes away with your PR: https://github.com/JuliaPackaging/BinaryBuilderBase.jl/actions/runs/6754635721/job/18362311393?pr=346