Skip to content

fix(jest-config): allow reporters in project config #13043

fix(jest-config): allow reporters in project config

fix(jest-config): allow reporters in project config #13043

Triggered via pull request December 25, 2023 11:19
Status Failure
Total duration 1h 1m 19s
Artifacts

nodejs.yml

on: pull_request
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
18s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
36s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
34s
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
TypeScript Compatibility
5m 51s
TypeScript Compatibility
Typecheck Examples and Tests
4m 26s
Typecheck Examples and Tests
Lint
1m 43s
Lint
Validate Yarn dependencies and constraints
14s
Validate Yarn dependencies and constraints
Node LTS on Ubuntu with leak detection
1m 13s
Node LTS on Ubuntu with leak detection
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Fit to window
Zoom out
Zoom in

Annotations

7 errors
can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L51
expect(received).toMatchSnapshot(hint) Snapshot name: `can press "p" to filter by file name: test results 2` - Snapshot - 0 + Received + 2 PASS __tests__/bar.spec.js ✓ bar 1 ✓ bar 2 + + A worker process has failed to exit gracefully and has been force exited. This is likely caused by tests leaking due to improper teardown. Try running with --detectOpenHandles to find leaks. Active timers can also cause this, ensure that .unref() was called on them. at Object.toMatchSnapshot (e2e/__tests__/watchModePatterns.test.ts:51:18)
can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L70
expect(received).toMatchSnapshot(hint) Snapshot name: `can press "t" to filter by test name: test results 1` - Snapshot - 0 + Received + 2 PASS __tests__/bar.spec.js + A worker process has failed to exit gracefully and has been force exited. This is likely caused by tests leaking due to improper teardown. Try running with --detectOpenHandles to find leaks. Active timers can also cause this, ensure that .unref() was called on them. + PASS __tests__/foo.spec.js at Object.toMatchSnapshot (e2e/__tests__/watchModePatterns.test.ts:70:18)
Windows with shard 1/4 / Node LTS using jest-jasmine2
Process completed with exit code 1.
Node crawler does not pick up symlinked files by default: e2e/Utils.ts#L105
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test' at rmSync (e2e/Utils.ts:105:8) at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:36:10)
Should throw if watchman used with haste.enableSymlinks: e2e/Utils.ts#L105
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test' at rmSync (e2e/Utils.ts:105:8) at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:15:10)
Should throw if watchman used with haste.enableSymlinks: e2e/Utils.ts#L105
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test' at rmSync (e2e/Utils.ts:105:8) at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:36:10)
Windows with shard 4/4 / Node v21.x
Process completed with exit code 1.