[test/performance] round computed rate in real-traffic-test #15641
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
real-traffic-test benchmark SLA 2 fails frequently just because the computed rate is not exactly the expected value , e.g. https://prow.knative.dev/view/gs/knative-prow/logs/performance-tests_serving_main_periodic/1862287597506662400
Let's do the same here as we already to in https://github.com/knative/serving/blob/main/test/performance/benchmarks/rollout-probe/main.go#L234 , and add tolerance to the rate comparison to fit within the nearest integer.