chore(deps): update dependency @prettier/sync to ^0.5.0 #13317
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
nodejs.yml
on: pull_request
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
53s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
1m 19s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
1m 43s
TypeScript Compatibility
6m 42s
Typecheck Examples and Tests
4m 43s
Lint
1m 59s
Validate Yarn dependencies and constraints
24s
Node LTS on Ubuntu with leak detection
1m 12s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
3 errors and 2 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 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)
|
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 1/4 / Node v20.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 2/4 / Node v18.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|