dwsmith1983 opened a new issue, #7609: URL: https://github.com/apache/datafusion-comet/issues/7609
### Describe the bug `rust-test` fails since Rust 1.100.0 became the stable toolchain on 2026-11-12. `rust-toolchain.toml` tracks `stable`, so every PR and the merge queue now pick it up. The merge queue run for #7608 failed this way: https://github.com/apache/datafusion-comet/actions/runs/43339215892 The first failures are in `comet_native_udf_bridge`, and nextest stops there: ``` run `cargo build -p comet-test-udfs` first: Internal("failed to open .../native/target/debug/build/libcomet_test_udfs.so: cannot open shared object file: No such file or directory") ``` The library is built; the path is wrong. `native/core/build.rs` sets `COMET_TEST_UDFS_LIB` by taking the third ancestor of `OUT_DIR`, assuming `target/<profile>/build/<pkg>-<hash>/out`. Cargo 1.100 uses the new build-dir layout, which splits the package name and hash into two directories: ``` 1.99.0 OUT_DIR=.../target/debug/build/odprobe-df8bb64132399cde/out 1.100.0 OUT_DIR=.../target/debug/build/odprobe/a333b6d15c5ac5f2/out ``` So the third ancestor is now `target/debug/build`. The cdylib itself is still written to `target/debug/libcomet_test_udfs.so`. Every test that goes through `test_udfs_path()` (the c_udf loader, cache and planner tests as well) reads the same variable. ### Steps to reproduce With Rust 1.100.0: ```shell cd native cargo build -p comet-test-udfs cargo test -p datafusion-comet --lib comet_native_udf_bridge ``` ### Expected behavior `COMET_TEST_UDFS_LIB` points at `target/<profile>/libcomet_test_udfs.so` under both layouts. Taking the parent of the nearest `build` ancestor of `OUT_DIR`, rather than a fixed depth, would cover both. Pinning `rust-toolchain.toml` to 1.99 would unblock the queue in the meantime. ### Additional context The `OUT_DIR` lines above come from an empty crate whose `build.rs` prints `OUT_DIR`, built with each toolchain. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
