Add --onlyFailures to documentation #13824
nodejs.yml
on: pull_request
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
13s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
19s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
46s
TypeScript Compatibility
5m 26s
Typecheck Examples and Tests
3m 58s
Lint
1m 55s
Validate Yarn dependencies and constraints
15s
Node LTS on Ubuntu with leak detection
1m 13s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
3 errors and 2 warnings
does not trigger unexpected token error message for regular syntax errors:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\unexpected-token'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/unexpectedToken.test.ts:16:24)
|
collects coverage only from multiple specified files:
e2e/__tests__/coverageReport.test.ts#L66
expect(received).toMatchSnapshot()
Snapshot name: `collects coverage only from multiple specified files 1`
- Snapshot - 7
+ Received + 0
- --------------|---------|----------|---------|---------|-------------------
- File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
- --------------|---------|----------|---------|---------|-------------------
- All files | 100 | 100 | 100 | 100 |
- file.js | 100 | 100 | 100 | 100 |
- otherFile.js | 100 | 100 | 100 | 100 |
- --------------|---------|----------|---------|---------|-------------------
at Object.toMatchSnapshot (e2e/__tests__/coverageReport.test.ts:66:18)
|
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)
|
Windows with shard 1/4 / Node v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
macOS with shard 2/3 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
|