-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[test/performance] round computed rate in real-traffic-test #15641
[test/performance] round computed rate in real-traffic-test #15641
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #15641 +/- ##
=======================================
Coverage 83.53% 83.53%
=======================================
Files 219 219
Lines 17427 17427
=======================================
Hits 14558 14558
+ Misses 2498 2496 -2
- Partials 371 373 +2 ☔ View full report in Codecov by Sentry. |
/test ? |
@skonto: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/test performance-tests |
Din't pass the first SLA. :(
|
/test performance-tests |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: maschmid, skonto The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@maschmid hi, this still fails:
Not sure if we can verify it here. Could you take a look on this one too? Btw I will stamp it based on the other test. |
Trying to see if #15654 helps with the SLA 1 |
included in #15654 |
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.