Fix calledWith(objectContaining) when there are multiple calls #14451
Triggered via pull request
February 15, 2025 01:00
ecraig12345
Status
Success
Total duration
17m 40s
Artifacts
–
nodejs.yml
on: pull_request
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
14s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
17s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
54s
TypeScript Compatibility
5m 34s
Typecheck Examples and Tests
3m 57s
Lint
1m 56s
Validate Yarn dependencies and constraints
14s
Node LTS on Ubuntu with leak detection
46s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
17 errors and 5 warnings
|
handles a bad revision for "changedSince":
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
|
|
handles a bad revision for "changedSince":
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
|
|
gets changed files for hg:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
|
|
gets changed files for hg:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
|
|
monitors only root paths for hg:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
|
|
monitors only root paths for hg:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
|
|
handles a bad revision for "changedSince":
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
|
|
handles a bad revision for "changedSince":
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
|
|
all passing › runs the tests in the correct order:
e2e/__tests__/circusConcurrent.test.ts#L28
expect(received).toMatchSnapshot()
Snapshot name: `all passing runs the tests in the correct order 1`
- Snapshot - 6
+ Received + 6
@@ -67,41 +67,41 @@
START "nine"
at log (__tests__/concurrent.test.js:15:11)
console.log
- END: "nine"
+ END: "five"
at log (__tests__/concurrent.test.js:15:11)
console.log
START "ten"
at log (__tests__/concurrent.test.js:15:11)
console.log
- END: "five"
+ END: "six"
at log (__tests__/concurrent.test.js:15:11)
console.log
- END: "six"
+ END: "seven"
at log (__tests__/concurrent.test.js:15:11)
console.log
- END: "seven"
+ END: "eight"
at log (__tests__/concurrent.test.js:15:11)
console.log
- END: "ten"
+ END: "nine"
at log (__tests__/concurrent.test.js:15:11)
console.log
- END: "eight"
+ END: "ten"
at log (__tests__/concurrent.test.js:15:11)
console.log
afterAll
at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:28:20)
|
|
all passing › runs the tests in the correct order:
e2e/__tests__/circusConcurrent.test.ts#L28
expect(received).toMatchSnapshot()
Snapshot name: `all passing runs the tests in the correct order 1`
- Snapshot - 6
+ Received + 6
@@ -67,41 +67,41 @@
START "nine"
at log (__tests__/concurrent.test.js:15:11)
console.log
- END: "nine"
+ END: "six"
at log (__tests__/concurrent.test.js:15:11)
console.log
START "ten"
at log (__tests__/concurrent.test.js:15:11)
console.log
- END: "five"
+ END: "seven"
at log (__tests__/concurrent.test.js:15:11)
console.log
- END: "six"
+ END: "five"
at log (__tests__/concurrent.test.js:15:11)
console.log
- END: "seven"
+ END: "nine"
at log (__tests__/concurrent.test.js:15:11)
console.log
- END: "ten"
+ END: "eight"
at log (__tests__/concurrent.test.js:15:11)
console.log
- END: "eight"
+ END: "ten"
at log (__tests__/concurrent.test.js:15:11)
console.log
afterAll
at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:28:20)
|
|
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)
|
|
processChild › handles `Map`:
e2e/__tests__/nonSerializableStructuresInequality.test.ts#L36
Process exited
at waitUntil (e2e/__tests__/nonSerializableStructuresInequality.test.ts:36:9)
at Object.testIn2Workers (e2e/__tests__/nonSerializableStructuresInequality.test.ts:72:35)
|
|
processChild › handles `Map`:
undefined#L1
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
|
processChild › handles `Map`:
undefined#L1
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
|
processChild › handles `Symbol`:
e2e/__tests__/nonSerializableStructuresInequality.test.ts#L36
Process exited
at waitUntil (e2e/__tests__/nonSerializableStructuresInequality.test.ts:36:9)
at Object.testIn2Workers (e2e/__tests__/nonSerializableStructuresInequality.test.ts:98:35)
|
|
processChild › handles `Symbol`:
undefined#L1
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
|
processChild › handles `Symbol`:
undefined#L1
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
|
Windows with shard 2/4 / Node v18.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Windows with shard 3/4 / Node v20.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Windows with shard 3/4 / Node v22.x
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
|
|
Windows with shard 4/4 / Node v16.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|