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

tests: update coveragePathIgnore jest configuration #10448

Merged
merged 2 commits into from
Mar 11, 2020
Merged

Conversation

paulirish
Copy link
Member

@paulirish paulirish commented Mar 10, 2020

this should fix the OOM that happens sometimes.

I tested this PR by commenting out coverageReporters: ['none'], from jest.config.js and then running yarn jest "byte-eff" --ci --coverage --reporters=default
before the change i saw /test/ and fixtures/ files in the output. afterwards i didnt. seems good. 😁


apparently our negative matches stopped working at some point. my guess is via jestjs/jest#7170 when we updated to jest 24. (march 2019)

(i didnt confirm this for sure, but it seems likely)

our coverage definitely changed when that landed....
image
https://coveralls.io/repos/109595/builds?page=180

@paulirish paulirish requested a review from a team as a code owner March 10, 2020 20:35
@paulirish paulirish requested review from brendankenny and removed request for a team March 10, 2020 20:35
@connorjclark connorjclark changed the title tests: update coveragePathIgnore configuration tests: update coveragePathIgnore jest configuration Mar 10, 2020
@brendankenny
Copy link
Member

apparently our negative matches stopped working at some point. my guess is via facebook/jest#7170 when we updated to jest 24. (march 2019)

our coverage definitely changed when that landed....

that's unfortunate. I would have thought our coverage check would have caught that, but weirdly codecov doesn't show much change (-0.04%) for that PR...

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

Successfully merging this pull request may close these issues.

5 participants