dd-trace-go
dd-trace-go copied to clipboard
[FLAKY TEST] profiler: TestStopLatency
Example failure (which passed after re-running on the same commit): https://github.com/DataDog/dd-trace-go/actions/runs/4008861739/jobs/6883545759#step:6:157
=== Failed
=== FAIL: profiler TestStopLatency (3.27s)
profiler_test.go:227: profiler took 862.397191ms to stop
The test attempts to have a little leniency to account for CI being sometimes substantially slower. But it's fundamentally a time-based test, which I think always introduces potential flakiness.