ci(prof): run additional allocation test on all PHP versions

[realFlowControl]

Description

This PR is based on #3559 with the intention to run that new correctness test on all PHP versions and provide a value and error range that matches all PHP versions. Additionally this runs the allocation_time_combined test without an adjusted sampling distance for allocations 🎉

Reviewer checklist

• Test coverage seems ok.
• Appropriate labels assigned.

[datadog-official]

⚠️ Tests

✨ Fix all issues with BitsAI or with Cursor

⚠️ Warnings

🧪 1028 Tests failed

testSearchPhpBinaries from integration.DDTrace\Tests\Integration\PHPInstallerTest (Datadog) (Fix with Cursor)

DDTrace\Tests\Integration\PHPInstallerTest::testSearchPhpBinaries
Test code or tested code printed unexpected output: Searching for available php binaries, this operation might take a while.

testSimplePushAndProcess from laravel-58-test.DDTrace\Tests\Integrations\Laravel\V5_8\QueueTest (Datadog) (Fix with Cursor)

DDTrace\Tests\Integrations\Laravel\V5_8\QueueTest::testSimplePushAndProcess
Test code or tested code printed unexpected output: spanLinksTraceId: 69b0443c00000000b7d5c92645b2ba67
tid: 69b0443c00000000
hexProcessTraceId: b7d5c92645b2ba67
hexProcessSpanId: a551c06431b1354f
processTraceId: 13246715045195463271
processSpanId: 11912514025934632271

phpvfscomposer://tests/vendor/phpunit/phpunit/phpunit:106

testSimplePushAndProcess from laravel-8x-test.DDTrace\Tests\Integrations\Laravel\V8_x\QueueTest (Datadog) (Fix with Cursor)

DDTrace\Tests\Integrations\Laravel\V8_x\QueueTest::testSimplePushAndProcess
Test code or tested code printed unexpected output: spanLinksTraceId: 69b044bd00000000e4865f5a0527e1b3
tid: 69b044bd00000000
hexProcessTraceId: e4865f5a0527e1b3
hexProcessSpanId: 3dd959933f6e6093
processTraceId: 16466953927764992435
processSpanId: 4456691795219079315

phpvfscomposer://tests/vendor/phpunit/phpunit/phpunit:106

View all

ℹ️ Info

❄️ No new flaky tests detected

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: e9c2a9b | Docs | Datadog PR Page | Was this helpful? React with 👍/👎 or give us feedback!}

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 62.32%. Comparing base (41b371e) to head (e9c2a9b).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #3592      +/-   ##
==========================================
- Coverage   62.39%   62.32%   -0.08%     
==========================================
  Files         142      142              
  Lines       13586    13586              
  Branches     1775     1775              
==========================================
- Hits         8477     8467      -10     
- Misses       4304     4311       +7     
- Partials      805      808       +3     

see 3 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 41b371e...e9c2a9b. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[pr-commenter]

Benchmarks [ profiler ]

Benchmark execution time: 2026-03-10 16:24:35

Comparing candidate commit e9c2a9b in PR branch florian/foobar with baseline commit 41b371e in branch master.

Found 0 performance improvements and 3 performance regressions! Performance is the same for 26 metrics, 7 unstable metrics.

scenario:php-profiler-timeline-memory-control

• 🟥 cpu_user_time [+33.879ms; +46.399ms] or [+5.625%; +7.704%]
• 🟥 execution_time [+35.388ms; +41.999ms] or [+5.604%; +6.651%]

scenario:php-profiler-timeline-memory-with-profiler

• 🟥 execution_time [+26.875ms; +45.485ms] or [+2.706%; +4.580%]

[morrisonlevi]

This stack is for wall-time. The idea here is that str_replace will use enough CPU that the allocation time spent is negligible, and the replace operation will dominate it.

The variability comes from whether it's piggy-backing on the allocation interrupt (for frameless versions, where we don't get an interrupt on the frameless call) or on older versions without it, we get an interrupt, and it's more accurate.