about summary refs log tree commit diff
diff options
context:
space:
mode:
authorbinarycat <binarycat@envs.net>2025-01-11 14:00:16 -0600
committerbinarycat <binarycat@envs.net>2025-01-11 14:00:16 -0600
commitaf2247ce10bbe701714a19908ea0c6c957ae59e1 (patch)
tree0bf70d700d60f7a1404220683ab57208f4d2eafd
parent251206c27b619ccf3a08e2ac4c525dc343f08492 (diff)
downloadrust-af2247ce10bbe701714a19908ea0c6c957ae59e1.tar.gz
rust-af2247ce10bbe701714a19908ea0c6c957ae59e1.zip
allow rustdoc-js tests to be run at stage0
this mirrors the behavior of rustdoc-js-std tests.

previously this required COMPILETEST_FORCE_STAGE0.
-rw-r--r--src/bootstrap/src/core/build_steps/test.rs5
1 files changed, 4 insertions, 1 deletions
diff --git a/src/bootstrap/src/core/build_steps/test.rs b/src/bootstrap/src/core/build_steps/test.rs
index 914260e38d1..2632719f7c9 100644
--- a/src/bootstrap/src/core/build_steps/test.rs
+++ b/src/bootstrap/src/core/build_steps/test.rs
@@ -1637,7 +1637,10 @@ impl Step for Compiletest {
             return;
         }
 
-        if builder.top_stage == 0 && env::var("COMPILETEST_FORCE_STAGE0").is_err() {
+        if builder.top_stage == 0
+            && env::var("COMPILETEST_FORCE_STAGE0").is_err()
+            && self.mode != "js-doc-test"
+        {
             eprintln!("\
 ERROR: `--stage 0` runs compiletest on the beta compiler, not your local changes, and will almost always cause tests to fail
 HELP: to test the compiler, use `--stage 1` instead