Skip to content

fix: allow Node16/NodeNext/Bundler moduleResolution in project's tsconfig #13712

fix: allow Node16/NodeNext/Bundler moduleResolution in project's tsconfig

fix: allow Node16/NodeNext/Bundler moduleResolution in project's tsconfig #13712

Triggered via pull request May 20, 2024 19:39
Status Success
Total duration 15m 23s
Artifacts

nodejs.yml

on: pull_request
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
20s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
20s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
1m 3s
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
TypeScript Compatibility
5m 29s
TypeScript Compatibility
Typecheck Examples and Tests
3m 53s
Typecheck Examples and Tests
Lint
1m 55s
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

4 errors and 4 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)
collects coverage only from specified file: e2e/__tests__/coverageReport.test.ts#L49
expect(received).toMatchSnapshot() Snapshot name: `collects coverage only from specified file 1` - Snapshot - 6 + Received + 0 - ----------|---------|----------|---------|---------|------------------- - File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s - ----------|---------|----------|---------|---------|------------------- - All files | 100 | 100 | 100 | 100 | - file.js | 100 | 100 | 100 | 100 | - ----------|---------|----------|---------|---------|------------------- at Object.toMatchSnapshot (e2e/__tests__/coverageReport.test.ts:49:18)
--findRelatedTests flag › coverage configuration is applied correctly: node:internal/child_process#L512
Could not find test summary in the output. OUTPUT: PASS __tests__/a.test.js ✓ a (4 ms) node:events:497 throw er; // Unhandled 'error' event ^ Error: kill EPERM at ChildProcess.kill (node:internal/child_process:512:26) at listOnTimeout (node:internal/timers:573:17) at processTimers (node:internal/timers:514:7) Emitted 'error' event on ChildProcess instance at: at ChildProcess.kill (node:internal/child_process:512:12) [... lines matching original stack trace ...] at processTimers (node:internal/timers:514:7) { errno: -4048, code: 'EPERM', syscall: 'kill' } Node.js v21.7.3 at extractSummary (e2e/Utils.ts:245:11) at Object.<anonymous> (e2e/__tests__/findRelatedFiles.test.ts:244:43)
should not transpile the transformer: e2e/__tests__/globalSetup.test.ts#L168
expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 at Object.toBe (e2e/__tests__/globalSetup.test.ts:168:20)
macOS with shard 2/3 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 1/4 / Node v21.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 2/4 / Node v21.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 1/4 / Node v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1