fix(fleet): Mark TestInstallParity as flaky

[BaptisteFoy]

What does this PR do?

Marks TestInstallParity as flaky

Motivation

Describe how you validated your changes

Possible Drawbacks / Trade-offs

Additional Notes

[BaptisteFoy]

/merge

[dd-devflow]

Devflow running: /merge

View all feedbacks in Devflow UI.

---

2025-01-29 17:12:24 UTC ℹ️ 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.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

---

2025-01-29 18:05:12 UTC ℹ️ MergeQueue: merge request added to the queue

The median merge time in main is 27m.

---

2025-01-29 18:28:34 UTC ℹ️ MergeQueue: This merge request was merged

[agent-platform-auto-pr]

[Fast Unit Tests Report]

On pipeline 54351066 (CI Visibility). The following jobs did not run any unit tests:

Jobs:

• tests_deb-arm64-py3
• tests_deb-x64-py3
• tests_flavor_dogstatsd_deb-x64
• tests_flavor_heroku_deb-x64
• tests_flavor_iot_deb-x64
• tests_rpm-arm64-py3
• tests_rpm-x64-py3
• tests_windows-x64

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

[agent-platform-auto-pr]

Test changes on VM

Use this command from test-infra-definitions to manually test this PR changes on a VM:

inv aws.create-vm --pipeline-id=54351066 --os-family=ubuntu

Note: This applies to commit d2f3116

[agent-platform-auto-pr]

Uncompressed package size comparison

Comparison with ancestor 3728d5a4abbb31f074fcce7953739502811991ae

Diff per package

package	diff	status	size	ancestor	threshold
datadog-agent-amd64-deb	0.00MB	✅	911.85MB	911.85MB	0.50MB
datadog-agent-x86_64-rpm	0.00MB	✅	921.59MB	921.59MB	0.50MB
datadog-agent-x86_64-suse	0.00MB	✅	921.59MB	921.59MB	0.50MB
datadog-agent-arm64-deb	0.00MB	✅	899.25MB	899.25MB	0.50MB
datadog-agent-aarch64-rpm	0.00MB	✅	908.97MB	908.97MB	0.50MB
datadog-dogstatsd-amd64-deb	0.00MB	✅	59.01MB	59.01MB	0.50MB
datadog-dogstatsd-x86_64-rpm	0.00MB	✅	59.09MB	59.09MB	0.50MB
datadog-dogstatsd-x86_64-suse	0.00MB	✅	59.09MB	59.09MB	0.50MB
datadog-dogstatsd-arm64-deb	0.00MB	✅	56.50MB	56.50MB	0.50MB
datadog-heroku-agent-amd64-deb	0.00MB	✅	477.79MB	477.79MB	0.50MB
datadog-iot-agent-amd64-deb	0.00MB	✅	93.79MB	93.79MB	0.50MB
datadog-iot-agent-x86_64-rpm	0.00MB	✅	93.86MB	93.86MB	0.50MB
datadog-iot-agent-x86_64-suse	0.00MB	✅	93.86MB	93.86MB	0.50MB
datadog-iot-agent-arm64-deb	0.00MB	✅	89.85MB	89.85MB	0.50MB
datadog-iot-agent-aarch64-rpm	0.00MB	✅	89.92MB	89.92MB	0.50MB

Decision

✅ Passed

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: cf20325f-a474-4174-b634-9ea6e70ccf47

Baseline: 3728d5a
Comparison: d2f3116
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	file_tree	memory utilization	+0.49	[+0.42, +0.55]	1	Logs
➖	file_to_blackhole_1000ms_latency_linear_load	egress throughput	+0.33	[-0.13, +0.79]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	+0.13	[-0.79, +1.05]	1	Logs
➖	file_to_blackhole_0ms_latency_http1	egress throughput	+0.08	[-0.78, +0.94]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	+0.02	[-0.73, +0.76]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.04, +0.03]	1	Logs
➖	file_to_blackhole_300ms_latency	egress throughput	-0.01	[-0.64, +0.63]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	-0.01	[-0.29, +0.26]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	-0.03	[-0.80, +0.75]	1	Logs
➖	file_to_blackhole_0ms_latency_http2	egress throughput	-0.03	[-0.89, +0.82]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	-0.11	[-0.17, -0.04]	1	Logs bounds checks dashboard
➖	quality_gate_idle	memory utilization	-0.11	[-0.15, -0.07]	1	Logs bounds checks dashboard
➖	file_to_blackhole_500ms_latency	egress throughput	-0.18	[-0.96, +0.61]	1	Logs
➖	quality_gate_logs	% cpu utilization	-0.72	[-3.77, +2.33]	1	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-0.93	[-1.86, -0.00]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	-1.23	[-1.29, -1.16]	1	Logs

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	links
✅	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_idle_all_features	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10
✅	quality_gate_logs	lost_bytes	10/10
✅	quality_gate_logs	memory_usage	10/10

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:

1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

2. 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.

3. Its configuration does not mark it "erratic".

CI Pass/Fail Decision

✅ Passed. All Quality Gates 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_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_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.