-
Notifications
You must be signed in to change notification settings - Fork 13.9k
compiletest: Don't set TARGET for non run-make tests
#147929
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
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
There are a few tests that were trying to skip i586 targets via the `TARGET` environment variable instead, so better to just add support for the directive.
If something like this is needed again in the future, please set environment variables for the build and run subprocesses, instead of setting them on the compiletest process.
|
Some changes occurred in src/tools/compiletest cc @jieyouxu |
rust-bors bot
added a commit
that referenced
this pull request
Oct 21, 2025
compiletest: Don't set `TARGET` for non run-make tests try-job: dist-i586-gnu-i586-i686-musl try-job: i686-gnu-1 try-job: i686-msvc-1 try-job: test-various
This comment has been minimized.
This comment has been minimized.
jieyouxu
approved these changes
Oct 21, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
@bors r+ rollup |
rust-timer
added a commit
that referenced
this pull request
Oct 21, 2025
Rollup merge of #147929 - Zalathar:target, r=jieyouxu compiletest: Don't set `TARGET` for non run-make tests There are a few tests that were using `TARGET` to quietly do nothing on `i586` targets, but it's cleaner to just add support for `//@ ignore-i586` instead. This lets us get rid of an unsafe `env::set_var` in compiletest, which really should have been setting the environment variable on individual build/run subprocess commands anyway. - The original code and tests were introduced way back in #39068
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-compiletest
Area: The compiletest test runner
A-testsuite
Area: The testsuite used to check the correctness of rustc
S-waiting-on-bors
Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
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.
There are a few tests that were using
TARGETto quietly do nothing oni586targets, but it's cleaner to just add support for//@ ignore-i586instead.This lets us get rid of an unsafe
env::set_varin compiletest, which really should have been setting the environment variable on individual build/run subprocess commands anyway.