fix failing snapshot test (#15497) #14439
nodejs.yml
on: push
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
15s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
20s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
39s
TypeScript Compatibility
5m 41s
Typecheck Examples and Tests
4m 3s
Lint
1m 49s
Validate Yarn dependencies and constraints
23s
Node LTS on Ubuntu with leak detection
49s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
10 errors and 7 warnings
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 - 2
+ Received + 2
@@ -87,16 +87,16 @@
END: "six"
at log (__tests__/concurrent.test.js:15:11)
console.log
- END: "seven"
+ END: "ten"
at log (__tests__/concurrent.test.js:15:11)
console.log
- END: "ten"
+ END: "seven"
at log (__tests__/concurrent.test.js:15:11)
console.log
END: "eight"
at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:28:20)
|
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)
|
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)
|
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 - 2
+ Received + 2
@@ -92,16 +92,16 @@
END: "seven"
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)
at runMicrotasks (<anonymous>)
|
handles a bad revision for "changedSince":
e2e/Utils.ts#L107
EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir '\\?\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
EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir '\\?\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)
|
processChild › handles functions:
undefined#L1
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
processChild › handles functions:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\bigint-inequality-test'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/nonSerializableStructuresInequality.test.ts:48:10)
|
processChild › handles mixed structure:
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:111:35)
|
with only › runs the tests in the correct order:
e2e/__tests__/circusConcurrent.test.ts#L66
expect(received).toMatchSnapshot()
Snapshot name: `with only runs the tests in the correct order 1`
- Snapshot - 2
+ Received + 2
@@ -22,16 +22,16 @@
END: "nine"
at log (__tests__/concurrent-only.test.js:15:11)
console.log
- END: "six"
+ END: "four"
at log (__tests__/concurrent-only.test.js:15:11)
console.log
- END: "four"
+ END: "six"
at log (__tests__/concurrent-only.test.js:15:11)
console.log
afterAll
at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:66:20)
|
Ubuntu with shard 3/4 / Node v18.x
Attempt 1 failed. Reason: 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
|
macOS with shard 2/3 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
|
macOS with shard 2/3 / Node v16.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 2/4 / Node v23.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 4/4 / Node LTS using jest-jasmine2
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
|