- Notifications
You must be signed in to change notification settings - Fork13.6k
tests: Skip supported-crate-types test on musl hosts#144144
New issue
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Open
Gelbpunkt wants to merge1 commit intorust-lang:masterChoose a base branch
base:master
Could not load branches
Branch not found:{{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline, and old review comments may become outdated.
+5 −0
Conversation
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
This test depends on the target-specific behavior of crt-static for musltargets. However, running the testsuite on a musl host requiressetting `crt-static` to `false`, as it wouldn't otherwise be possible tobuild rustc. This in turn will enable `-Ctarget-feature=-crt-static` forall tests, mismatching the expected `+crt-static` for the musl targettested in this testcase.Since this test specifically tests the default value of `crt-static` forthe musl target, ignoring it entirely makes more sense than manuallysetting `-Ctarget-feature=+crt-static` here, but both would be validapproaches.Signed-off-by: Jens Reidel <adrian@travitia.xyz>
rustbot has assigned@SparrowLii. Use |
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Labels
S-waiting-on-reviewStatus: Awaiting review from the assignee but also interested parties. T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.
3 participants
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.
Uh oh!
There was an error while loading.Please reload this page.
This test depends on the target-specific default of crt-static for musl targets. However, running the testsuite on a musl host requires setting
crt-statictofalse, as it wouldn't otherwise be possible to build rustc. This in turn will enable-Ctarget-feature=-crt-staticfor all tests, mismatching the expected+crt-staticfor the musl target tested in this testcase.Since this test specifically tests the default value of
crt-staticfor the musl target, ignoring it entirely makes more sense than manually setting-Ctarget-feature=+crt-statichere, but both would be valid approaches.