Property 'wrapperLength' does not exist on type 'TransformResult'.

Process completed with exit code 1.

Property 'wrapperLength' does not exist on type 'TransformResult'.

Process completed with exit code 1.

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)

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: 16.548 s Ran all test suites." at Object.toMatch (e2e/__tests__/jestEnvironmentJsdom.test.ts:26:18)

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.27 s Ran all test suites." at Object.toMatch (e2e/__tests__/jestEnvironmentJsdom.test.ts:26:18)

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.049 s Ran all test suites." at Object.toMatch (e2e/__tests__/jestEnvironmentJsdom.test.ts:26:18)

Final attempt failed. Child_process exited with error code 1

RPC failed; curl 92 HTTP/2 stream 3 was not closed cleanly: CANCEL (err 8)

40 bytes of body are still expected

early EOF

fetch-pack: invalid index-pack output

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)

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)

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: 17.058 s Ran all test suites." at Object.toMatch (e2e/__tests__/jestEnvironmentJsdom.test.ts:26:18)

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: 9.589 s Ran all test suites." at Object.toMatch (e2e/__tests__/jestEnvironmentJsdom.test.ts:26:18)

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: 9.394 s Ran all test suites." at Object.toMatch (e2e/__tests__/jestEnvironmentJsdom.test.ts:26:18)

Final attempt failed. Child_process exited with error code 1

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)

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)

expect(received).toMatchSnapshot() Snapshot name: `all passing runs the tests in the correct order 1` - Snapshot - 3 + Received + 3 @@ -82,21 +82,21 @@ END: "five" at log (__tests__/concurrent.test.js:15:11) console.log - END: "six" + END: "ten" at log (__tests__/concurrent.test.js:15:11) console.log - END: "seven" + END: "six" 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)

Final attempt failed. Child_process exited with error code 1

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: 23.146 s Ran all test suites." at Object.toMatch (e2e/__tests__/jestEnvironmentJsdom.test.ts:26:18)

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.949 s Ran all test suites." at Object.toMatch (e2e/__tests__/jestEnvironmentJsdom.test.ts:26:18)

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.009 s Ran all test suites." at Object.toMatch (e2e/__tests__/jestEnvironmentJsdom.test.ts:26:18)

Final attempt failed. Child_process exited with error code 1

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Attempt 1 failed. Reason: Child_process exited with error code 1

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Attempt 1 failed. Reason: Child_process exited with error code 1

Attempt 2 failed. Reason: Child_process exited with error code 1

Attempt 1 failed. Reason: Child_process exited with error code 1

Attempt 1 failed. Reason: Child_process exited with error code 1

Attempt 1 failed. Reason: Child_process exited with error code 1

Attempt 2 failed. Reason: Child_process exited with error code 1

Attempt 1 failed. Reason: Child_process exited with error code 1

Attempt 2 failed. Reason: Child_process exited with error code 1

Attempt 1 failed. Reason: Child_process exited with error code 1