[Backport 7.83.x] [automated] Upgrade embedded Python patch version to 3.13.15

[dd-octo-sts]

Backport eafd80b from #54696.

---

What does this PR do?

Upgrades the Agent's embedded Python interpreter from 3.13.14 to 3.13.15 (patch version update).

Changes

• Updated omnibus/config/software/python3.rb with new version and SHA256
• Updated deps/cpython/cpython.MODULE.bazel with new version and SHA256
• Updated test/new-e2e/tests/agent-platform/common/agent_behaviour.go with expected version
• Created release note documenting the upgrade

Motivation

Keep embedded Python up-to-date with bug fixes and security patches.

Verification

SHA256 hash automatically fetched and verified against the official Python.org SBOM file.

See the official Python release page for details.

Describe how you validated your changes

CI is considered enough to validate changes.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 432d40e186

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Invalidate cached AIX stages when bumping Python

When an AIX build host has already completed a build, this version bump is ignored because stages/02-python.sh exits whenever the version-independent /opt/dd-build/.done/02-python sentinel exists; the Python-extension stages use similarly unversioned sentinels, and build.sh does not clear them. Re-running build.sh for this release without manually invoking clean.sh can therefore package Python 3.13.14 while the source and changelog claim 3.13.15. Include the Python version in the relevant sentinel/cache identity or automatically invalidate the Python-dependent stages when it changes.

Useful? React with 👍 / 👎.

[dd-octo-sts]

Files inventory check summary

File checks results against ancestor dca6425c:

Results for datadog-agent_7.83.0~rc.3.git.4.432d40e.pipeline.131104130-1_amd64.deb:

Detected file changes:

5 Changed files:

• opt/datadog-agent/embedded/lib/python3.13/imaplib.py:
  • Size changed: +10.18% (5.41 KiB) (53.09 KiB -> 58.5 KiB)
• opt/datadog-agent/embedded/lib/python3.13/idlelib/run.py:
  • Size changed: +12.11% (2.59 KiB) (21.36 KiB -> 23.95 KiB)
• opt/datadog-agent/embedded/lib/python3.13/curses/textpad.py:
  • Size changed: +20.09% (1.53 KiB) (7.59 KiB -> 9.12 KiB)
• opt/datadog-agent/embedded/lib/python3.13/tkinter/dialog.py:
  • Size changed: +13.03% (200.0 B) (1.5 KiB -> 1.69 KiB)
• opt/datadog-agent/embedded/lib/python3.13/idlelib/util.py:
  • Size changed: +98.70% (1.26 KiB) (1.28 KiB -> 2.55 KiB)

Results for datadog-iot-agent_7.83.0~rc.3.git.4.432d40e.pipeline.131104130-1_amd64.deb:

No change detected

[cit-pr-commenter-54b7da]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Job ID: 5cce6670-3694-428c-91b8-3e361ba82de2

Baseline: dca6425
Comparison: 432d40e
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_idle	memory utilization	+0.35	[+0.22, +0.47]	1	Logs bounds checks dashboard
➖	quality_gate_metrics_logs	memory utilization	+0.28	[+0.03, +0.54]	1	Logs bounds checks dashboard
➖	quality_gate_security_no_fs_load	memory utilization	+0.08	[-0.07, +0.23]	1	Logs bounds checks dashboard
➖	quality_gate_security_idle	memory utilization	+0.07	[-0.04, +0.17]	1	Logs bounds checks dashboard
➖	quality_gate_idle_all_features	memory utilization	-0.23	[-0.28, -0.19]	1	Logs bounds checks dashboard
➖	quality_gate_security_mean_fs_load	memory utilization	-0.28	[-0.35, -0.20]	1	Logs bounds checks dashboard
➖	quality_gate_private_action_runner	memory utilization	-0.43	[-0.55, -0.31]	1	Logs bounds checks dashboard
➖	quality_gate_logs	% cpu utilization	-1.31	[-2.17, -0.45]	1	Logs bounds checks dashboard

Bounds Checks: ❌ Failed

perf	experiment	bounds_check_name	replicates_passed	observed_value	links
✅	quality_gate_idle	intake_connections	10/10	4 = 4	bounds checks dashboard
❌	quality_gate_idle	memory_usage	0/10	172.91MiB > 154MiB	bounds checks dashboard
✅	quality_gate_idle	total_bytes_received	10/10	745.85KiB ≤ 819.20KiB	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	4 = 4	bounds checks dashboard
❌	quality_gate_idle_all_features	memory_usage	9/10	516.14MiB > 512MiB	bounds checks dashboard
✅	quality_gate_idle_all_features	total_bytes_received	10/10	1.13MiB ≤ 1.25MiB	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	4 ≤ 6	bounds checks dashboard
❌	quality_gate_logs	memory_usage	5/10	201.66MiB > 195MiB	bounds checks dashboard
✅	quality_gate_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_logs	total_bytes_received	10/10	263.82MiB ≤ 292MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	363.48 ≤ 2000	bounds checks dashboard
✅	quality_gate_metrics_logs	intake_connections	10/10	4 ≤ 6	bounds checks dashboard
✅	quality_gate_metrics_logs	memory_usage	10/10	407.92MiB ≤ 430MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_metrics_logs	total_bytes_received	10/10	0.94GiB ≤ 1.04GiB	bounds checks dashboard
✅	quality_gate_private_action_runner	memory_usage	10/10	71.40MiB ≤ 75MiB	bounds checks dashboard
✅	quality_gate_security_idle	cpu_usage	10/10	31.28 ≤ 100	bounds checks dashboard
✅	quality_gate_security_idle	memory_usage	10/10	324.08MiB ≤ 330MiB	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	cpu_usage	10/10	60.41 ≤ 200	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	memory_usage	10/10	303.34MiB ≤ 310MiB	bounds checks dashboard
✅	quality_gate_security_no_fs_load	cpu_usage	10/10	20.43 ≤ 100	bounds checks dashboard
✅	quality_gate_security_no_fs_load	memory_usage	10/10	309.97MiB ≤ 320MiB	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:

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

❌ Failed. Some Quality Gates were violated.

• quality_gate_idle_all_features, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check memory_usage: 9/10 replicas passed. Failed 1 which is > 0. Gate FAILED.
• quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_security_mean_fs_load, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_mean_fs_load, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_private_action_runner, 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 total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check memory_usage: 5/10 replicas passed. Failed 5 which is > 0. Gate FAILED.
• quality_gate_security_no_fs_load, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_no_fs_load, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_idle, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check total_bytes_received: 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 intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check memory_usage: 0/10 replicas passed. Failed 10 which is > 0. Gate FAILED.
• quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.