fix(jest-reporters): do not check coverageThreshold when running a shard #16844
Aeirxnodejs.yml
on: pull_request
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
28s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
36s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
58s
TypeScript Compatibility
5m 48s
Static Checks (Lint, Typecheck, Yarn Validate)
3m 51s
Node LTS on Ubuntu with leak detection
1m 3s
Node LTS on Ubuntu with watchman
1m 23s
Matrix: test-coverage
Matrix: test-runtime-vm-modules
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
1 error and 3 warnings
|
notify › does not report --notify flag:
e2e/__tests__/detectOpenHandles.ts#L111
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "Jest did not exit one second after the test run has completed.·
'This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue."
at Object.toBe (e2e/__tests__/detectOpenHandles.ts:111:27)
|
|
macOS with shard 3/3 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
macOS with shard 2/3 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
macOS with shard 3/3 / Node v24.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|