Rerun distributed performance test in RERUNNER step (#8801) After the improvement of automatically rerunning and tagging, we want to manage performance test in the same way:
- Only run each performance test scenario once. - If it fails, `GRADLE_RERUNNER` will kick in and rerun the failed scenario. The good thing is that it might be scheduled to another build agent, which mitigates the effect of bad agent.
This PR does: - Remove all `Retry` from performance tests. - Add `GRADLE_RERUNNER` to performance tests and refactor some code. - Add tests for `PerformanceTest`. - Since `GRADLE_RERUNNER` depends on reading of test binary result, write binary test result file in `RerunableDistributedPerformanceTest`.
Fix cache-hit in flakiness detection performance test (#8482) We don't want build cache hit in performance flakiness detection, however, previously the coordinator build resolves "flakiness-detection-commit" baseline to real commit id "5.3-commit-237a600", resulting in unexpected cache hit.
This PR fixes it by:
- On coordinator's side, pass "flakiness-detection-commit" as it is to worker build. - On worker's side, worker build resolves "flakiness-detection-commit" to real commit version - this disables build cache.
Since `DetermineBaselines` is becoming more and more complex, this PR also adds a unit test for `DetermineBaselines` class.