chore: update micromatch #14130
Triggered via pull request
September 26, 2024 07:30
SimenB
Status
Success
Total duration
14m 9s
Artifacts
–
nodejs.yml
on: pull_request
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
55s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
1m 10s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
1m 28s
TypeScript Compatibility
5m 43s
Typecheck Examples and Tests
3m 54s
Lint
1m 48s
Validate Yarn dependencies and constraints
16s
Node LTS on Ubuntu with leak detection
1m 11s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
10 errors and 3 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)
|
|
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)
|
|
works with single typescript config that imports something:
e2e/__tests__/typescriptConfigFile.test.ts#L38
expect(received).toContain(expected) // indexOf
Expected substring: "PASS __tests__/mytest.alpha.js"
Received string: "Error: kill EPERM
at ChildProcess.kill (node:internal/child_process:511:26)
at ChildProcessWorker.killChild (D:\\a\\jest\\jest\\packages\\jest-worker\\build\\index.js:1000:17)
at ChildProcessWorker.forceExit (D:\\a\\jest\\jest\\packages\\jest-worker\\build\\index.js:1005:33)
at Timeout._onTimeout (D:\\a\\jest\\jest\\packages\\jest-worker\\build\\index.js:567:16)
at listOnTimeout (node:internal/timers:594:17)
at processTimers (node:internal/timers:529:7) {
errno: -4048,
code: 'EPERM',
syscall: 'kill'
}"
at Object.toContain (e2e/__tests__/typescriptConfigFile.test.ts:38:18)
|
|
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 v18.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
|