nyc generates no output on TravisCI
See original GitHub issueLink to bug demonstration repository.
- https://github.com/chrisveness/geodesy
- https://travis-ci.org/chrisveness/geodesy/jobs/493767331#L2781
Expected Behavior

Observed Behavior

.travis.yml runs after_success: nyc npm test && nyc report --reporter=text-lcov | coveralls which consistently fails as shown above.
I think have inconsistently seen a similar issue in my local environment, but haven’t been able to reproduce it consistently.
Forensic Information
Ubuntu 14.04.5 LTS, Mac OS X 10.13.3, Windows Node 8.15.0, 10.15.1, 11.10.0, nyc 13.3.0
Issue Analytics
- State:
- Created 5 years ago
- Comments:16 (3 by maintainers)
Top Results From Across the Web
nyc report is not uploaded to Codecov in TravisCI build
When I run the npm run codecov --disable=gcov it generates the reports and I can see the results. But in my TravisCI build,...
Read more >Common Build Problems - Travis CI Docs
Build times out because no output was received #. When a long running command or compile step regularly takes longer than 10 minutes...
Read more >Travis CI: "You Have Too Many Tests LOLZ!" - randyzwitch.com
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself. Stalled ......
Read more >Empirical Study of Restarted and Flaky Builds on Travis CI
produce a set of reports (e.g., the output of linters and tests). If the ... Second, the Travis CI API does not support...
Read more >React App Build and Release — Travis CI and Github - Medium
Any software development starts with source code management (SCM) and a version control system (VCS). In my case, I used git for VCS....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Could you try setting the
ESM_DISABLE_CACHEenvironmental variable noted in https://github.com/standard-things/esm? Maybe trycross-env ESM_DISABLE_CACHE=1 nyc --cache=false npm test? Just to try ruling out issues caused by caching.I think this problem is unchanged.
It is less urgent for me as I found the workaround (above) of running
nyc npm testtwice.I still have similar problems in my local development environment, and sometimes don’t seem to be able to generate coverage at all.