TypeError: timer.unref is not a function

[iemjitendra]

TypeError: timer.unref is not a function

[pichlermarc]

Do you call MeterProvider.shutdown() when the tests are done?
Which platform are you running on?

[iemjitendra]

@pichlermarc Do you call MeterProvider.shutdown() when the tests are done? >>> NO
Which platform are you running on? >>> i am running on my localhost(macbook). i run yarn test on my project after integrating metrics sdk. As i still did not write any test cases for metrics then why my project existing test suite is braking by just integrating metrics api.
I tried this as well, did not work for me -> #3723 (comment)

[iemjitendra]

@pichlermarc can you please help in identify this issue. As i could not make out if this issue coming from metrics library or is there something wrong i am doing it.

[pichlermarc]

The reason is that we currently don't set the browser overrides in a way that jest can deal with them, it only works for webpack and some other bundlers.

See

• #3723 (reply in thread)
• #4543

So it's not something you're doing wrong, but testing in jest like this is a case we currently don't support. That being said #4543 is now up-for-grabs in case someone has cycles to work on it.

[iemjitendra]

thank you so much for help @pichlermarc
this issue is resolved by mocking metircs library in jest setupTest file, which is root file of jest
jest.mock('@opentelemetry/sdk-metrics');

BTW in the future upcoming versions, can this error go away without mocking metrics library.

[dyladan]

I believe this can be closed in favor of #4543

[pichlermarc]

BTW in the future upcoming versions, can this error go away without mocking metrics library.

@iemjitendra, yes we hope to address this with #4543, which should take care of that. I'll close this issue as duplicate for now as the other one is more explicit about what we need to do.