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.

Sign up for GitHub

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

Jump to bottom

investigate seemingly non-deterministic nyc output #3155

Closed
boneskull opened this issue Dec 13, 2017 · 3 comments
Closed

investigate seemingly non-deterministic nyc output #3155

boneskull opened this issue Dec 13, 2017 · 3 comments
Labels
status: accepting prs Mocha can use your help with this one! type: chore generally involving deps, tooling, configuration, etc.

Comments

@boneskull
Copy link
Contributor

I don't believe the coverage data out of nyc. I've also seen this sort of thing happen with my own two eyes.

It is likely a misconfiguration on our part, but I don't know where. It may involve the way we are aggregating the results.

I would be indebted to @bcoe if he could take a look at our command-line usage and config file. Is there something obviously amiss?

Hey, at least we aren't in sourcemap hell...
@boneskull boneskull added type: chore generally involving deps, tooling, configuration, etc. status: accepting prs Mocha can use your help with this one! qa labels Dec 13, 2017
@boneskull
Copy link
Contributor Author

Why would a PR without code changes like this exhibit the same behavior?

@boneskull
Copy link
Contributor Author

...need to make sure it's not bad math on Coveralls' part...

@outsideris outsideris mentioned this issue Apr 3, 2018
Merged
@boneskull
Copy link
Contributor Author

this is either no longer happening or I just haven't noticed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: accepting prs Mocha can use your help with this one! type: chore generally involving deps, tooling, configuration, etc.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@boneskull