-
Notifications
You must be signed in to change notification settings - Fork 2
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
CircleCI Jest error with [email protected]
#349
Comments
After a lot of test-and-error CircleCI builds I found the error between the last successful build #1559 and #1561 with the following two diff in the dependency logs: ├─┬ [email protected]
- │ ├── @jest/[email protected]
+ │ ├── @jest/[email protected]
│ ├── [email protected]
- │ └── [email protected]
+ │ └── [email protected] - ├─┬ [email protected]
+ ├─┬ [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
- │ ├── [email protected] deduped
+ │ ├── [email protected]
│ ├── [email protected] deduped
- │ ├── [email protected]
- │ └── [email protected]
+ │ ├── [email protected]
+ │ └── [email protected] Since jest itself has not changed, the error must be caused by ts-jest. Reverting the ts-jest version to the last version 25.2.1 fixed the CircleCI problem. The ts-jest changelog v25.3.0 states a breaking change:
Furthermore, we cache the npm dependencies on CircleCI for a specific branch and only update them when the package.json is changed OR a new branch is pushed. |
Explanation what has happened:
I expect other branches (also from The fix would be switch to the - "ts-jest": "^25.2.1",
+ "ts-jest": "~25.2.1", @anita-steiner and @dvvanessastoiber would that work that fix for you? |
Observed behavior
lineupjs4
branch from 30.03.2020thinkh/331_string-filter-compatibility
branch from 30.03.2020thinkh/347_fix-overview-column
branch from 01.04.2020lineupjs4
branch from 01.04.2020Expected behavior
The test should run without errors.
The text was updated successfully, but these errors were encountered: