|
|
|
|
|
|
by pm215
3298 days ago
|
|
|
IME the problem with applying rr to a flaky test is that it's not uncommon that rr will just reliably and deterinistically cause the test to not fail. This is especially true for failures due to multithreading bugs and similar race conditions, where they can easily just not manifest under rr's deterministic thread scheduler. So if you always run your tests under rr your flakiness problem may go away but the underlying bug causing it hasn't... rr's pretty great for a lot of purposes though -- I think the clearest use case for it is the "memory corruption happens but doesn't get noticed until execution has progressed a long way forward from the actual site of the bug" kind of problem, which it can speed up debugging of massively. |
|
|
If you figure out the cause of a bug that rr chaos mode was not able to reproduce, please file an rr issue and explain the situation. We've generally been able to improve chaos mode to find hitherto non-reproducible bugs.