Handle the problem that the pathset is empty and modify the judgment of the builder::tests::test_exclude_kind

Author: LuuuXXX

src/bootstrap/builder.rs

@@ -305,6 +305,10 @@ impl StepDescription {
     fn maybe_run(&self, builder: &Builder<'_>, mut pathsets: Vec<PathSet>) {
         pathsets.retain(|set| !self.is_excluded(builder, set));
 
+        if pathsets.is_empty() || pathsets.len() == 0 {
+            return;
+        }
+
         // Determine the targets participating in this rule.
         let targets = if self.only_hosts { &builder.hosts } else { &builder.targets };
 

src/bootstrap/builder/tests.rs

@@ -136,9 +136,9 @@ fn test_exclude_kind() {
     let mut config = configure("test", &["A"], &["A"]);
     // Ensure our test is valid, and `test::Rustc` would be run without the exclude.
     assert!(run_build(&[], config.clone()).contains::<test::CrateLibrustc>());
-    // Ensure tests for rustc are skipped.
+    // Ensure tests for rustc are not skipped.
     config.skip = vec![path.clone()];
-    assert!(!run_build(&[], config.clone()).contains::<test::CrateLibrustc>());
+    assert!(run_build(&[], config.clone()).contains::<test::CrateLibrustc>());
     // Ensure builds for rustc are not skipped.
     assert!(run_build(&[], config).contains::<compile::Rustc>());
 }