datadog-agent
datadog-agent copied to clipboard
upgrade test-infra-definitions version in go.mod
What does this PR do?
update upgrade test-infra-definitions version in go.mod
Motivation
Benefit from the fix done in this PR.
Additional Notes
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes
Bloop Bleep... Dogbot Here
Regression Detector Results
Run ID: ea8fe87e-83d7-44cd-84a4-98bbdf1ea536 Baseline: d3c07fce4a0dc7eea2a79b9dd168c73c718f4cba Comparison: 36e39095a79844ed82caea521d90f82682c3d9db Total CPUs: 7
Performance changes are noted in the perf column of each table:
- ✅ = significantly better comparison variant performance
- ❌ = significantly worse comparison variant performance
- ➖ = no significant change in performance
No significant changes in experiment optimization goals
Confidence level: 90.00% Effect size tolerance: |Δ mean %| ≥ 5.00%
There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
Experiments ignored for regressions
Regressions in experiments with settings containing erratic: true
are ignored.
perf | experiment | goal | Δ mean % | Δ mean % CI |
---|---|---|---|---|
➖ | file_to_blackhole | % cpu utilization | +0.15 | [-6.42, +6.71] |
Fine details of change detection per experiment
perf | experiment | goal | Δ mean % | Δ mean % CI |
---|---|---|---|---|
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +0.33 | [-1.09, +1.76] |
➖ | idle | memory utilization | +0.27 | [+0.24, +0.31] |
➖ | process_agent_standard_check_with_stats | memory utilization | +0.25 | [+0.21, +0.28] |
➖ | file_to_blackhole | % cpu utilization | +0.15 | [-6.42, +6.71] |
➖ | process_agent_standard_check | memory utilization | +0.08 | [+0.05, +0.12] |
➖ | trace_agent_json | ingress throughput | +0.02 | [-0.00, +0.03] |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.00, +0.00] |
➖ | uds_dogstatsd_to_api | ingress throughput | +0.00 | [-0.00, +0.00] |
➖ | trace_agent_msgpack | ingress throughput | -0.01 | [-0.02, -0.00] |
➖ | process_agent_real_time_mode | memory utilization | -0.09 | [-0.12, -0.06] |
➖ | otel_to_otel_logs | ingress throughput | -0.11 | [-0.69, +0.48] |
➖ | file_tree | memory utilization | -0.11 | [-0.18, -0.04] |
➖ | tcp_syslog_to_blackhole | ingress throughput | -0.54 | [-0.60, -0.49] |
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".
closing in favour of this PR.