Remove the agent_integration_tests GitLab job as it doesn’t run any useful test anymore#39772
Conversation
f5c2100 to
8b6fe4e
Compare
Gitlab CI Configuration ChangesRemoved Jobs
Changes Summary
ℹ️ Diff available in the job log. |
8b6fe4e to
f23c10b
Compare
agent_integration_tests job owneragent_integration_tests GitLab job as it doesn’t run any useful test anymore
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: dfca5e3 Optimization Goals: ✅ No significant changes detected
|
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ❌ | docker_containers_cpu | % cpu utilization | +8.96 | [+5.76, +12.17] | 1 | Logs |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ❌ | docker_containers_cpu | % cpu utilization | +8.96 | [+5.76, +12.17] | 1 | Logs |
| ➖ | quality_gate_metrics_logs | memory utilization | +0.76 | [+0.36, +1.16] | 1 | Logs bounds checks dashboard |
| ➖ | otlp_ingest_logs | memory utilization | +0.66 | [+0.53, +0.78] | 1 | Logs |
| ➖ | quality_gate_idle | memory utilization | +0.31 | [+0.27, +0.36] | 1 | Logs bounds checks dashboard |
| ➖ | quality_gate_idle_all_features | memory utilization | +0.24 | [+0.20, +0.27] | 1 | Logs bounds checks dashboard |
| ➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | +0.22 | [+0.18, +0.26] | 1 | Logs |
| ➖ | file_to_blackhole_100ms_latency | egress throughput | +0.08 | [-0.53, +0.70] | 1 | Logs |
| ➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.04 | [-0.53, +0.60] | 1 | Logs |
| ➖ | file_to_blackhole_0ms_latency | egress throughput | +0.02 | [-0.56, +0.60] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api | ingress throughput | +0.01 | [-0.29, +0.31] | 1 | Logs |
| ➖ | quality_gate_logs | % cpu utilization | +0.00 | [-2.79, +2.79] | 1 | Logs bounds checks dashboard |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.01, +0.01] | 1 | Logs |
| ➖ | file_to_blackhole_500ms_latency | egress throughput | -0.03 | [-0.65, +0.60] | 1 | Logs |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | -0.14 | [-0.21, -0.07] | 1 | Logs |
| ➖ | ddot_metrics | memory utilization | -0.16 | [-0.28, -0.05] | 1 | Logs |
| ➖ | file_tree | memory utilization | -0.21 | [-0.25, -0.17] | 1 | Logs |
| ➖ | ddot_logs | memory utilization | -0.36 | [-0.45, -0.27] | 1 | Logs |
| ➖ | otlp_ingest_metrics | memory utilization | -0.43 | [-0.57, -0.29] | 1 | Logs |
| ➖ | docker_containers_memory | memory utilization | -0.64 | [-0.68, -0.59] | 1 | Logs |
Bounds Checks: ✅ Passed
| perf | experiment | bounds_check_name | replicates_passed | links |
|---|---|---|---|---|
| ✅ | 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_1000ms_latency | 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_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_idle_all_features | memory_usage | 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 |
| ✅ | quality_gate_metrics_logs | cpu_usage | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | intake_connections | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | lost_bytes | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_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
✅ Passed. All Quality Gates passed.
- quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check lost_bytes: 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_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
|
/merge |
|
View all feedbacks in Devflow UI.
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.
devflow unqueued this merge request: It did not become mergeable within the expected time |
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
|
/merge |
|
View all feedbacks in Devflow UI.
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.
The expected merge time in
|
Remove several exclusion rules that no longer serve any purpose: - `eventContext`, `(*DatadogLogger).changeLogLevel`, `defaultRetryDuration`, `defaultRetries`: suppressed `unused` warnings for symbols that no longer exist in the codebase (or in the case of `changeLogLevel`, the method moved to a different type during a refactor). - `pem.Encode` errcheck exclusion: the file that motivated this (test/integration/utils/certificates.go) was deleted in #39772. All remaining live `pem.Encode` call sites already check or explicitly ignore the error. - `exported const APIName` revive exclusion: the constant no longer exists in `pkg/serverless/trace/inferredspan/`; the file is also already globally excluded via the paths list, making this rule doubly redundant. Also update the stale comment on the `io.WriteString` errcheck exclusion whose originating file (tools/dep_tree_resolver/go_deps.go) was deleted in #22067 — the rule is still live, covering writes to http.ResponseWriter.
### What does this PR do? Removes several dead or redundant exclusion rules from `.golangci.yml`: **Duplicate rule (cosmetic):** - Removed a duplicate `unnecessary conversion` exclusion that appeared twice. **Dead `unused` suppressions (task #10):** - `` `eventContext` is unused `` — symbol no longer exists in the codebase. - `` `(*DatadogLogger).changeLogLevel` is unused `` — `changeLogLevel` moved to `*loggerPointer` during a refactor; the original type no longer has this method. - `` `defaultRetryDuration` is unused `` — symbol no longer exists. - `` `defaultRetries` is unused `` — symbol is used; the linter wouldn't fire on it regardless. **Dead errcheck exclusion:** - `pem.Encode` — the file that motivated this (`test/integration/utils/certificates.go`) was deleted in #39772. All remaining live `pem.Encode` call sites already check or explicitly ignore the error. **Dead revive exclusion:** - `exported const APIName` — the constant no longer exists in `pkg/serverless/trace/inferredspan/`; the file is also already globally excluded via the `paths` list. **Stale comment fix:** - Updated the comment on the `io.WriteString` errcheck exclusion — its originating file (`tools/dep_tree_resolver/go_deps.go`) was deleted in #22067. The rule itself is kept as it still covers unchecked writes to `http.ResponseWriter`. ### Motivation Dead exclusions accumulate noise in the config and make it harder to reason about which rules are actively suppressing real violations. ### Describe how you validated your changes Ran `dda inv linter.go` — 0 issues. ### Additional Notes Part of a broader linter configuration cleanup pass. Co-authored-by: pierre.gimalac <pierre.gimalac@datadoghq.com>
What does this PR do?
Remove @DataDog/container-integrations from owner of integration tests found in
test/integrationand triggered in theagent_integration_testsjob.Motivation
test/integrationused to contain CircleCI tests.@DataDog/container-integrations and @DataDog/container-app have migrated all their tests to the new e2e tests framework so that all their tests have been removed from
test/integrationwith:kubeletandkube_apiserverintegration tests #34759Describe how you validated your changes
Wait for CI status…
Possible Drawbacks / Trade-offs
Additional Notes
After this cleanup PR, the only remaining directories inside
test/integrationare:test/integration/dockerwhich contains only a single file:otel_agent_build_tests.pyandtest/integration/serverlessAccording to git history, serverless teams seem to be the most active contributors on the remaining tests. Hence the update of the
CODEOWNERSfiles.