fix: refactor _importCoreModule so required core module is consistent #14463
Triggered via pull request
February 20, 2025 09:09
Status
Success
Total duration
16m 58s
Artifacts
–
nodejs.yml
on: pull_request
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
12s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
17s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
50s
TypeScript Compatibility
5m 42s
Typecheck Examples and Tests
4m 13s
Lint
1m 55s
Validate Yarn dependencies and constraints
13s
Node LTS on Ubuntu with leak detection
44s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
9 errors and 6 warnings
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)
|
can press "f" to run only failed tests:
e2e/__tests__/watchModeOnlyFailed.test.ts#L45
expect(received).toMatchSnapshot(hint)
Snapshot name: `can press "f" to run only failed tests: test results 1`
- Snapshot - 0
+ Received + 2
@@ -9,6 +9,8 @@
> 1 | test('bar 1', () => { expect('bar').toBe('foo'); });
| ^
at Object.toBe (__tests__/bar.spec.js:1:37)
+ 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__/watchModeOnlyFailed.test.ts:45: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 - 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)
|
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
@@ -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"
at Object.toMatchSnapshot (e2e/__tests__/circusConcurrent.test.ts:28:20)
|
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)
|
processChild › handles `Symbol`:
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:98:35)
|
processChild › handles `Symbol`:
undefined#L1
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
processChild › handles `Symbol`:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\bigint-inequality-test'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/nonSerializableStructuresInequality.test.ts:48:10)
|
processChild › handles `Symbol`:
undefined#L1
Timed out
at timeoutKill (node_modules/execa/lib/kill.js:65:23)
|
Ubuntu with shard 3/4 / Node v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 2/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 3/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
|
Windows with shard 4/4 / Node v18.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|