[test-infra-definitions][automated] Bump test-infra-definitions to 3b71e7f684e6ae257c9592b469c1a45dd3099d7f

[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 3b71e7f684e6ae257c9592b469c1a45dd3099d7f from 65fbab1e1eaf.
Here is the full changelog between the two commits: https://github.com/DataDog/test-infra-definitions/compare/65fbab1e1eaf..3b71e7f684e6ae257c9592b469c1a45dd3099d7f

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

[pr-commenter]

Regression Detector

Regression Detector Results

Run ID: 6dab9708-b3e8-417f-a4cc-f18ac9f06b90
Baseline: 10c4965
Comparison: ad2b755

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
➖	idle	memory utilization	+0.27	[+0.23, +0.30]
➖	file_tree	memory utilization	+0.17	[+0.07, +0.26]
➖	pycheck_1000_100byte_tags	% cpu utilization	+0.08	[-4.83, +4.99]
➖	otel_to_otel_logs	ingress throughput	+0.04	[-0.31, +0.39]
➖	uds_dogstatsd_to_api	ingress throughput	+0.00	[-0.20, +0.20]
➖	trace_agent_msgpack	ingress throughput	+0.00	[-0.00, +0.00]
➖	trace_agent_json	ingress throughput	+0.00	[-0.01, +0.01]
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.05	[-0.08, -0.02]
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-0.20	[-3.05, +2.66]
➖	basic_py_check	% cpu utilization	-0.84	[-3.31, +1.62]
➖	tcp_syslog_to_blackhole	ingress throughput	-5.18	[-25.54, +15.17]

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

[agent-platform-auto-pr]

Closing PR since it is considered stale compared to #25777. If you really want to merge this PR feel free to re-open it