On Tue, Feb 05, 2019 at 10:45:35AM -0800, Junio C Hamano wrote: > - Perhaps find the fork point, run tests to find known breakages > and exclude them? This would simply be not practical, as it > doubles the number of tests run, for individual topic branches > because there are an order of magnitude more of them than the > primary integration branches. I think this can be limited to the tests that failed, which makes things much faster. I.e., we run the tests at the tip of topic X and see that t1234 fails. We then go back to the fork point and we just need to run t1234 again. If it succeeds, then we blame X for the failure. If it fails, then we consider it a false positive. You do pay the price to do a full build at the fork point, but in my experience that is much quicker than the tests. -Peff
