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

Fix check-coverage with custom options #483

Merged
merged 1 commit into from
Jan 16, 2017

Conversation

wbyoung
Copy link
Contributor

@wbyoung wbyoung commented Jan 7, 2017

Specifically, if the temp directory is configured, this needs to be configured on the NYC instance for both the command line action check-coverage as well as the --check-coverage flag passed when executing tests.

Specifically, if the temp directory is configured, this needs to be
configured on the NYC instance for both the command line action
`check-coverage` as well as the `--check-coverage` flag passed when
executing tests.
@coveralls
Copy link

coveralls commented Jan 7, 2017

Coverage Status

Changes Unknown when pulling 40605d4 on wbyoung:fix-check-coverage into ** on istanbuljs:master**.

@bcoe
Copy link
Member

bcoe commented Jan 8, 2017

@wbyoung looks quite reasonable to me 👍 thanks for the contribution.

@bcoe bcoe merged commit 1022b16 into istanbuljs:master Jan 16, 2017
@bcoe
Copy link
Member

bcoe commented Jan 16, 2017

@wbyoung thanks for the contribution, hopefully the first of many; I'm hoping to have at least a candidate release out to the next tag today.

@wbyoung wbyoung deleted the fix-check-coverage branch January 16, 2017 20:37
@wbyoung
Copy link
Contributor Author

wbyoung commented Jan 16, 2017

@bcoe awesome — thanks for merging & releasing quickly!

@bcoe
Copy link
Member

bcoe commented Jan 17, 2017

@wbyoung would love your help testing both of your patches:

npm cache clear; npm i nyc@next

once we're happy with our smoke testing, I'll promote this to latest.

@wbyoung
Copy link
Contributor Author

wbyoung commented Jan 18, 2017

@bcoe it looks like you released already… I have two projects that are now failing after this release. See wbyoung/relateify#1 and wbyoung/babel-plugin-transform-postcss#3.

The output I get is:

/Users/wbyoung/Code/relateify/node_modules/nyc/node_modules/istanbul-lib-coverage/lib/file.js:253
        for (i = 0; i < retArray.length; i += 1) {
                                ^

TypeError: Cannot read property 'length' of undefined
    at /Users/wbyoung/Code/relateify/node_modules/nyc/node_modules/istanbul-lib-coverage/lib/file.js:253:33
    at Array.forEach (native)
    at FileCoverage.merge (/Users/wbyoung/Code/relateify/node_modules/nyc/node_modules/istanbul-lib-coverage/lib/file.js:249:26)
    at /Users/wbyoung/Code/relateify/node_modules/nyc/node_modules/istanbul-lib-coverage/lib/coverage-map.js:54:26
    at Array.forEach (native)
    at CoverageMap.merge (/Users/wbyoung/Code/relateify/node_modules/nyc/node_modules/istanbul-lib-coverage/lib/coverage-map.js:51:29)
    at /Users/wbyoung/Code/relateify/node_modules/nyc/index.js:432:9
    at Array.forEach (native)
    at NYC._getCoverageMapFromAllCoverageFiles (/Users/wbyoung/Code/relateify/node_modules/nyc/index.js:431:22)
    at NYC.checkCoverage (/Users/wbyoung/Code/relateify/node_modules/nyc/index.js:464:18)
npm ERR! Test failed.  See above for more details.

@bcoe
Copy link
Member

bcoe commented Jan 18, 2017

try rm -rf ./node_modules/.cache, I don't think we've made any major changes to Istanbul-lib-coverage so this is weird.

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

Successfully merging this pull request may close these issues.

3 participants