How to disable "has been running for over 60 seconds"?

mikhail-modin · July 17, 2025, 11:06pm

I have some tests, which run definitely more then 60 sec. I don't need that message. How I can disable it?

nerditation · July 17, 2025, 11:56pm

this warning cannot be suppressed. see:

github.com/rust-lang/rust

RUST_TEST_TIME_INTEGRATION and RUST_TEST_TIME_UNIT ignored

opened 03:25AM - 20 Sep 23 UTC

closed 04:22PM - 08 Oct 23 UTC

peter-lyons-kehl

C-bug

The below defected/unimplemented feature is NOT documented in Cargo book, but it…'s in the public & documented interface of `library/test/src/time.rs` and its submodule `time_constants` (even though it may be accessible from Rust tools only). `https://github.com/rust-lang/rust/blob/41bafc4ff3eb6a73aa40e60c3bd4494302c7ec57/library/test/src/time.rs#L31C38-L31C57 and https://github.com/rust-lang/rust/blob/41bafc4ff3eb6a73aa40e60c3bd4494302c7ec57/library/test/src/time.rs#L38C45-L38C71 suggest that unit tests use `RUST_TEST_TIME_UNIT`, and integration tests use `RUST_TEST_TIME_INTEGRATION` (despite a 2x copy-and-paste mistake of mentioning "threshold for unit-tests" for integration and doc tests). However, neither `RUST_TEST_TIME_UNIT` nor `RUST_TEST_TIME_INTEGRATION` seems to have any effect. As per https://github.com/rust-lang/rust/blob/41bafc4ff3eb6a73aa40e60c3bd4494302c7ec57/library/test/src/time.rs#L106 `from_env_var(&str)`: With https://github.com/peter-kehl/test_timeout_rs: ```bash export RUST_TEST_TIME_UNIT=3600000,3600000 export RUST_TEST_TIME_INTEGRATION=3600000,3600000 git clone https://github.com/peter-kehl/test_timeout_rs cd test_timeout_rs cargo test Compiling test_timeout_rs v0.1.0 (/share/pkehl/GIT/test_timeout_rs) Finished test [unoptimized + debuginfo] target(s) in 0.45s Running unittests src/lib.rs (target/debug/deps/test_timeout_rs-ccebbdfa21928176) running 1 test test unit_test::long_unit_test has been running for over 60 seconds test unit_test::long_unit_test ... ok test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 62.00s Running tests/integration.rs (target/debug/deps/integration-f2beccbd60895674) running 1 test test long_unit_test has been running for over 60 seconds test long_unit_test ... ok test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 62.00s Doc-tests test_timeout_rs running 0 tests test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s ``` - `cargo test` still reports "test ... has been running for over 60 seconds" - for both unit tests and integration tests. ``` rustc --version --verbose rustc 1.74.0-nightly (b4e54c6e3 2023-09-11) binary: rustc commit-hash: b4e54c6e39984840a04dcd02d14ec8c3574d30e5 commit-date: 2023-09-11 host: x86_64-unknown-linux-gnu release: 1.74.0-nightly LLVM version: 17.0.0 ```

system · October 15, 2025, 11:57pm

This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.

Topic		Replies	Views
Integration test times out while debugging help	9	3326	January 6, 2020
Profiling your test suite? help	4	479	June 24, 2022
Limit execution time of test? help	7	8003	January 12, 2023
[Solved] Run "cargo test" 1_000_000 times	7	2447	January 12, 2023
How to make a test optional in cargo? help	5	1282	April 5, 2025

How to disable "has been running for over 60 seconds"?

Related topics