fix(ci-visibility): proper statuscode with pytest-xdist + ATR

[gnufede]

Checklist

• PR author has checked that all the criteria below are met
• The PR description includes an overview of the change
• The PR description articulates the motivation for the change
• The change includes tests OR the PR description describes a testing strategy
• The PR description notes risks associated with the change, if any
• Newly-added code is easy to change
• The change follows the library release note guidelines
• The change includes or references documentation updates if necessary
• Backport labels are set (if applicable)

Reviewer Checklist

• Reviewer has checked that all the criteria below are met
• Title is accurate
• All changes are related to the pull request's stated goal
• Avoids breaking API changes
• Testing strategy adequately addresses listed risks
• Newly-added code is easy to change
• Release note makes sense to a user of the library
• If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment
• Backport labels are set in a manner that is consistent with the release branch maintenance policy

[github-actions]

CODEOWNERS have been resolved as:

ddtrace/contrib/internal/pytest/_atr_utils.py                           @DataDog/ci-app-libraries
ddtrace/contrib/internal/pytest/_attempt_to_fix.py                      @DataDog/ci-app-libraries
ddtrace/contrib/internal/pytest/_efd_utils.py                           @DataDog/ci-app-libraries
ddtrace/contrib/internal/pytest/_plugin_v2.py                           @DataDog/ci-app-libraries
ddtrace/contrib/internal/pytest/_retry_utils.py                         @DataDog/ci-app-libraries
ddtrace/contrib/internal/pytest/_utils.py                               @DataDog/ci-app-libraries
ddtrace/internal/packages.py                                            @DataDog/apm-core-python
tests/contrib/pytest/test_pytest_attempt_to_fix.py                      @DataDog/ci-app-libraries
tests/contrib/pytest/utils.py                                           @DataDog/ci-app-libraries

[github-actions]

Bootstrap import analysis

Comparison of import times between this PR and base.

Summary

The average import time from this PR is: 235 ± 3 ms.

The average import time from base is: 238 ± 4 ms.

The import time difference between this PR and base is: -2.6 ± 0.1 ms.

Import time breakdown

The following import paths have shrunk:

ddtrace.auto 2.047 ms (0.87%)

ddtrace.bootstrap.sitecustomize 1.375 ms (0.58%)

ddtrace.bootstrap.preload 1.375 ms (0.58%)

ddtrace.internal.products 1.375 ms (0.58%)

ddtrace.internal.remoteconfig.client 0.642 ms (0.27%)

ddtrace 0.672 ms (0.29%)

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-04-25 16:38:51

Comparing candidate commit f44346d in PR branch gnufede/SDTEST-1894 with baseline commit 73764dc in branch main.

Found 5 performance improvements and 3 performance regressions! Performance is the same for 482 metrics, 2 unstable metrics.

scenario:ddtracerun-auto_profiling

• 🟥 execution_time [+173.044ms; +176.858ms] or [+25.836%; +26.405%]

scenario:iast_aspects-ospathsplitext_aspect

• 🟥 execution_time [+475.063ns; +650.623ns] or [+10.516%; +14.402%]

scenario:otelspan-start-finish

• 🟩 execution_time [-18.358ms; -18.019ms] or [-23.361%; -22.931%]

scenario:otelspan-start-finish-telemetry

• 🟩 execution_time [-19.548ms; -19.142ms] or [-24.284%; -23.781%]

scenario:span-start-finish

• 🟩 execution_time [-15.711ms; -15.335ms] or [-32.883%; -32.096%]

scenario:span-start-finish-telemetry

• 🟩 execution_time [-15.791ms; -15.342ms] or [-32.087%; -31.175%]

scenario:span-start-finish-traceid128

• 🟩 execution_time [-18.430ms; -18.034ms] or [-35.930%; -35.157%]

scenario:telemetryaddmetric-1-gauge-metric-1-times

• 🟥 execution_time [+213.658ns; +289.008ns] or [+10.318%; +13.957%]