Coverage output in Github Action is different to when run locally

[rubengmurray]

First of, I don't know whether this is within scope of c8 or not, but I'm sharing here anyway for further input / visibility.

NOTE: Our test suite is run via the same npm scripts - which control the choreography of downloading all docker containers + spinning up the server in the same order - in Github vs Local so I see no reason why the metric should be different, but here is the output.

Local:

Github Action

Process:

• Run test script
• Script pulls down required docker dependencies
• Spin up node server
• Test APIs from mocha
• Use c8 to track test coverage

Anyone seen this before / any pointers?

[MeirionHughes]

I'm getting exactly the same issue. same coverage scripts report different coverage between my local (windows) and github action (ubuntu I think?)

[rubengmurray]

Interesting point on OS. I'm running locally on macOS, but in the cloud on ubuntu-latest.

Just had this come up again

Github Action

Local