Since upgrading to Rust 1.86.0, I’ve noticed that running a single test in RustRover triggers a full rebuild of all dependencies, taking about a minute each time. This has significantly slowed down my development workflow.
It honestly reminds me of the old Java days—sipping coffee while waiting for Tomcat to restart.
I had to downgrade to Rust 1.85.1 using rustup default 1.85.1 just to get back the fast, incremental builds.
I’m currently on macOS 15.4, using RustRover 2024.3.7 and 2025.1.
Has anyone else experienced this? Any better workarounds?
From the discussion in the ticket, we should have a fix in 2025.1.1 and 2024.3.8 (I advise to skip 2025.1 for now anyway).
it is scheduled to be addressed in the upcoming 2025.1.1 release.
This fix was included in RustRover 2024.3.8; however, multiple issues were introduced, and we decided to roll back this update. We will add an explanation to RustRover 2024.3.8 release notes to prevent further misunderstandings.
@debug and @boying52 Version 2025.1.1 has just been released, and it's supposed to fix that bug (which, according to another user, doesn't happen in debug mode):