[test-infra-definitions][automated] Bump test-infra-definitions to 1c333ed90674178de0564a34a599b26357ad1b5d

[agent-platform-auto-pr]

This PR was automatically created by the test-infra-definitions bump task.

This PR bumps the test-infra-definitions submodule to 1c333ed90674178de0564a34a599b26357ad1b5d from 9c7c5005ca28.
Here is the full changelog between the two commits: DataDog/test-infra-definitions@9c7c500...1c333ed

⚠️ This PR is opened with the qa/no-code-change and changelog/no-changelog labels by default. Please make sure this is appropriate

[agent-platform-auto-pr]

[Fast Unit Tests Report]

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

Jobs:

• 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]

Package size comparison

Comparison with ancestor 3627a74336d52b84b78d68514c3b53efa1063fd4

Diff per package

package	diff	status	size	ancestor	threshold
datadog-agent-amd64-deb	0.00MB	✅	1265.73MB	1265.73MB	140.00MB
datadog-iot-agent-amd64-deb	0.00MB	✅	113.24MB	113.24MB	10.00MB
datadog-dogstatsd-amd64-deb	0.00MB	✅	78.41MB	78.41MB	10.00MB
datadog-heroku-agent-amd64-deb	0.00MB	✅	526.58MB	526.58MB	70.00MB
datadog-agent-x86_64-rpm	0.00MB	✅	1274.97MB	1274.97MB	140.00MB
datadog-agent-x86_64-suse	0.00MB	✅	1274.97MB	1274.97MB	140.00MB
datadog-iot-agent-x86_64-rpm	0.00MB	✅	113.31MB	113.31MB	10.00MB
datadog-iot-agent-x86_64-suse	0.00MB	✅	113.31MB	113.31MB	10.00MB
datadog-dogstatsd-x86_64-rpm	0.00MB	✅	78.49MB	78.49MB	10.00MB
datadog-dogstatsd-x86_64-suse	0.00MB	✅	78.49MB	78.49MB	10.00MB
datadog-agent-arm64-deb	0.00MB	✅	1000.85MB	1000.85MB	140.00MB
datadog-iot-agent-arm64-deb	0.00MB	✅	108.72MB	108.72MB	10.00MB
datadog-dogstatsd-arm64-deb	0.00MB	✅	55.65MB	55.65MB	10.00MB
datadog-agent-aarch64-rpm	0.00MB	✅	1010.07MB	1010.07MB	140.00MB
datadog-iot-agent-aarch64-rpm	0.00MB	✅	108.79MB	108.79MB	10.00MB

Decision

✅ Passed

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 960cfc3e-3fa5-4aa1-8b40-e30cde868240

Baseline: 3627a74
Comparison: cd37fb4
Diff

❌ Experiments with missing or malformed data

This is a critical error. No usable optimization goal data was produced by the listed experiments. This may be a result of misconfiguration. Ping #single-machine-performance and we can help out.

• tcp_dd_logs_filter_exclude (Logs)

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_logs	% cpu utilization	+1.13	[-1.82, +4.08]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	+0.93	[+0.80, +1.06]	1	Logs bounds checks dashboard
➖	tcp_syslog_to_blackhole	ingress throughput	+0.55	[+0.48, +0.61]	1	Logs
➖	quality_gate_idle	memory utilization	+0.40	[+0.36, +0.44]	1	Logs bounds checks dashboard
➖	file_to_blackhole_1000ms_latency_linear_load	egress throughput	+0.24	[-0.23, +0.70]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	+0.10	[-0.69, +0.89]	1	Logs
➖	file_to_blackhole_0ms_latency_http2	egress throughput	+0.05	[-0.82, +0.91]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	+0.04	[-0.73, +0.81]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	+0.03	[-0.70, +0.76]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.02	[-0.06, +0.11]	1	Logs
➖	file_to_blackhole_0ms_latency_http1	egress throughput	+0.01	[-0.80, +0.81]	1	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-0.03	[-0.76, +0.71]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	-0.09	[-0.92, +0.74]	1	Logs
➖	file_to_blackhole_300ms_latency	egress throughput	-0.12	[-0.75, +0.51]	1	Logs
➖	otel_to_otel_logs	ingress throughput	-0.24	[-0.90, +0.42]	1	Logs
➖	file_tree	memory utilization	-0.36	[-0.48, -0.24]	1	Logs

Bounds Checks: ❌ Failed

perf	experiment	bounds_check_name	replicates_passed	links
❌	file_to_blackhole_0ms_latency_http1	lost_bytes	9/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	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	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	bounds checks dashboard
✅	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_logs, 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_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.