-
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
Update release.json and Go modules for 7.55.2-rc.1 #27785
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## 7.55.x #27785 +/- ##
==========================================
- Coverage 45.08% 44.94% -0.14%
==========================================
Files 2354 2354
Lines 272910 272910
==========================================
- Hits 123033 122662 -371
- Misses 140163 140576 +413
+ Partials 9714 9672 -42
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Regression DetectorRegression Detector ResultsRun ID: c3ce9dc6-543b-4bce-bcca-fa18eb5291b6 Baseline: 51e67a8 Performance changes are noted in the perf column of each table:
No significant changes in experiment optimization goalsConfidence level: 90.00% There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
|
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
➖ | pycheck_1000_100byte_tags | % cpu utilization | +2.52 | [-2.39, +7.42] | |
➖ | file_tree | memory utilization | +1.53 | [+1.42, +1.64] | |
➖ | basic_py_check | % cpu utilization | +0.56 | [-2.02, +3.13] | |
➖ | idle | memory utilization | +0.26 | [+0.20, +0.31] | |
➖ | trace_agent_msgpack | ingress throughput | +0.00 | [-0.00, +0.00] | |
➖ | trace_agent_json | ingress throughput | -0.00 | [-0.01, +0.01] | |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.00 | [-0.20, +0.20] | |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.01 | [-0.05, +0.03] | |
➖ | otel_to_otel_logs | ingress throughput | -0.06 | [-0.42, +0.30] | |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -0.34 | [-3.20, +2.52] | |
➖ | tcp_syslog_to_blackhole | ingress throughput | -6.80 | [-27.16, +13.56] |
Explanation
A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".
For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.
-
Its configuration does not mark it "erratic".
What does this PR do?
Update release.json and Go modules for 7.55.2-rc.1
Motivation
Additional Notes
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes