feat(ci): test binaries less heavy and less link time

[Aaalibaba42]

What does this PR do?

Test binaries inherit [profile.dev] debug = 2 (full debug info) from root Cargo.toml.

Motivation

This dominated Windows link/PDB time and cached target size

Additional Notes

line-tables-only keeps file/line info for backtraces and llvm-cov.

How to test the change?

On the first commit of this PR, it took 38min, which is pretty much in line with before the change, but cache needed rebuilding, I pushed an empty commit and it took less than 20 minutes, it might be a fluke, I'll do another empty commit, but it might be really big improvement for not much.

Apparently though, having a warm cache is pretty hard, and the 10gb repo limit is exceeded and cache evicted extremely quickly. Once caching is done by sccache, we would have the full upside of this, and it could have a real impact

[datadog-prod-us1-4]

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 76.56%

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

[dd-octo-sts]

Artifact Size Benchmark Report

aarch64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so	8.20 MB	8.20 MB	0% (0 B) 👌
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a	89.47 MB	89.47 MB	0% (0 B) 👌

aarch64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a	100.65 MB	100.65 MB	0% (0 B) 👌
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so	11.06 MB	11.06 MB	0% (0 B) 👌

libdatadog-x64-windows

Artifact	Baseline	Commit	Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll	26.62 MB	26.62 MB	0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib	94.56 KB	94.56 KB	0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb	180.69 MB	180.69 MB	0% (0 B) 👌
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib	772.58 MB	772.58 MB	0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll	8.72 MB	8.72 MB	0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib	94.56 KB	94.56 KB	0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb	25.64 MB	25.64 MB	0% (0 B) 👌
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib	51.06 MB	51.06 MB	0% (0 B) 👌

libdatadog-x86-windows

Artifact	Baseline	Commit	Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll	23.20 MB	23.20 MB	0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib	96.04 KB	96.04 KB	0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb	185.61 MB	185.60 MB	-0% (-8.00 KB) 👌
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib	759.08 MB	759.08 MB	0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll	6.74 MB	6.74 MB	0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib	96.04 KB	96.04 KB	0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb	27.58 MB	27.58 MB	0% (0 B) 👌
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib	48.60 MB	48.60 MB	0% (0 B) 👌

x86_64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a	79.74 MB	79.74 MB	0% (0 B) 👌
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so	9.15 MB	9.15 MB	0% (0 B) 👌

x86_64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a	95.38 MB	95.38 MB	0% (0 B) 👌
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so	11.16 MB	11.16 MB	0% (0 B) 👌

[pr-commenter]

Benchmarks

Comparison

Benchmark execution time: 2026-08-20 15:36:26

Comparing candidate commit 051e9c4 in PR branch jwiriath/APMSP-3942-line-table-only with baseline commit 24022a9 in branch main.

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

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:alloc_free/system/4096

• 🟩 execution_time [-12.839ns; -12.665ns] or [-12.098%; -11.934%]

scenario:glob_matcher/unicode_pattern_ascii_subject/wall_time

• 🟩 execution_time [-4.777ns; -4.706ns] or [-5.046%; -4.971%]

scenario:no_profiler/short_circuit/4096

• 🟩 execution_time [-6.154ns; -6.038ns] or [-5.951%; -5.839%]

scenario:profiler_attached/fast_path_system/4096

• 🟩 execution_time [-9.005ns; -8.857ns] or [-8.440%; -8.301%]

scenario:profiler_attached/slow_path_system/4096

• 🟩 execution_time [-7.720ns; -7.623ns] or [-5.014%; -4.951%]

scenario:trace_buffer/4_senders/no_delay

• 🟩 execution_time [-241.659µs; -215.283µs] or [-9.662%; -8.608%]
• 🟩 throughput [+137285.002op/s; +154975.529op/s] or [+9.534%; +10.762%]

Candidate

Omitted due to size.

Baseline

Omitted due to size.

[Aaalibaba42]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-08-26 12:12:47 UTC ℹ️ Start processing command /merge

---

2026-08-26 12:12:51 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in main is approximately 53m (p90).

---

2026-08-26 12:55:49 UTC ℹ️ MergeQueue: This merge request was merged