-
Notifications
You must be signed in to change notification settings - Fork 13.3k
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
compiletest: Deny usage of special FileCheck suffixes as revision names #134925
compiletest: Deny usage of special FileCheck suffixes as revision names #134925
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @oli-obk (or someone else) some time within the next two weeks. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
Some changes occurred in src/tools/compiletest cc @jieyouxu |
45542b6
to
0117c97
Compare
0117c97
to
891041f
Compare
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.
Thanks for the PR. I left some initial feedback.
@@ -553,6 +553,21 @@ fn test_duplicate_revisions() { | |||
parse_rs(&config, "//@ revisions: rpass1 rpass1"); | |||
} | |||
|
|||
#[test] |
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.
Suggestion: just #[should_panic]
here instead of trying to catch the panic.
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.
Changed in the latest commit. I had to select a specific revision name for this CHECK
, I'm not currently aware of a way to test all of them without manually catching the panic... Any tips on this will be greatly appreciated
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.
In the long run compiletest shouldn't be using randomly placed panics as an error handling strategy (really, the lack thereof), but in the short run this is reasonable.
I think it's a reasonable compromise for the time being.
r? jieyouxu |
@rustbot author |
2103a5a
to
4a5e76a
Compare
@rustbot ready |
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.
Thanks!
@bors r+ rollup |
…kingjubilee Rollup of 4 pull requests Successful merges: - rust-lang#134925 (deny usage of special FileCheck prefixes as revision names) - rust-lang#134996 (Add UWP (msvc) target support page) - rust-lang#135104 (do not in-place-iterate over flatmap/flatten) - rust-lang#135110 (library: fix adler{ -> 2}.debug) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#134925 - DavisRayM:130982-deny-special-filecheck-prefixes, r=jieyouxu deny usage of special FileCheck prefixes as revision names Adds a check that ensures special FileCheck prefixes are not used as revision names. Fix rust-lang#130982
@bors retry r- |
Adds a check that ensures special FileCheck suffixes are not used as revision names.
Fix #130982