RUST: Casper tests log restrictions

[NazarY-DevBrother]

We have an issue with log overload.
The problem is that when we run the tests under Casper, we see thousands of logs that aren’t related to the tests themselves. This behavior appeared after we completely updated the crate for logging (check details with @YuriiO-DevBrother )

The entry point for the Casper tests is the file → casper/tests/mod.rs.

Lowering the log level from Debug to Info only partially helped, but as a result, we still have hundreds of logs that aren’t related to the tests.

Logs example:
{"timestamp":"2025-11-26T17:47:29.167811Z","level":"INFO","message":"PreCharging 04f700a417754b775d95421973bdbdadb2d23c8a5af46f1829b1431f5c136e549e8a0d61aa0c793f1a614f8e437711c7758473c6ceb0859ac7e9e07911ca66b5c4 for 90000"} {"timestamp":"2025-11-26T17:47:29.340434Z","level":"INFO","message":"Processing user deploy 04f700a417754b775d95421973bdbdadb2d23c8a5af46f1829b1431f5c136e549e8a0d61aa0c793f1a614f8e437711c7758473c6ceb0859ac7e9e07911ca66b5c4"} {"timestamp":"2025-11-26T17:47:29.349617Z","level":"INFO","message":"Refunding 04f700a417754b775d95421973bdbdadb2d23c8a5af46f1829b1431f5c136e549e8a0d61aa0c793f1a614f8e437711c7758473c6ceb0859ac7e9e07911ca66b5c4 with 88858"} {"timestamp":"2025-11-26T17:47:29.481689Z","level":"INFO","message":"PreCharging 04f700a417754b775d95421973bdbdadb2d23c8a5af46f1829b1431f5c136e549e8a0d61aa0c793f1a614f8e437711c7758473c6ceb0859ac7e9e07911ca66b5c4 for 90000"} {"timestamp":"2025-11-26T17:47:29.634305Z","level":"INFO","message":"Processing user deploy 04f700a417754b775d95421973bdbdadb2d23c8a5af46f1829b1431f5c136e549e8a0d61aa0c793f1a614f8e437711c7758473c6ceb0859ac7e9e07911ca66b5c4"} {"timestamp":"2025-11-26T17:47:29.643522Z","level":"INFO","message":"Refunding 04f700a417754b775d95421973bdbdadb2d23c8a5af46f1829b1431f5c136e549e8a0d61aa0c793f1a614f8e437711c7758473c6ceb0859ac7e9e07911ca66b5c4 with 89086"} {"timestamp":"2025-11-26T17:47:29.764499Z","level":"INFO","message":"PreCharging 04f700a417754b775d95421973bdbdadb2d23c8a5af46f1829b1431f5c136e549e8a0d61aa0c793f1a614f8e437711c7758473c6ceb0859ac7e9e07911ca66b5c4 for 90000"} {"timestamp":"2025-11-26T17:47:29.913595Z","level":"INFO","message":"Processing user deploy 04f700a417754b775d95421973bdbdadb2d23c8a5af46f1829b1431f5c136e549e8a0d61aa0c793f1a614f8e437711c7758473c6ceb0859ac7e9e07911ca66b5c4"} {"timestamp":"2025-11-26T17:47:29.925032Z","level":"INFO","message":"Refunding 04f700a417754b775d95421973bdbdadb2d23c8a5af46f1829b1431f5c136e549e8a0d61aa0c793f1a614f8e437711c7758473c6ceb0859ac7e9e07911ca66b5c4 with 89140"}

We need to investigate how to exclude these logs, or at least reduce their presence, since they’re currently printed forcibly (they don’t pertain to the tests). As a result, these logs heavily pollute the CI, and our CI job simply can’t display errors when tests fail because everything is clogged with logs.

[linear]

F1R-97

[NazarY-DevBrother]

The best solution would be to limit the logging level to Error. As an alternative, we can exclude logging from the Casper runtime:
let filter = EnvFilter::builder() .with_default_directive(LevelFilter::OFF.into()) .parse("casper::tests=debug") // Тільки логи від самих тестів .unwrap();

However, for now, I’ve just raised the level to Error for Casper tests.