flaky instrumentation-runtime-node test

[trentm]

I believe the 'should export event loop utilization metrics after eventLoopUtilizationMeasurementInterval' test case in

opentelemetry-js-contrib/plugins/node/instrumentation-perf-hooks/test/event_loop_utilization.test.ts

Line 94 in 4483a32

assert.strictEqual(metrics[0].dataPoints[0].value < 1, true);

may be flaky.

In the following unit-test run for PR #1938, that test assert failed:

    assert.strictEqual(metrics[0].dataPoints[0].value < 1, true);

https://github.com/open-telemetry/opentelemetry-js-contrib/actions/runs/8026238361/job/21928362946?pr=1938

> @opentelemetry/[email protected] test
> nyc ts-mocha -p tsconfig.json 'test/**/*.test.ts'



  nodejs.event_loop.utilization
    ✓ should stop exporting metrics when disabled
    ✓ should not export immediately after enable
    ✓ can use default eventLoopUtilizationMeasurementInterval
    1) should export event loop utilization metrics after eventLoopUtilizationMeasurementInterval


  3 passing (84ms)
  1 failing

  1) nodejs.event_loop.utilization
       should export event loop utilization metrics after eventLoopUtilizationMeasurementInterval:

      AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:

false !== true

      + expected - actual

      -false
      +true
      
      at Context.<anonymous> (test/event_loop_utilization.test.ts:94:12)
      at runNextTicks (internal/process/task_queues.js:60:5)
      at processTimers (internal/timers.js:497:9)

So I wonder if the new nodejs.event_loop.utilization metric can unexpectedly be higher than 1.
I have not been able to reproduce this failing locally.

I have only seen the failure that one time in CI. Mostly I'm just noting it for now. I'll have a PR to add some more output in those asserts in case that might help; but otherwise, I think we can wait and see if the test fails at all frequently before spending a lot of time on it.

/cc @d4nyll

[pichlermarc]

I'll look into it.