You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In 6fbd4fe I set coverage thresholds to be 100% after reaching that level while testing locally.
It passed locally but failed on Github Actions where the percentages were < 100%.
Left = local results; Right = Github Actions
Troubleshooting attempts
I tried
--no-cache when calling jest, locally and remote
jest --clearCache locally
Removing cache: yarn from .github/workflows/matt-fyi-cd.yml
Cloning and installing the repo from scratch locally
Updating my local yarn version to be the same as Github Actions (Node version was already the same)
None of those helped.
Changing coverage provider
I changed coverageProvider in Jest from v8 to babel (the actual default) and the results were consistent between local and Github Actions environments.
I have read that v8 is still experimental, though is apparently faster. So we may want to investigate changing back to it in the future.
The text was updated successfully, but these errors were encountered:
Already solved but adding details for posterity.
Context
In 6fbd4fe I set coverage thresholds to be 100% after reaching that level while testing locally.
It passed locally but failed on Github Actions where the percentages were < 100%.
Left = local results; Right = Github Actions

Troubleshooting attempts
I tried
--no-cache
when callingjest
, locally and remotejest --clearCache
locallycache: yarn
from.github/workflows/matt-fyi-cd.yml
None of those helped.
Changing coverage provider
I changed
coverageProvider
in Jest fromv8
tobabel
(the actual default) and the results were consistent between local and Github Actions environments.I have read that
v8
is still experimental, though is apparently faster. So we may want to investigate changing back to it in the future.The text was updated successfully, but these errors were encountered: