Opt out of cargo build-dir layout v2 in CI test job - #1041
Closed
francisdb wants to merge 1 commit into
Closed
Conversation
Since nightly 2026-07-30, cargo enables its new build-dir layout by default (rust-lang/cargo#17258). cargo-nextest does not support the new layout yet: it builds the runtime library search path from the old target/debug[/deps] convention, so with bevy/dynamic_linking every test binary fails to load libbevy_dylib.so and test listing aborts. This currently breaks the Test Suite job on every PR. Set cargo's temporary opt-out env var in the test job to keep the old layout until a nextest release supports layout v2.
Author
|
Should no longer be needed as the issue in nextest has been fixed https://github.com/nextest-rs/nextest/releases/tag/cargo-nextest-0.9.143 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Objective
Since cargo nightly 2026-07-30, cargo enables its new build-dir layout by default (rust-lang/cargo#17258). cargo-nextest does not support the new layout yet: it builds the runtime library search path from the old target/debug[/deps] convention, so with bevy/dynamic_linking every test binary fails to load libbevy_dylib.so and test listing aborts. This currently breaks the Test Suite job on every PR.
Solution
Set cargo's temporary opt-out env var
__CARGO_TEMPORARY_BUILD_DIR_NEW_LAYOUT_OPT_OUTin the test job to keep the old layout until a nextest release supports layout v2.AI assisted
Testing
CI should now succeed, unlike #1040
Reported on the nextest side as nextest-rs/nextest#3512