-
Notifications
You must be signed in to change notification settings - Fork 22
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
Build failure with Jest snapshot errors #14
Comments
Replaced the $ jest --coverage --updateSnapshot
PASS packages/assert/__tests__/assert.test.ts
› 4 snapshots updated.
PASS packages/jest/__tests__/matcher.test.ts
› 4 snapshots updated.
PASS packages/test-utils/__tests__/test-utils.test.ts
› 2 snapshots updated.
PASS packages/preset-rules/__tests__/rules.test.ts
PASS packages/jest/__tests__/setup.test.ts
PASS packages/format/__tests__/format.test.ts
› 1 snapshot updated.
...
Snapshot Summary
› 11 snapshots updated from 4 test suites.
Test Suites: 7 passed, 7 total
Tests: 38 passed, 38 total
Snapshots: 11 updated, 7 passed, 18 total
Time: 6.225 s
Ran all test suites in 2 projects.
Done in 13.35s. But think |
Tried reverting
Same snapshot issues as before 😞 |
Yeah, definitely don't keep Something else I thought of to try... I see the CI is set to run on ubuntu. Are you generating the snapshots locally on a Mac? If so, let's try setting the
|
check if the snapshot errors could be related to OS #14
Thanks Trevor, I was thinking about the OS too.
|
@trevor-bliss Resolved this issue by switching to circleci. Tests all pass now 😌 |
Created Test workflow is failing with Jest snapshot errors · Issue #159 · actions/setup-node and also filed a github support ticket. |
I'm a big fan of CircleCI so I don't think this is a huge loss :P |
Good to know :) |
Build is failing with Jest snapshot errors saying they are not up-to-date - but the updated snapshots have been checked in and the tests pass locally after a clean build. Even checked out the branch to a diff clean location in my machine and tried out the CI commands - no issues 😕
Originally posted by @mohanraj-r in #13 (comment)
The text was updated successfully, but these errors were encountered: