test: use more lenient time window for runtime metric time window (#7467)

BridgeAR · web-flow · commit 5889aba44e28 · 2026-02-10T09:53:17.000-05:00
Not only rounding issues can happen, the overall measured time
window might sometimes slightly deviate. The more lenient range
should account for that.
diff --git a/packages/dd-trace/test/runtime_metrics.spec.js b/packages/dd-trace/test/runtime_metrics.spec.js
@@ -527,8 +527,8 @@ function createGarbage (count = 50) {
               }
               if (metric === 'runtime.node.cpu.total') {
                 assert(
-                  // Subtracting 0.02 since lower numbers can happen due to rounding issues.
-                  number >= expected - 0.02 && number <= expected + 1,
+                  // Subtracting 0.1 for time-window/baseline alignment numbers and due to rounding issues.
+                  number >= expected - 0.1 && number <= expected + 1,
                   `${metric} sanity check failed (increase CPU load above with more ticks): ${number} ${expected}`
                 )
                 totalPercent = number

Original file line number	Diff line number	Diff line change
`@@ -527,8 +527,8 @@ function createGarbage (count = 50) {`
`527`	`527`	`}`
`528`	`528`	`if (metric === 'runtime.node.cpu.total') {`
`529`	`529`	`assert(`
`530`		`- // Subtracting 0.02 since lower numbers can happen due to rounding issues.`
`531`		`- number >= expected - 0.02 && number <= expected + 1,`
	`530`	`+ // Subtracting 0.1 for time-window/baseline alignment numbers and due to rounding issues.`
	`531`	`+ number >= expected - 0.1 && number <= expected + 1,`
`532`	`532`	`${metric} sanity check failed (increase CPU load above with more ticks): ${number} ${expected}`
`533`	`533`	`)`
`534`	`534`	`totalPercent = number`