Internal build failure after commit 001fc99

[Reidddddd]

Internal nighty CI tried to build v2.5.7 yesterday (yesterday just pushed), while before v2.5.6(inclusive) every release were built successfully.

Built got error:

  error: failed to parse lock file at: /home/jenkins/agent/workspace/di-milvus/Release-Milvus-Image-Build/internal/core/thirdparty/tantivy/tantivy-binding/Cargo.lock
  
  Caused by:
    lock file version `4` was found, but this version of Cargo does not understand this lock file, perhaps Cargo needs to be updated?
  make[3]: *** [thirdparty/tantivy/CMakeFiles/tantivy_binding_target.dir/build.make:73: thirdparty/tantivy/compile_tantivy] Error 101
  make[3]: Leaving directory '/home/jenkins/agent/workspace/di-milvus/Release-Milvus-Image-Build/cmake_build'
  make[2]: *** [CMakeFiles/Makefile2:1668: thirdparty/tantivy/CMakeFiles/tantivy_binding_target.dir/all] Error 2

I'm pretty sure the rust and cargo version are correct, and only 1 version in the env

 cargo --version
 cargo 1.73.0 (9c4383fb5 2023-08-26)
 rustc --version
 rustc 1.73.0 (cc66ad468 2023-10-03)
 which cargo
 /root/.cargo/bin/cargo
 which rustc
 /root/.cargo/bin/rustc

 rustup show
 Default host: x86_64-unknown-linux-gnu
 rustup home:  /root/.rustup
 1.73-x86_64-unknown-linux-gnu (default)
 rustc 1.73.0 (cc66ad468 2023-10-03)

And I found this commit quite related, 001fc99

Any expert has insight about it?

[xiaofan-luan]

Possible Issues and Fixes:

1. Check Jenkins Build Environment

Jenkins might be running a different cargo binary than the one in /root/.cargo/bin/cargo. Try printing the Cargo version inside the Jenkins job:

cargo --version
which cargo

If it differs, Jenkins might be using a system-installed Cargo. You can force Jenkins to use Rust from rustup:

export PATH="$HOME/.cargo/bin:$PATH"
cargo --version  # Verify again

To persist this, add it to your Jenkins build script or the .bashrc file for the user running Jenkins.

2. Manually Remove and Regenerate Cargo.lock

If the build is still failing, try deleting and regenerating the Cargo.lock file:

rm -f thirdparty/tantivy/tantivy-binding/Cargo.lock
cargo generate-lockfile

Then retry the build.

3. Force Cargo to Use the Correct Rust Version in Jenkins

If Jenkins is overriding cargo with an older version, explicitly set the Rust version in your Jenkins build script:

rustup default stable
rustup override set stable

If your rust-toolchain file is missing in thirdparty/tantivy/tantivy-binding/, create it with:

echo "stable" > thirdparty/tantivy/tantivy-binding/rust-toolchain

This forces Cargo to use Rust from rustup.

4. Check System-Wide Cargo Version

Run:

/usr/bin/cargo --version

If this outputs an older version, Jenkins is likely using the system-wide Cargo instead of Rust installed via rustup. In this case, either update the system's Rust or modify Jenkins to use the rustup-managed version.

5. Reinstall Rust and Cargo (Last Resort)

If nothing works, try reinstalling Rust:

rustup self uninstall
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
source $HOME/.cargo/env
rustup install stable

Then retry your build.

Let me know what cargo --version shows inside Jenkins!

[kawaiinonian]

Build failure still happen after I regenerate a Cargo.lock file. Error message shows a requirement of higher rustc version. But once update and make, build failed again. It seems all caused by this line of Cargo.toml.
icu_segmenter = "2.0.0-beta2"
All compile goes right in v2.4.x.