Skip to content

ci: enable pkg-pr-new workflow (#15655) #14797

ci: enable pkg-pr-new workflow (#15655)

ci: enable pkg-pr-new workflow (#15655) #14797

Triggered via push June 5, 2025 07:22
Status Success
Total duration 25m 0s
Artifacts

nodejs.yml

on: push
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
50s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
57s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
1m 20s
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
TypeScript Compatibility
5m 52s
TypeScript Compatibility
Typecheck Examples and Tests
4m 17s
Typecheck Examples and Tests
Lint
1m 47s
Lint
Validate Yarn dependencies and constraints
13s
Validate Yarn dependencies and constraints
Node LTS on Ubuntu with leak detection
46s
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

2 errors and 4 warnings
check is not leaking memory: e2e/__tests__/jestEnvironmentJsdom.test.ts#L27
expect(received).toMatch(expected) Expected pattern: /PASS\s__tests__\/b.test.js/ Received string: "FAIL __tests__/b.test.js ● Test suite failed to run· EXPERIMENTAL FEATURE! Your test suite is leaking memory. Please ensure all references are cleaned.· There is a number of things that can leak memory: - Async operations that have not finished (e.g. fs.readFile). - Timers not properly mocked (e.g. setInterval, setTimeout). - Keeping references to the global scope.· at onResult (../../home/runner/work/jest/jest/packages/jest-core/build/index.js:1061:18) at Array.map (<anonymous>)· PASS __tests__/a.test.js ● Console· console.log a· at Object.log (__tests__/a.test.js:1:25)·· Test Suites: 1 failed, 1 passed, 2 total Tests: 1 passed, 1 total Snapshots: 0 total Time: 3.303 s Ran all test suites." at Object.toMatch (e2e/__tests__/jestEnvironmentJsdom.test.ts:27: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)
Node LTS on Ubuntu with coverage (4/4)
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
macOS with shard 3/3 / Node v24.x
Attempt 2 failed. Reason: Child_process exited with error code 1
macOS with shard 3/3 / Node v24.x
Attempt 1 failed. Reason: Child_process exited with error code 1