Skip to content

compiletest: Deny usage of special FileCheck suffixes as revision names #134925

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.

Sign up for GitHub

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 2 commits into from
Jan 5, 2025
Merged

compiletest: Deny usage of special FileCheck suffixes as revision names #134925

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
891041f
deny usage of FileCheck prefixes as revision names
DavisRayM Dec 30, 2024
4a5e76a
limit special `FileCheck` revision checks
DavisRayM Jan 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions src/tools/compiletest/src/header.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -934,6 +934,9 @@ fn iter_header(

impl Config {
fn parse_and_update_revisions(&self, testfile: &Path, line: &str, existing: &mut Vec<String>) {
const FORBIDDEN_REVISION_NAMES: [&str; 9] =
["CHECK", "COM", "NEXT", "SAME", "EMPTY", "NOT", "COUNT", "DAG", "LABEL"];

if let Some(raw) = self.parse_name_value_directive(line, "revisions") {
if self.mode == Mode::RunMake {
panic!("`run-make` tests do not support revisions: {}", testfile.display());
Expand All @@ -948,6 +951,13 @@ impl Config {
raw,
testfile.display()
);
} else if FORBIDDEN_REVISION_NAMES.contains(&revision.as_str()) {
panic!(
"invalid revision: `{}` in line `{}`: {}",
revision,
raw,
testfile.display()
);
}
existing.push(revision);
}
Expand Down
15 changes: 15 additions & 0 deletions src/tools/compiletest/src/header/tests.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -553,6 +553,21 @@ fn test_duplicate_revisions() {
parse_rs(&config, "//@ revisions: rpass1 rpass1");
}

#[test]
Copy link
Member

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.

Copy link
Contributor Author

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

Copy link
Member

@jieyouxu jieyouxu Jan 4, 2025 •
edited
Loading

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.

fn test_forbidden_revisions() {
let config: Config = cfg().build();
let revisions = ["CHECK", "COM", "NEXT", "SAME", "EMPTY", "NOT", "COUNT", "DAG", "LABEL"];
for rev in revisions {
let res = std::panic::catch_unwind(|| {
parse_rs(&config, format!("//@ revisions: {rev}").as_str());
});
assert!(res.is_err());
if let Some(msg) = res.unwrap_err().downcast_ref::<String>() {
assert!(msg.contains(format!("invalid revision: `{rev}` in line ` {rev}`").as_str()))
}
}
}

#[test]
fn ignore_arch() {
let archs = [
Expand Down
Loading