Windows tests are failing

[pichlermarc]

Windows tests seem to be failing in CI and locally. The tests for @opentelemetry/instrumentation-http seem to make the JavaScript heap run out of memory.

How to reproduce

Using node 16.19.1 and npm 8.19.3

• clone repo
• npm install
• npm run compile
• npm run test

Failures in CI

• https://github.com/open-telemetry/opentelemetry-js/actions/runs/4231076762
• https://github.com/open-telemetry/opentelemetry-js/actions/runs/4240317550
• https://github.com/open-telemetry/opentelemetry-js/actions/runs/4240406706

[pichlermarc]

Looks like this may be related to nyc, leaving it out drastically reduces memory usage to a few megabytes. 🤔
Looking into possible solutions other than increasing heap size, maybe we can reduce memory usage by adding some config options.

[pichlermarc]

During local testing, I discovered that it looks like source map updates in babel are allocating a lot of memory, this is only an issue when running that with nyc. I'm not entirely sure why this only happens when nyc is involved though. 🤔

The only tests which failed in this manner are the ones from @opentelemetry/instrumentation-http, I have not seen any indicators that anything we do in @opentelemetry/instrumentation-http causes this kind of excessive memory use.

I went ahead and opened a PR to remove nyc from the test script used in the Windows test workflow, and introduced test:coverage as an additional script that runs the tests with nyc. This should fix the problem outlined in this issue.

Should we have more problems, it may be worth updating tooling (babel) and looking into the structure of the @opentelemetry/instrumentation-http tests.

[MSNev]

I've also got a local repro of this (even with the above changes), where it will always fail on my windows machine (from a CLEAN build only), once I have a good build it continues to work.

Repo steps

git clean -xdf
npm install
npm run compile
npm run test

I (should) have a PR available shortly to fix