Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different coverage reported on Windows vs Linux #137

Closed
oliversalzburg opened this issue Aug 28, 2019 · 5 comments
Closed

Different coverage reported on Windows vs Linux #137

oliversalzburg opened this issue Aug 28, 2019 · 5 comments
Labels
more-info-needed For issues that have not be described fully

Comments

@oliversalzburg
Copy link

I get differing coverage reports depending on if I run the test on Windows 10 x64 vs Ubuntu x64. Both platforms are running Node 12.9.1. The issue seems to only affect specific files in the test suite/application.

Windows

image

Ubuntu

image

The pattern is always the same in all affected files. The imports are shown as not covered and so is the class and method declaration.

When I tried to isolate the behavior in a smaller projects, I was not able to. Any suggestions on how to approach this so I can get more useful information?

@bcoe
Copy link
Owner

bcoe commented Sep 6, 2019

@oliversalzburg could you provide a repository with a minimal reproduction of the issue you're seeing?

@bcoe bcoe added the more-info-needed For issues that have not be described fully label Sep 6, 2019
@oliversalzburg
Copy link
Author

I actually tried working on one for a while, but when I removed all our private dependencies, I was no longer to reproduce the issue :(

I was hoping someone might have an idea of why this is happening so I could investigate into a certain area. I will try my luck again with a repro and report back.

@bcoe
Copy link
Owner

bcoe commented Sep 6, 2019

👍 are you using anything that transpiles code, like Babel, TypeScript, or ESM?

@oliversalzburg
Copy link
Author

I'm not. This is plain JS running in Node.

@oliversalzburg
Copy link
Author

oliversalzburg commented Sep 9, 2019

Ugh, can't reproduce it at work at all right now. Either the code has changed so that the issue no longer appears or it's something special about my home workstation. I'll check it out tonight.

I can currently no longer reproduce this. Linux and Windows are reporting the same coverage. As my workstations all run Windows, my original plan to reproduce this on another workstation is pointless as the wrong coverage report came originally from Linux.

Not sure we'll be able to track this down to a specific change again. I'll reopen if we can, otherwise I'll just be happy that the report is correct now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
more-info-needed For issues that have not be described fully
Projects
None yet
Development

No branches or pull requests

2 participants