We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When building zenoh-c with the latest Rust toolchain 1.80.0, it passed on main but failed on dev/1.0.0 with the following log
error: failed to run custom build command for `zenoh-c v0.11.0-dev (/workspace/src/zenoh-c)` note: To improve backtraces for build dependencies, set the CARGO_PROFILE_DEV_BUILD_OVERRIDE_DEBUG=true environment variable to enable debug information generation. Caused by: process didn't exit successfully: `/workspace/src/zenoh-c/target/debug/build/zenoh-c-5c9a536c45363946/build-script-build` (exit status: 101) --- stderr thread 'main' panicked at build.rs:73:34: called `Result::unwrap()` on an `Err` value: "z_owned_bytes_t not found (requested explicitly by splitguide.yaml)" stack backtrace: 0: 0x5926d09419b5 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h3692694645b1bb6a 1: 0x5926d096b6fb - core::fmt::write::h5131d80b4c69b88d 2: 0x5926d093ee8f - std::io::Write::write_fmt::h1fb327a7d8b0eb36 3: 0x5926d094178e - std::sys_common::backtrace::print::h998d75b840f75a73 4: 0x5926d0942d49 - std::panicking::default_hook::{{closure}}::h18ec7fe6a38b9da0 5: 0x5926d0942aea - std::panicking::default_hook::hfb3f22c2e4075a6a 6: 0x5926d09431e3 - std::panicking::rust_panic_with_hook::h51af00bcb4660c4e 7: 0x5926d09430c4 - std::panicking::begin_panic_handler::{{closure}}::h39f76aa863fbe8ce 8: 0x5926d0941e79 - std::sys_common::backtrace::__rust_end_short_backtrace::h4d10fc2251b89840 9: 0x5926d0942df7 - rust_begin_unwind 10: 0x5926d01bb5b3 - core::panicking::panic_fmt::h319840fcbcd912ef 11: 0x5926d01bbb86 - core::result::unwrap_failed::haccb9aaa604e1e21 12: 0x5926d01e5fa8 - build_script_build::main::h482fb9bad024fb13 13: 0x5926d01e1b03 - core::ops::function::FnOnce::call_once::ha3721b8c77065de7 14: 0x5926d0262f86 - std::sys_common::backtrace::__rust_begin_short_backtrace::h76ddc3f2a85aace5 15: 0x5926d02f2539 - std::rt::lang_start::{{closure}}::h6252f24aa8edd9e0 16: 0x5926d093a57d - std::rt::lang_start_internal::h63a185b0ddd212e9 17: 0x5926d02f2517 - std::rt::lang_start::h9299f1e8555e3077 18: 0x5926d01f83b5 - main 19: 0x76c77d02a1ca - __libc_start_call_main at ./csu/../sysdeps/nptl/libc_start_call_main.h:58:16 20: 0x76c77d02a28b - __libc_start_main_impl at ./csu/../csu/libc-start.c:360:3 21: 0x5926d01bc0c5 - _start 22: 0x0 - <unknown>
The text was updated successfully, but these errors were encountered:
Closed by #560
Sorry, something went wrong.
No branches or pull requests
Describe the bug
When building zenoh-c with the latest Rust toolchain 1.80.0, it passed on main but failed on dev/1.0.0 with the following log
System info
The text was updated successfully, but these errors were encountered: