Skip to content

feat(expect): Expose spyMatchers #14077

feat(expect): Expose spyMatchers

feat(expect): Expose spyMatchers #14077

Triggered via pull request September 2, 2024 09:28
@ronyheronyhe
synchronize #15288
ronyhe:main
Status Failure
Total duration 15m 14s
Artifacts

nodejs.yml

on: pull_request
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
19s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
17s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
47s
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
TypeScript Compatibility
5m 31s
TypeScript Compatibility
Typecheck Examples and Tests
4m 1s
Typecheck Examples and Tests
Lint
1m 36s
Lint
Validate Yarn dependencies and constraints
19s
Validate Yarn dependencies and constraints
Node LTS on Ubuntu with leak detection
1m 6s
Node LTS on Ubuntu with leak detection
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 3 warnings
Lint: scripts/buildUtils.mjs#L95
Expected object keys to be in ascending order. './build/spyMatchers' should be before './build/toThrowMatchers'
Lint
Process completed with exit code 1.
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)
Should throw if watchman used with haste.enableSymlinks: e2e/Utils.ts#L158
EEXIST: file already exists, symlink 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test\symlinked-files\test.js' -> 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test\test-files\test.js' at symlinkSync (e2e/Utils.ts:158:8) at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:30:16)
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 v22.x
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