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

Failing to Generate Coverage for Some Files #183

Open
DeedleFake opened this issue Mar 6, 2019 · 2 comments
Open

Failing to Generate Coverage for Some Files #183

DeedleFake opened this issue Mar 6, 2019 · 2 comments

Comments

@DeedleFake
Copy link

I'm running flow-coverage-report against a moderately large codebase. It's failing get coverage information for some files, seemingly at random. I'm not sure what's different about these files from the others.

An example:

ERROR Collecting coverage data from scripts/uglify.js { Error: Command failed: flow coverage --json scripts/uglify.js
    at ChildProcess.exithandler (child_process.js:297:12)
    at ChildProcess.emit (events.js:197:13)
    at maybeClose (internal/child_process.js:984:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:265:5)
  killed: true,
  code: null,
  signal: 'SIGTERM',
  cmd: 'flow coverage --json scripts/uglify.js' }

Interestingly, running flow coverage --json scripts/uglify.js manually works completely fine. The number of files it fails on also seems to vary depending on what the -c flag has been set to. If it's left on the default of 1, it fails on about a third to half of the files, and setting it to 4 causes it to fail on all of the files in the entire codebase.

@kiparenkomb
Copy link

Hi everybody!
I have the same error and I cannot understand what the problem is?

@rpl
Copy link
Owner

rpl commented Sep 18, 2020

@kiparenkomb VERBOSE=1 flow-coverage-report ... may be able to produce some additional info about what is going on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants