-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Bump github.com/DataDog/datadog-api-client-go/v2 from 2.38.0 to 2.42.0 in /test/new-e2e #38347
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
base: main
Are you sure you want to change the base?
Conversation
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: fd52a57 Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | docker_containers_memory | memory utilization | +1.21 | [+1.13, +1.29] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +0.81 | [-0.02, +1.65] | 1 | Logs |
➖ | quality_gate_logs | % cpu utilization | +0.69 | [-2.10, +3.49] | 1 | Logs bounds checks dashboard |
➖ | otlp_ingest_logs | memory utilization | +0.38 | [+0.25, +0.50] | 1 | Logs |
➖ | otlp_ingest_metrics | memory utilization | +0.34 | [+0.20, +0.48] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | +0.27 | [+0.21, +0.33] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | +0.25 | [+0.18, +0.33] | 1 | Logs bounds checks dashboard |
➖ | ddot_logs | memory utilization | +0.21 | [+0.12, +0.30] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | +0.12 | [-0.50, +0.73] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | +0.09 | [-0.53, +0.70] | 1 | Logs |
➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | +0.06 | [+0.01, +0.11] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | +0.02 | [-0.56, +0.60] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.02, +0.01] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | -0.00 | [-0.57, +0.57] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | -0.01 | [-0.25, +0.23] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.01 | [-0.61, +0.60] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.01 | [-0.31, +0.28] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | -0.03 | [-0.61, +0.55] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | -0.12 | [-0.67, +0.44] | 1 | Logs |
➖ | ddot_metrics | memory utilization | -0.31 | [-0.43, -0.19] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | -0.42 | [-0.50, -0.34] | 1 | Logs bounds checks dashboard |
➖ | file_tree | memory utilization | -0.98 | [-1.12, -0.85] | 1 | Logs |
➖ | docker_containers_cpu | % cpu utilization | -3.84 | [-6.85, -0.84] | 1 | Logs |
Bounds Checks: ❌ Failed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
❌ | quality_gate_idle_all_features | memory_usage | 9/10 | bounds checks dashboard |
✅ | docker_containers_cpu | simple_check_run | 10/10 | |
✅ | docker_containers_memory | memory_usage | 10/10 | |
✅ | docker_containers_memory | simple_check_run | 10/10 | |
✅ | file_to_blackhole_0ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency_linear_load | memory_usage | 10/10 | |
✅ | file_to_blackhole_100ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_300ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_300ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_500ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_500ms_latency | memory_usage | 10/10 | |
✅ | quality_gate_idle | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | lost_bytes | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | memory_usage | 10/10 | bounds checks dashboard |
Explanation
Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%
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
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".
CI Pass/Fail Decision
❌ Failed. Some Quality Gates were violated.
- quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check memory_usage: 9/10 replicas passed. Failed 1 which is > 0. Gate FAILED.
- quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
8985eba
to
979c1ed
Compare
Bumps [github.com/DataDog/datadog-api-client-go/v2](https://github.com/DataDog/datadog-api-client-go) from 2.38.0 to 2.42.0. - [Release notes](https://github.com/DataDog/datadog-api-client-go/releases) - [Changelog](https://github.com/DataDog/datadog-api-client-go/blob/master/CHANGELOG.md) - [Commits](DataDog/datadog-api-client-go@v2.38.0...v2.42.0) --- updated-dependencies: - dependency-name: github.com/DataDog/datadog-api-client-go/v2 dependency-version: 2.42.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
e0fc2d1
to
1153add
Compare
This commit was created from the local commit with hash 649209311b648aabddcbac4867e03aa23c1a73cc.
Bumps github.com/DataDog/datadog-api-client-go/v2 from 2.38.0 to 2.42.0.
Release notes
Sourced from github.com/DataDog/datadog-api-client-go/v2's releases.
Changelog
Sourced from github.com/DataDog/datadog-api-client-go/v2's changelog.
... (truncated)
Commits
fe955e0
Bump versions and add changelog entries. (#3189)7f5716e
Regenerate client from commit be63084a of spec repo (#3182)413fb07
Regenerate client from commit 76086f13 of spec repo (#3181)4b030d1
Regenerate client from commit c051b78b of spec repo (#3170)2a13386
Regenerate client from commit 31044eb9 of spec repo (#3176)d32a82b
Regenerate client from commit 51c1745 of spec repo (#3177)4b16e31
Regenerate client from commit 0ec5a2f3 of spec repo (#3178)7d26bbb
Regenerate client from commit 949f90e2 of spec repo (#3137)7d84218
Regenerate client from commit 5d86661b of spec repo (#3166)ac087a6
Regenerate client from commit 8772660e of spec repo (#3110)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)