Skip to content

feat: add retryImmediately option to jest.retryTimes (#14696) #13547

feat: add retryImmediately option to jest.retryTimes (#14696)

feat: add retryImmediately option to jest.retryTimes (#14696) #13547

Triggered via pull request March 26, 2024 08:21
Status Success
Total duration 1h 51m 2s
Artifacts

nodejs.yml

on: pull_request
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
1m 2s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
1m 13s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
1m 21s
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
TypeScript Compatibility
6m 19s
TypeScript Compatibility
Typecheck Examples and Tests
3m 54s
Typecheck Examples and Tests
Lint
2m 10s
Lint
Validate Yarn dependencies and constraints
15s
Validate Yarn dependencies and constraints
Node LTS on Ubuntu with leak detection
1m 14s
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

5 errors and 2 warnings
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 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:51:18)
can press "u" to update snapshots: e2e/__tests__/watchModeUpdateSnapshot.test.ts#L50
expect(received).toMatchSnapshot(hint) Snapshot name: `can press "u" to update snapshots: test results 1` - Snapshot - 0 + Received + 1 @@ -14,7 +14,8 @@ | ^ at Object.toMatchSnapshot (__tests__/bar.spec.js:1:35) › 1 snapshot failed. + 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. Snapshot Summary › 1 snapshot failed from 1 test suite. Inspect your code changes or press `u` to update them." at Object.toMatchSnapshot (e2e/__tests__/watchModeUpdateSnapshot.test.ts:50:18)
testMatch should able to match file with cjs and mjs extension: e2e/__tests__/testMatch.test.ts#L13
expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 at Object.toBe (e2e/__tests__/testMatch.test.ts:13:27)
Windows with shard 4/4 / Node v20.x
unable to access 'https://github.com/jestjs/jest/': Failed to connect to github.com port 443 after 21030 ms: Couldn't connect to server
Windows with shard 4/4 / Node v20.x
unable to access 'https://github.com/jestjs/jest/': Failed to connect to github.com port 443 after 21091 ms: Couldn't connect to server
Windows with shard 1/4 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 2/4 / Node v21.x
Attempt 1 failed. Reason: Child_process exited with error code 1