chore(profiling-315): install 3.15 gtest in test/py315

[vlad-scherbich]

prev: #19272 | next: #19273

Description

Delta vs #19272.

dd_wrapper_add_test gains optional INSTALL_SUBDIR. Only caller: test_frame_state_315 with INSTALL_SUBDIR py315, so that gtest installs to test/py315/ instead of the shared test/ directory.

build_base_venvs artifact paths include test/test_* and test/py315/test_* so the isolated binary is published for downstream jobs.

The gtest itself stays in #19269. This PR is the keyword, dest, and artifact glob.

Layer	Meaning	Which PR
Compiled	INSTALL_SUBDIR keyword + test/py315 dest	this PR
Armed	cmake install path + artifact publish	this PR
Observable	—	—

Testing

Risks

Additional Notes

changelog/no-changelog.

Contributes to #17817

Pre-review checklist

• The changes have been tested in real services in staging
• The PR does not result in new crashes

[datadog-datadog-us1-prod]

 

✨ Unblock PR with BitsAI

⚠️ Warnings

❌ Your PR has failed checks. Please review the issues below and take necessary action before merging.

🚦 16 Pipeline jobs failed

DataDog/apm-reliability/dd-trace-py | core/internal 1/9 — 🔧 Needs a code fix, caused by this PR

View more details · View in GitLab

DataDog/apm-reliability/dd-trace-py | core/internal 9/9 — 🔧 Needs a code fix, caused by this PR

View more details · View in GitLab

DataDog/apm-reliability/dd-trace-py | profiling/profile 10/23 — 🔧 Needs a code fix, caused by this PR

View more details · View in GitLab

View all 16 failed jobs.

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 1dbd9e8 | Docs | View more details | Give us feedback!}

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-09-02 19:39:33

Comparing candidate commit 1dbd9e8 in PR branch vlad/315-profiling-test-install-subdir with baseline commit 1fc47d8 in branch main.

📊 Benchmarking dashboard

Found 0 performance improvements and 4 performance regressions! Performance is the same for 579 metrics, 10 unstable metrics, 3 known flaky benchmarks, 15 flaky benchmarks without significant changes.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

• 🟩 = significantly better candidate vs. baseline
• 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

scenario:httppropagationinject-ids_only

• 🟥 execution_time [+1.867µs; +2.035µs] or [+11.286%; +12.301%]

scenario:iastaspectsospath-ospathbasename_aspect

• 🟥 execution_time [+107.906µs; +116.581µs] or [+25.739%; +27.808%]

scenario:telemetryaddmetric-1-count-metric-1-times

• 🟥 execution_time [+370.702ns; +422.170ns] or [+13.798%; +15.714%]

scenario:tracer-small

• 🟥 execution_time [+39.158µs; +41.111µs] or [+11.748%; +12.334%]

Unstable benchmarks

These benchmarks have a confidence interval too wide to call a change; treat them as noise rather than signal.

scenario:coreapiscenario-context_with_data_listeners

• unstable execution_time [-761.482ns; +715.860ns] or [-6.837%; +6.428%]

scenario:coreapiscenario-core_dispatch_1_listener

• unstable execution_time [-37.533ns; +30.562ns] or [-6.016%; +4.899%]

scenario:coreapiscenario-core_dispatch_50_listeners

• unstable execution_time [-1701.262ns; +1635.652ns] or [-9.867%; +9.486%]

scenario:coreapiscenario-core_dispatch_exception_listeners

• unstable execution_time [-1342.752ns; +1120.842ns] or [-10.369%; +8.655%]

scenario:coreapiscenario-core_dispatch_listeners

• unstable execution_time [-326.419ns; +335.208ns] or [-8.795%; +9.031%]

scenario:coreapiscenario-core_dispatch_no_args_listeners

• unstable execution_time [-263.853ns; +253.794ns] or [-8.934%; +8.593%]

scenario:coreapiscenario-core_dispatch_with_results_1_listener

• unstable execution_time [-88.000ns; +62.033ns] or [-7.424%; +5.233%]

scenario:coreapiscenario-core_dispatch_with_results_50_listeners

• unstable execution_time [-3911.536ns; +4154.865ns] or [-9.542%; +10.136%]

scenario:coreapiscenario-core_dispatch_with_results_listeners

• unstable execution_time [-771.733ns; +769.826ns] or [-9.458%; +9.435%]

scenario:packagesupdateimporteddependencies-import_many_stdlib_cached

• unstable execution_time [-53.035µs; +57.097µs] or [-9.225%; +9.932%]

Known flaky benchmarks

These benchmarks are marked as flaky and will not trigger a failure. Modify FLAKY_BENCHMARKS_REGEX to control which benchmarks are marked as flaky.

scenario:iastaspects-casefold_noaspect

• 🟥 execution_time [+44.336µs; +49.705µs] or [+17.888%; +20.054%]

scenario:iastaspects-swapcase_aspect

• 🟥 execution_time [+32.352µs; +41.732µs] or [+11.300%; +14.576%]

scenario:span-start

• 🟥 execution_time [+1.721ms; +1.856ms] or [+12.711%; +13.716%]

Known flaky benchmarks without significant changes:

• scenario:errortrackingflasksqli-baseline
• scenario:flasksimple-iast-get
• scenario:iastaspects-casefold_aspect
• scenario:iastaspects-index_aspect
• scenario:iastaspects-ljust_noaspect
• scenario:iastaspects-lower_aspect
• scenario:iastaspects-replace_aspect
• scenario:iastaspects-title_noaspect
• scenario:iastaspects-translate_aspect
• scenario:iastaspects-translate_noaspect
• scenario:iastaspects-upper_noaspect
• scenario:packagespackageforrootmodulemapping-cache_off
• scenario:packagespackageforrootmodulemapping-cache_on
• scenario:sethttpmeta-all-enabled
• scenario:telemetryaddmetric-record-100-metrics

[vlad-scherbich]

Folded into #19269 (df5e2f72de). The only INSTALL_SUBDIR caller is test_frame_state_315, which already lives on #19269; sitting after #19272 implied an asyncio dependency that does not exist. #19273 restacked onto #19272. Not merged.

[vlad-scherbich]

Closed: folded into #19269, not merged.