One feature I've added to my own generative testing tool [1] to mitigate this problem is to save the random value that made the test fail and add it to a set of deterministic test cases that always need to pass before the tool will try any new randomized cases.
Of course, if you discover a test failure on a very low-probability corner case, other people working on their own branches probably won't trigger it. But with the right workflow, the situation shouldn't be all that different from adding a regular test case, which could always fail once attempt you merge it with someone else's code that wasn't written against it.
Of course, if you discover a test failure on a very low-probability corner case, other people working on their own branches probably won't trigger it. But with the right workflow, the situation shouldn't be all that different from adding a regular test case, which could always fail once attempt you merge it with someone else's code that wasn't written against it.
[1] https://github.com/DalekBaldwin/check-it