chore: remove @types/prettier
dev dependency and update @prettier/sync
#13619
nodejs.yml
on: pull_request
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
58s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
1m 28s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
1m 32s
TypeScript Compatibility
6m 5s
Typecheck Examples and Tests
3m 53s
Lint
1m 52s
Validate Yarn dependencies and constraints
15s
Node LTS on Ubuntu with leak detection
1m 10s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
6 errors and 4 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)
|
transform-esm-testrunner › runs test with native ESM:
node:internal/child_process#L512
Can't parse JSON.
ERROR: SyntaxError Unexpected end of JSON input
STDOUT:
STDERR: node:events:497
throw er; // Unhandled 'error' event
^
Error: kill EPERM
at ChildProcess.kill (node:internal/child_process:512:26)
at listOnTimeout (node:internal/timers:573:17)
at process.processTimers (node:internal/timers:514:7)
Emitted 'error' event on ChildProcess instance at:
at ChildProcess.kill (node:internal/child_process:512:12)
[... lines matching original stack trace ...]
at process.processTimers (node:internal/timers:514:7) {
errno: -4048,
code: 'EPERM',
syscall: 'kill'
}
Node.js v21.7.3
at json (e2e/runJest.ts:156:11)
at Object.<anonymous> (e2e/__tests__/transform.test.ts:339:39)
|
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)
|
collects coverage only from specified file:
e2e/__tests__/coverageReport.test.ts#L49
expect(received).toMatchSnapshot()
Snapshot name: `collects coverage only from specified file 1`
- Snapshot - 6
+ Received + 0
- ----------|---------|----------|---------|---------|-------------------
- File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
- ----------|---------|----------|---------|---------|-------------------
- All files | 100 | 100 | 100 | 100 |
- file.js | 100 | 100 | 100 | 100 |
- ----------|---------|----------|---------|---------|-------------------
at Object.toMatchSnapshot (e2e/__tests__/coverageReport.test.ts:49:18)
|
respects testEnvironment docblock:
node:internal/child_process#L512
Can't parse JSON.
ERROR: SyntaxError Unexpected end of JSON input
STDOUT:
STDERR: node:events:497
throw er; // Unhandled 'error' event
^
Error: kill EPERM
at ChildProcess.kill (node:internal/child_process:512:26)
at listOnTimeout (node:internal/timers:573:17)
at process.processTimers (node:internal/timers:514:7)
Emitted 'error' event on ChildProcess instance at:
at ChildProcess.kill (node:internal/child_process:512:12)
[... lines matching original stack trace ...]
at process.processTimers (node:internal/timers:514:7) {
errno: -4048,
code: 'EPERM',
syscall: 'kill'
}
Node.js v21.7.3
at json (e2e/runJest.ts:156:11)
at Object.<anonymous> (e2e/__tests__/testEnvironment.test.ts:23:37)
|
globalSetup works with ESM modules:
e2e/__tests__/globalSetup.test.ts#L202
expect(received).toBe(expected) // Object.is equality
Expected: 0
Received: 1
at Object.toBe (e2e/__tests__/globalSetup.test.ts:202:20)
|
macOS with shard 2/3 / 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
|
Windows with shard 1/4 / Node v21.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 1/4 / Node v21.x
Attempt 2 failed. Reason: Child_process exited with error code 1
|