Skip to content

Add One Double Zero as coverage provider #14199

Add One Double Zero as coverage provider

Add One Double Zero as coverage provider #14199

Triggered via pull request October 25, 2024 12:21
Status Failure
Total duration 15m 23s
Artifacts

nodejs.yml

on: pull_request
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
14s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
24s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
1m 10s
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
TypeScript Compatibility
5m 46s
TypeScript Compatibility
Typecheck Examples and Tests
3m 47s
Typecheck Examples and Tests
Lint
1m 49s
Lint
Validate Yarn dependencies and constraints
15s
Validate Yarn dependencies and constraints
Node LTS on Ubuntu with leak detection
1m 18s
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
Validate Yarn dependencies and constraints
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)
respects testEnvironment docblock: node:internal/child_process#L511
Can't parse JSON. ERROR: SyntaxError Unexpected end of JSON input STDOUT: STDERR: node:events:496 throw er; // Unhandled 'error' event ^ Error: kill EPERM at ChildProcess.kill (node:internal/child_process:511:26) at listOnTimeout (node:internal/timers:594:17) at process.processTimers (node:internal/timers:529:7) Emitted 'error' event on ChildProcess instance at: at ChildProcess.kill (node:internal/child_process:511:12) [... lines matching original stack trace ...] at process.processTimers (node:internal/timers:529:7) { errno: -4048, code: 'EPERM', syscall: 'kill' } Node.js v22.10.0 at json (e2e/runJest.ts:157:11) at Object.<anonymous> (e2e/__tests__/testEnvironment.test.ts:14:37)
processChild › handles circular inequality properly: e2e/__tests__/nonSerializableStructuresInequality.test.ts#L36
Process exited at waitUntil (e2e/__tests__/nonSerializableStructuresInequality.test.ts:36:9) at Object.testIn2Workers (e2e/__tests__/nonSerializableStructuresInequality.test.ts:56:35)
processChild › handles circular inequality properly: undefined#L1
Timed out at timeoutKill (node_modules/execa/lib/kill.js:65:23)
processChild › handles circular inequality properly: undefined#L1
Timed out at timeoutKill (node_modules/execa/lib/kill.js:65:23)
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 v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 4/4 / Node v18.x
Attempt 1 failed. Reason: Child_process exited with error code 1