Skip to content

chore: deprecate jest-repl #13407

chore: deprecate jest-repl

chore: deprecate jest-repl #13407

Triggered via pull request February 28, 2024 09:00
Status Failure
Total duration 27m 8s
Artifacts

nodejs.yml

on: pull_request
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
56s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
1m 5s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
1m 20s
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
TypeScript Compatibility
6m 33s
TypeScript Compatibility
Typecheck Examples and Tests
4m 33s
Typecheck Examples and Tests
Lint
1m 55s
Lint
Validate Yarn dependencies and constraints
14s
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

13 errors and 6 warnings
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 2` - Snapshot - 0 + Received + 1 PASS __tests__/bar.spec.js ✓ bar › 1 snapshot updated. + 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 updated from 1 test suite. at Object.toMatchSnapshot (e2e/__tests__/watchModeUpdateSnapshot.test.ts:50: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 2` - Snapshot - 0 + Received + 1 PASS __tests__/bar.spec.js ✓ bar › 1 snapshot updated. + 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 updated from 1 test suite. at Object.toMatchSnapshot (e2e/__tests__/watchModeUpdateSnapshot.test.ts:50:18)
handles a bad revision for "changedSince": e2e/Utils.ts#L105
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:105:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
handles a bad revision for "changedSince": e2e/Utils.ts#L105
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:105:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
gets changed files for hg: e2e/Utils.ts#L105
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:105:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
gets changed files for hg: e2e/Utils.ts#L105
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:105:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
monitors only root paths for hg: e2e/Utils.ts#L105
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:105:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
monitors only root paths for hg: e2e/Utils.ts#L105
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:105:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
handles a bad revision for "changedSince": e2e/Utils.ts#L105
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:105:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
handles a bad revision for "changedSince": e2e/Utils.ts#L105
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:105:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
handles a bad revision for "changedSince": e2e/Utils.ts#L105
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:105:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
handles a bad revision for "changedSince": e2e/Utils.ts#L105
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:105:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
Windows with shard 3/4 / Node v21.x
Final attempt failed. Child_process exited with error code 1
Windows with shard 1/4 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 1/4 / Node LTS using jest-jasmine2
Attempt 2 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
Windows with shard 2/4 / Node v21.x
Attempt 2 failed. Reason: Child_process exited with error code 1
Windows with shard 3/4 / Node v21.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 3/4 / Node v21.x
Attempt 2 failed. Reason: Child_process exited with error code 1