Skip to content

Pin Rust 1.99 in Linux CI until ort supports Rust 1.100 - #55

Open
reidmorrison wants to merge 1 commit into
elixir-nx:mainfrom
reidmorrison:ci-pin-rust-1.99
Open

reidmorrison wants to merge 1 commit into
elixir-nx:mainfrom
reidmorrison:ci-pin-rust-1.99

Conversation

@reidmorrison

Copy link
Copy Markdown

Rust 1.100 (due Nov 12) changes cargo's build directory layout. The copy-dylibs step in ort-sys 2.0.0-rc.8 can't handle the new layout, so builds that link ONNX Runtime dynamically fail in the ort-sys build script. That includes the cuda/tensorrt features, which the Linux CI job enables through config/config.exs. I reproduced it on 1.100.0-beta.7; static CPU builds are fine.

This pins the Linux job to 1.99.1 and adds a short README note for GPU users. The real fix is moving to ort rc.14 or later. Happy to help with that separately if you want.

Rust 1.100 (due 2026-11-12) ships cargo's new build-dir layout. The
copy-dylibs step in ort-sys 2.0.0-rc.8 cannot handle it, so any build
that links ONNX Runtime dynamically fails in the ort-sys build script.
That includes the cuda/tensorrt features, which config/config.exs
enables for the Linux CI job. Static CPU builds, the default for apps
that depend on Ortex, are not affected.

Pin the Linux job to Rust 1.99.1 and note the limitation in the README.
The macOS job (static CoreML build) keeps using the runner's latest Rust.
Remove the pin once ort is upgraded (rc.14 and later support the new
layout).
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 this pull request may close these issues.

1 participant