da-viper wrote: >My intention here is that a big timeout can cause problems on CI when flaky >tests are failed (e.g. waiting for events)
The goal is to make the test no longer flaky, IMO if there is a wait for event longer than 50 seconds there is something else wrong with the test than the timeout itself. > Maybe we can do it only for mentioned tests. I noticed this timeouts on a stressed `M4 pro` which is quite a fast machine. so I assume no not so fast machines the issue is more prevalent. This could be higher on windows as the windows defender normally scans new binaries. the unified timeouts was completed [here](https://github.com/llvm/llvm-project/commit/25c62bca9bc671ae5ce18a79fdef8d6e948c1064) https://github.com/llvm/llvm-project/pull/170890 _______________________________________________ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
