Skip to content

fix: pass resolve conditions when loading stub module #14443

fix: pass resolve conditions when loading stub module

fix: pass resolve conditions when loading stub module #14443

Triggered via pull request February 11, 2025 03:32
Status Success
Total duration 17m 13s
Artifacts

nodejs.yml

on: pull_request
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
47s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
58s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
1m 35s
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
TypeScript Compatibility
5m 44s
TypeScript Compatibility
Typecheck Examples and Tests
4m 1s
Typecheck Examples and Tests
Lint
1m 47s
Lint
Validate Yarn dependencies and constraints
20s
Validate Yarn dependencies and constraints
Node LTS on Ubuntu with leak detection
51s
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

10 errors and 12 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)
all passing › runs the tests in the correct order: e2e/__tests__/circusConcurrent.test.ts#L28
expect(received).toMatchSnapshot() Snapshot name: `all passing runs the tests in the correct order 1` - Snapshot - 2 + Received + 2 @@ -27,21 +27,21 @@ START "five" at log (__tests__/concurrent.test.js:15:11) console.log - END: "three" + END: "one" at log (__tests__/concurrent.test.js:15:11) console.log START "six" at log (__tests__/concurrent.test.js:15:11) console.log - END: "one" + END: "three" at log (__tests__/concurrent.test.js:15:11) console.log START "seven" at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:28:20)
all passing › runs the tests in the correct order: e2e/__tests__/circusConcurrent.test.ts#L28
expect(received).toMatchSnapshot() Snapshot name: `all passing runs the tests in the correct order 1` - Snapshot - 2 + Received + 2 @@ -87,16 +87,16 @@ END: "six" at log (__tests__/concurrent.test.js:15:11) console.log - END: "seven" + END: "ten" at log (__tests__/concurrent.test.js:15:11) console.log - END: "ten" + END: "seven" at log (__tests__/concurrent.test.js:15:11) console.log END: "eight" at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:28:20)
handles a bad revision for "changedSince": e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L51
expect(received).toMatchSnapshot(hint) Snapshot name: `can press "p" to filter by file name: test results 1` - Snapshot - 0 + Received + 2 PASS __tests__/bar.spec.js + A worker process has failed to exit gracefully and has been force exited. This is likely caused by tests leaking due to improper teardown. Try running with --detectOpenHandles to find leaks. Active timers can also cause this, ensure that .unref() was called on them. + PASS __tests__/foo.spec.js at Object.toMatchSnapshot (e2e/__tests__/watchModePatterns.test.ts:51:18)
all passing › runs the tests in the correct order: e2e/__tests__/circusConcurrent.test.ts#L28
expect(received).toMatchSnapshot() Snapshot name: `all passing runs the tests in the correct order 1` - Snapshot - 4 + Received + 4 @@ -67,21 +67,21 @@ START "nine" at log (__tests__/concurrent.test.js:15:11) console.log - END: "nine" + END: "five" at log (__tests__/concurrent.test.js:15:11) console.log START "ten" at log (__tests__/concurrent.test.js:15:11) console.log - END: "five" + END: "nine" at log (__tests__/concurrent.test.js:15:11) console.log END: "six" @@ -92,16 +92,16 @@ END: "seven" at log (__tests__/concurrent.test.js:15:11) console.log - END: "ten" + END: "eight" at log (__tests__/concurrent.test.js:15:11) console.log - END: "eight" + END: "ten" at log (__tests__/concurrent.test.js:15:11) console.log afterAll at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:28:20)
all passing › runs the tests in the correct order: e2e/__tests__/circusConcurrent.test.ts#L28
expect(received).toMatchSnapshot() Snapshot name: `all passing runs the tests in the correct order 1` - Snapshot - 2 + Received + 2 @@ -87,16 +87,16 @@ END: "six" at log (__tests__/concurrent.test.js:15:11) console.log - END: "seven" + END: "ten" at log (__tests__/concurrent.test.js:15:11) console.log - END: "ten" + END: "seven" at log (__tests__/concurrent.test.js:15:11) console.log END: "eight" at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:28:20)
Node crawler does not pick up symlinked files by default: e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:36:10)
Should throw if watchman used with haste.enableSymlinks: e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:15:10)
all passing › runs the tests in the correct order: e2e/__tests__/circusConcurrent.test.ts#L28
expect(received).toMatchSnapshot() Snapshot name: `all passing runs the tests in the correct order 1` - Snapshot - 2 + Received + 2 @@ -92,16 +92,16 @@ END: "seven" at log (__tests__/concurrent.test.js:15:11) console.log - END: "ten" + END: "eight" at log (__tests__/concurrent.test.js:15:11) console.log - END: "eight" + END: "ten" at log (__tests__/concurrent.test.js:15:11) console.log afterAll at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:28:20)
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
Cache not found for keys: node-cache-Linux-x64-yarn-56ba9cbbb4cfd97c4356844270814b17a0e7c7d5d814df8b8e341d60a0480f23
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
Cache not found for keys: node-cache-macOS-arm64-yarn-56ba9cbbb4cfd97c4356844270814b17a0e7c7d5d814df8b8e341d60a0480f23
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
Cache not found for keys: node-cache-Windows-x64-yarn-56ba9cbbb4cfd97c4356844270814b17a0e7c7d5d814df8b8e341d60a0480f23
macOS with shard 2/3 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
Ubuntu with shard 3/4 / Node v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Ubuntu with shard 3/4 / Node v22.x
Attempt 2 failed. Reason: Child_process exited with error code 1
Windows with shard 2/4 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 1/4 / Node v23.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 3/4 / Node v18.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 3/4 / Node v20.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 4/4 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 3/4 / Node v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1