feat(runtime): use compileFunction over new Script
#14347
SimenBnodejs.yml
on: pull_request
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
13s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
20s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
53s
TypeScript Compatibility
5m 29s
Typecheck Examples and Tests
3m 35s
Lint
1m 51s
Validate Yarn dependencies and constraints
13s
Node LTS on Ubuntu with leak detection
48s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
20 errors and 45 warnings
|
check is not leaking memory:
e2e/__tests__/jestEnvironmentJsdom.test.ts#L26
expect(received).toMatch(expected)
Expected pattern: /PASS\s__tests__\/a.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:1053:18)
at Array.map (<anonymous>)·
FAIL __tests__/a.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:1053:18)
at Array.map (<anonymous>)·
Test Suites: 2 failed, 2 total
Tests: 0 total
Snapshots: 0 total
Time: 17.248 s
Ran all test suites."
at Object.toMatch (e2e/__tests__/jestEnvironmentJsdom.test.ts:26:18)
|
|
check is not leaking memory:
e2e/__tests__/jestEnvironmentJsdom.test.ts#L26
expect(received).toMatch(expected)
Expected pattern: /PASS\s__tests__\/a.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:1053:18)
at Array.map (<anonymous>)·
FAIL __tests__/a.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:1053:18)
at Array.map (<anonymous>)·
Test Suites: 2 failed, 2 total
Tests: 0 total
Snapshots: 0 total
Time: 12.238 s
Ran all test suites."
at Object.toMatch (e2e/__tests__/jestEnvironmentJsdom.test.ts:26:18)
|
|
check is not leaking memory:
e2e/__tests__/jestEnvironmentJsdom.test.ts#L26
expect(received).toMatch(expected)
Expected pattern: /PASS\s__tests__\/a.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:1053:18)
at Array.map (<anonymous>)·
FAIL __tests__/a.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:1053:18)
at Array.map (<anonymous>)·
Test Suites: 2 failed, 2 total
Tests: 0 total
Snapshots: 0 total
Time: 11.513 s
Ran all test suites."
at Object.toMatch (e2e/__tests__/jestEnvironmentJsdom.test.ts:26:18)
|
|
Ubuntu with shard 4/4 / Node v16.x
Final attempt failed. Child_process exited with error 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)
|
|
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 2`
- Snapshot - 0
+ Received + 2
PASS __tests__/bar.spec.js
✓ bar 1
✓ bar 2
+
+ 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.
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 - 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)
|
|
check is not leaking memory:
e2e/__tests__/jestEnvironmentJsdom.test.ts#L26
expect(received).toMatch(expected)
Expected pattern: /PASS\s__tests__\/a.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 (../../../../../../../Users/runner/work/jest/jest/packages/jest-core/build/index.js:1053:18)
at Array.map (<anonymous>)·
FAIL __tests__/a.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 (../../../../../../../Users/runner/work/jest/jest/packages/jest-core/build/index.js:1053:18)
at Array.map (<anonymous>)·
Test Suites: 2 failed, 2 total
Tests: 0 total
Snapshots: 0 total
Time: 11.018 s
Ran all test suites."
at Object.toMatch (e2e/__tests__/jestEnvironmentJsdom.test.ts:26:18)
|
|
check is not leaking memory:
e2e/__tests__/jestEnvironmentJsdom.test.ts#L26
expect(received).toMatch(expected)
Expected pattern: /PASS\s__tests__\/a.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 (../../../../../../../Users/runner/work/jest/jest/packages/jest-core/build/index.js:1053:18)
at Array.map (<anonymous>)·
FAIL __tests__/a.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 (../../../../../../../Users/runner/work/jest/jest/packages/jest-core/build/index.js:1053:18)
at Array.map (<anonymous>)·
Test Suites: 2 failed, 2 total
Tests: 0 total
Snapshots: 0 total
Time: 6.74 s
Ran all test suites."
at Object.toMatch (e2e/__tests__/jestEnvironmentJsdom.test.ts:26:18)
|
|
check is not leaking memory:
e2e/__tests__/jestEnvironmentJsdom.test.ts#L26
expect(received).toMatch(expected)
Expected pattern: /PASS\s__tests__\/a.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 (../../../../../../../Users/runner/work/jest/jest/packages/jest-core/build/index.js:1053:18)
at Array.map (<anonymous>)·
FAIL __tests__/a.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 (../../../../../../../Users/runner/work/jest/jest/packages/jest-core/build/index.js:1053:18)
at Array.map (<anonymous>)·
Test Suites: 2 failed, 2 total
Tests: 0 total
Snapshots: 0 total
Time: 7.146 s
Ran all test suites."
at Object.toMatch (e2e/__tests__/jestEnvironmentJsdom.test.ts:26:18)
|
|
macOS with shard 3/3 / Node v16.x
Final attempt failed. Child_process exited with error code 1
|
|
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)
|
|
Node crawler does not pick up symlinked files by default:
e2e/Utils.ts#L107
EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test '\\?\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
EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test '\\?\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)
|
|
Should throw if watchman used with haste.enableSymlinks:
e2e/Utils.ts#L107
EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test '\\?\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)
|
|
check is not leaking memory:
e2e/__tests__/jestEnvironmentJsdom.test.ts#L26
expect(received).toMatch(expected)
Expected pattern: /PASS\s__tests__\/a.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 (D:/a/jest/jest/packages/jest-core/build/index.js:1053:18)
at Array.map (<anonymous>)·
FAIL __tests__/a.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 (D:/a/jest/jest/packages/jest-core/build/index.js:1053:18)
at Array.map (<anonymous>)·
Test Suites: 2 failed, 2 total
Tests: 0 total
Snapshots: 0 total
Time: 25.292 s
Ran all test suites."
at Object.toMatch (e2e/__tests__/jestEnvironmentJsdom.test.ts:26:18)
|
|
check is not leaking memory:
e2e/__tests__/jestEnvironmentJsdom.test.ts#L26
expect(received).toMatch(expected)
Expected pattern: /PASS\s__tests__\/a.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 (D:/a/jest/jest/packages/jest-core/build/index.js:1053:18)
at Array.map (<anonymous>)·
FAIL __tests__/a.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 (D:/a/jest/jest/packages/jest-core/build/index.js:1053:18)
at Array.map (<anonymous>)·
Test Suites: 2 failed, 2 total
Tests: 0 total
Snapshots: 0 total
Time: 16.788 s
Ran all test suites."
at Object.toMatch (e2e/__tests__/jestEnvironmentJsdom.test.ts:26:18)
|
|
check is not leaking memory:
e2e/__tests__/jestEnvironmentJsdom.test.ts#L26
expect(received).toMatch(expected)
Expected pattern: /PASS\s__tests__\/a.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 (D:/a/jest/jest/packages/jest-core/build/index.js:1053:18)
at Array.map (<anonymous>)·
FAIL __tests__/a.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 (D:/a/jest/jest/packages/jest-core/build/index.js:1053:18)
at Array.map (<anonymous>)·
Test Suites: 2 failed, 2 total
Tests: 0 total
Snapshots: 0 total
Time: 18.282 s
Ran all test suites."
at Object.toMatch (e2e/__tests__/jestEnvironmentJsdom.test.ts:26:18)
|
|
Windows with shard 4/4 / Node v16.x
Final attempt failed. Child_process exited with error code 1
|
|
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Validate Yarn dependencies and constraints
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Node LTS on Ubuntu with leak detection
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Lint
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 1/4 / Node v23.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 1/4 / Node v22.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 1/4 / Node v20.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 1/4 / Node v18.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Node LTS on Ubuntu with coverage (1/4)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 1/4 / Node LTS using jest-jasmine2
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 1/4 / Node v16.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Node LTS on Ubuntu with coverage (4/4)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Node LTS on Ubuntu with coverage (3/4)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 2/4 / Node LTS using jest-jasmine2
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Node LTS on Ubuntu with coverage (2/4)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 2/4 / Node v22.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 2/4 / Node v20.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 2/4 / Node v16.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 2/4 / Node v18.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 2/4 / Node v23.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 3/4 / Node LTS using jest-jasmine2
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Typecheck Examples and Tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 3/4 / Node v22.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 3/4 / Node v23.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 3/4 / Node v18.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 4/4 / Node v23.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 4/4 / Node v22.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 3/4 / Node v20.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 4/4 / Node v20.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 3/4 / Node v16.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 4/4 / Node v18.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 4/4 / Node LTS using jest-jasmine2
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
TypeScript Compatibility
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 4/4 / Node v16.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Ubuntu with shard 4/4 / Node v16.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Ubuntu with shard 4/4 / Node v16.x
Attempt 2 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 1/4 / Node v16.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 3/3 / Node v16.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
macOS with shard 3/3 / Node v16.x
Attempt 2 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 4/4 / Node v23.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Windows with shard 4/4 / Node v16.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
Windows with shard 4/4 / Node v16.x
Attempt 2 failed. Reason: Child_process exited with error code 1
|