Fix tests and doclink

Author: Kobzol

src/bootstrap/src/core/builder/tests.rs

@@ -1856,12 +1856,14 @@ mod snapshot {
         let ctx = TestCtx::new();
         insta::assert_snapshot!(
             ctx.config("test")
-                // Skip bootstrap tests, as for some reason the recursive nature of running
-                // bootstrap tests under bootstrap tests causes non-deterministic snapshot diffs
-                // on CI.
-                .args(&["--skip", "bootstrap"])
-                // rustdoc-js-std requires nodejs to be present
-                .args(&["--set", "build.nodejs=/bin/nodejs"])
+                // Bootstrap only run by default on CI, so we have to emulate that also locally.
+                .args(&["--ci", "true"])
+                // These rustdoc tests requires nodejs to be present.
+                // We can't easily opt out of it, so if it is present on the local PC, the test
+                // would have different result on CI, where nodejs might be missing.
+                .args(&["--set", "rustdoc-js-std"])
+                .args(&["--set", "rustdoc-js"])
+                .args(&["--set", "rustdoc-gui"])
                 .render_steps(), @r"
         [build] rustc 0 <host> -> Tidy 1 <host>
         [test] tidy <>

src/bootstrap/src/lib.rs

@@ -1151,7 +1151,7 @@ impl Build {
 
     /// Return a `Group` guard for a [`Step`] that tests `what` with the given `stage` and `target`
     /// (determined by `host_and_stage`).
-    /// Use this instead of [`builder::Builder::msg`] when there is no clear `build_compiler` to be
+    /// Use this instead of [`Build::msg`] when there is no clear `build_compiler` to be
     /// determined.
     ///
     /// [`Step`]: crate::core::builder::Step