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

caching issue with check-coverage & report #974

Closed
brewster1134 opened this issue Jan 21, 2019 · 2 comments
Closed

caching issue with check-coverage & report #974

brewster1134 opened this issue Jan 21, 2019 · 2 comments
Labels

Comments

@brewster1134
Copy link

i noticed that when i make configuration changes, the results are not reflected when i use either nyc check-coverage or nyc report. the only way (that i can find) to force it to refresh, is by running nyc mocha

  • it happens regardless of if configuration options are set from package,json or the command line
  • it still happens when cache is set to to false
  • it happens with any configuration option is changed
  • it even happens with a new shell session

although it happens with any option, the most visually obvious option i was using test with was all. here are steps to reproduce...

### initial report
nyc report --reporter text
# no files reported (correct)

nyc report --reporter text --all
# no files reported (incorrect)
nyc mocha -all
# all files reported (correct)
nyc report --reporter text --all
# all files reported (correct)

### works in reverse too

nyc report --reporter text
# no files reported (incorrect)
nyc mocha
# no files reported (correct)
nyc report --reporter text
# no files reported (correct)
@coreyfarrell
Copy link
Member

Both nyc report and nyc merge operate on existing results. They do not perform instrumentation, they only operate on existing files. Also note that these sub-commands do not support the --all option.

@stale
Copy link

stale bot commented Apr 28, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Apr 28, 2019
@stale stale bot closed this as completed May 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants