Use on WSL test runs

[lfloyd117]

I understand there are a few moving parts here and that this may not be entirely an issue with ember-cli-code-coverage specifically, but wanted to bring this integration issue up at very least as discussion so that we and anyone else with this setup may find a solution.

For some environment background, we are using [email protected]. Our CI uses docker running Linux containers via WSL on Windows hosts. We are able to get our full results and pass everything off to the scripts we use for handling code coverage.

But when we have the COVERAGE env var set to "true" to generate code coverage reports on our CI, we have cases where tests will fail loudly with Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory, which in my WSL experience is always an "out of memory" error. However we have memory logging in our test reporter (that shows the full system memory usage every test), and it looks green. My best guess is that something gets stuck in that test, ramps up memory and blows up before the next report.

Locally on my machine things run just fine. Since we use docker on our CI, I am able to mimic our CI builds directly on my machine using the same docker image and commands (which set the memory usage & CPU count as well).

Has anyone seen/documented such an issue or has workarounds? If I remove the COVERAGE env var, the issues go away. EDIT: It is worth noting we have tried increasing WSL memory allocation on the builders and it does not change the issue