You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Update profiler to 5.14.0
* test(profiler): fix wall profiler context telemetry tests on Ubuntu+Node24
With pprof 5.14.0, SetContext() in CPED mode only creates context holders
when inside an ALS run() scope. On Ubuntu (more aggressive GC), the transient
holders created by the profiler exporter's storage.run() were collected before
getMetrics() was called, causing the gauge to always report 0.
Fix by wrapping busyWait in tracer.trace() in the profiler test fixture so
there's a long-lived span context keeping CPED holders alive throughout the
test duration.
Additionally, use resolveAtFirstSuccess=true in both profiler telemetry
assertTelemetryReceived calls: with an active span, dd-trace emits 'tracers'
namespace generate-metrics events before the 'profilers' ones, so the handler
must keep scanning rather than stopping at the first event.
Also removes the macOS skip from the wall profiler context telemetry test and
increases TEST_DURATION_MS from 1500 to 3000 to avoid timing races.
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
0 commit comments