GlobalAPI: clarify key path behavior #14102
Triggered via pull request
September 20, 2024 08:52
Status
Success
Total duration
13m 34s
Artifacts
–
nodejs.yml
on: pull_request
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
15s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
18s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
45s
TypeScript Compatibility
5m 31s
Typecheck Examples and Tests
3m 57s
Lint
1m 52s
Validate Yarn dependencies and constraints
19s
Node LTS on Ubuntu with leak detection
1m 11s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
1 error and 1 warning
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)
|
macOS with shard 2/3 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
|