[test-infra-definitions][automated] Bump test-infra-definitions to 7442fc4b26bb7e82fcc139f972a22e20bef51d7a

[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 7442fc4b26bb7e82fcc139f972a22e20bef51d7a from e79f06b7fce3.
Here is the full changelog between the two commits: DataDog/test-infra-definitions@e79f06b...7442fc4

⚠️ 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 45026213 (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

[pr-commenter]

Regression Detector

Regression Detector Results

Run ID: 7222408f-d1db-48ff-8ae1-45f5ac50d9f9 Metrics dashboard Target profiles

Baseline: 7642cf1
Comparison: ed149f6

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

No significant changes in experiment optimization goals

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	otel_to_otel_logs	ingress throughput	+0.50	[-0.31, +1.30]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.01	[-0.09, +0.11]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.01, +0.01]	1	Logs
➖	pycheck_lots_of_tags	% cpu utilization	-0.11	[-2.60, +2.37]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	-0.20	[-0.25, -0.15]	1	Logs
➖	basic_py_check	% cpu utilization	-0.52	[-3.19, +2.15]	1	Logs
➖	idle	memory utilization	-0.85	[-0.91, -0.79]	1	Logs
➖	file_tree	memory utilization	-1.03	[-1.14, -0.92]	1	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-1.65	[-2.37, -0.92]	1	Logs

Bounds Checks

perf	experiment	bounds_check_name	replicates_passed
✅	idle	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:

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