-
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-infra-definitions][automated] Bump test-infra-definitions to d9c99212063b3aba38bc6bcd96ab3d74644c9492 #30225
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM as long as the CI passes !
[Fast Unit Tests Report] On pipeline 46914097 (CI Visibility). The following jobs did not run any unit tests: Jobs:
If you modified Go files and expected unit tests to run in these jobs, please double check the job logs. If you think tests should have been executed reach out to #agent-devx-help |
Test changes on VMUse this command from test-infra-definitions to manually test this PR changes on a VM: inv create-vm --pipeline-id=46914097 --os-family=ubuntu Note: This applies to commit 7cad58d |
Regression DetectorRegression Detector ResultsRun ID: 6a9e2b10-e2af-44b6-abb7-9d45e47ade62 Metrics dashboard Target profiles Baseline: a7a1121 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 | trials | links |
---|---|---|---|---|---|---|
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +0.79 | [+0.06, +1.53] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | +0.26 | [+0.21, +0.31] | 1 | Logs |
➖ | idle_all_features | memory utilization | +0.21 | [+0.12, +0.29] | 1 | Logs bounds checks dashboard |
➖ | file_to_blackhole_0ms_latency | egress throughput | +0.02 | [-0.31, +0.35] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | +0.01 | [-0.21, +0.24] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | +0.00 | [-0.11, +0.12] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.01, +0.01] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | -0.03 | [-0.21, +0.16] | 1 | Logs |
➖ | idle | memory utilization | -0.05 | [-0.10, -0.00] | 1 | Logs bounds checks dashboard |
➖ | file_tree | memory utilization | -0.09 | [-0.22, +0.04] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | -0.11 | [-0.36, +0.13] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.38 | [-0.86, +0.10] | 1 | Logs |
➖ | basic_py_check | % cpu utilization | -0.45 | [-3.27, +2.37] | 1 | Logs |
➖ | otel_to_otel_logs | ingress throughput | -0.56 | [-1.37, +0.25] | 1 | Logs |
➖ | pycheck_lots_of_tags | % cpu utilization | -1.69 | [-4.19, +0.81] | 1 | Logs |
Bounds Checks
perf | experiment | bounds_check_name | replicates_passed |
---|---|---|---|
✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 |
✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 |
✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 |
✅ | file_to_blackhole_300ms_latency | memory_usage | 10/10 |
✅ | file_to_blackhole_500ms_latency | memory_usage | 10/10 |
✅ | idle | memory_usage | 10/10 |
✅ | idle_all_features | memory_usage | 10/10 |
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".
/merge |
🚂 MergeQueue: waiting for PR to be ready This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals. Use |
🚂 MergeQueue: pull request added to the queue The median merge time in Use |
This PR was automatically created by the test-infra-definitions bump task.
This PR bumps the test-infra-definitions submodule to d9c99212063b3aba38bc6bcd96ab3d74644c9492 from f694c4dc33e4.
Here is the full changelog between the two commits: DataDog/test-infra-definitions@f694c4d...15203a0
qa/no-code-change
andchangelog/no-changelog
labels by default. Please make sure this is appropriate