Skip to content

./x.py test --host='' does nothing and succeeds #77906

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

Closed
jonas-schievink opened this issue Oct 13, 2020 · 5 comments
Closed

./x.py test --host='' does nothing and succeeds #77906

jonas-schievink opened this issue Oct 13, 2020 · 5 comments
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc C-bug Category: This is a bug. E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue. E-mentor Call for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)

Comments

@jonas-schievink
Copy link
Contributor

jonas-schievink commented Oct 13, 2020

Running ./x.py test --host='' builds bootstrap, but then exits successfully without building Rust and running any test. This should probably cause an error instead.

cc @Mark-Simulacrum

@jonas-schievink jonas-schievink added T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) C-bug Category: This is a bug. labels Oct 13, 2020
@jyn514 jyn514 added the A-testsuite Area: The testsuite used to check the correctness of rustc label Oct 13, 2020
@jyn514
Copy link
Member

jyn514 commented Feb 3, 2023

Here's the relevant code:

// Determine the targets participating in this rule.
let targets = if self.only_hosts { &builder.hosts } else { &builder.targets };
for target in targets {
let run = RunConfig { builder, paths: pathsets.clone(), target: *target };
(self.make_run)(run);
}

We should probably have an assert!(!targets.is_empty()) there or something (not an assert because of #107019, but something like it).

@jyn514 jyn514 added E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue. E-mentor Call for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion. labels Feb 3, 2023
@madsravn
Copy link
Contributor

madsravn commented Feb 3, 2023

@rustbot claim

@madsravn
Copy link
Contributor

@rustbot release-assignment

@AleksaBajat
Copy link

Hey @Mark-Simulacrum,
Is this issue still something that needs to be worked on? I noticed in the previous PR discussion that this might not require a change. However, if we still want to address this issue, I can review flags.rs and other mentioned code and attempt to make a more appropriate fix.

@Mark-Simulacrum
Copy link
Member

I'm going to go ahead and close this. I don't think it's critical that every invocation that is mostly a no-op errors. If you request an empty set, getting an empty set seems fine.

@Mark-Simulacrum Mark-Simulacrum closed this as not planned Won't fix, can't repro, duplicate, stale Jul 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc C-bug Category: This is a bug. E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue. E-mentor Call for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants