feat(runtime): use compileFunction over new Script
#14346
Triggered via pull request
January 16, 2025 11:48
SimenB
Status
Cancelled
Total duration
9m 52s
Artifacts
–
nodejs.yml
on: pull_request
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
19s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
22s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
1m 12s
TypeScript Compatibility
5m 35s
Typecheck Examples and Tests
3m 56s
Lint
1m 45s
Validate Yarn dependencies and constraints
13s
Node LTS on Ubuntu with leak detection
49s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
57 errors and 38 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: 16.883 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.623 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.679 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
|
|
macOS with shard 3/3 / Node v23.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
macOS with shard 3/3 / Node v16.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
macOS with shard 3/3 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
macOS with shard 3/3 / Node v18.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
macOS with shard 3/3 / Node v20.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
macOS with shard 3/3 / Node LTS using jest-jasmine2
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
Windows with shard 4/4 / Node v18.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
Windows with shard 4/4 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
Windows with shard 4/4 / Node v23.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
Windows with shard 4/4 / Node v20.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
Windows with shard 1/4 / Node v16.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
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)
|
|
Windows with shard 1/4 / Node v16.x
The operation was canceled.
|
|
Windows with shard 2/4 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
Windows with shard 2/4 / Node v22.x
The operation was canceled.
|
|
macOS with shard 2/3 / Node LTS using jest-jasmine2
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
macOS with shard 2/3 / Node LTS using jest-jasmine2
The operation was canceled.
|
|
Windows with shard 2/4 / Node v16.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
Windows with shard 2/4 / Node v16.x
The operation was canceled.
|
|
Windows with shard 3/4 / Node LTS using jest-jasmine2
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
Windows with shard 3/4 / Node LTS using jest-jasmine2
The operation was canceled.
|
|
Windows with shard 2/4 / Node v18.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
Windows with shard 2/4 / Node v18.x
The operation was canceled.
|
|
Windows with shard 3/4 / Node v18.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
Windows with shard 3/4 / Node v18.x
The operation was canceled.
|
|
Windows with shard 3/4 / Node v23.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
Windows with shard 3/4 / Node v23.x
The operation was canceled.
|
|
macOS with shard 2/3 / Node v20.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
macOS with shard 2/3 / Node v20.x
The operation was canceled.
|
|
macOS with shard 2/3 / Node v23.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
macOS with shard 2/3 / Node v23.x
The operation was canceled.
|
|
Windows with shard 3/4 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
Windows with shard 3/4 / Node v22.x
The operation was canceled.
|
|
macOS with shard 2/3 / Node v18.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
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)
|
|
macOS with shard 2/3 / Node v18.x
The operation was canceled.
|
|
Windows with shard 4/4 / Node LTS using jest-jasmine2
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
Windows with shard 4/4 / Node LTS using jest-jasmine2
The operation was canceled.
|
|
Windows with shard 3/4 / Node v20.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
Windows with shard 3/4 / Node v20.x
The operation was canceled.
|
|
Windows with shard 2/4 / Node LTS using jest-jasmine2
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
--findRelatedTests flag › coverage configuration is applied correctly:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\find-related-tests-test'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/findRelatedFiles.test.ts:16:24)
|
|
Windows with shard 2/4 / Node v23.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
Windows with shard 2/4 / Node v23.x
The operation was canceled.
|
|
Windows with shard 2/4 / Node LTS using jest-jasmine2
The operation was canceled.
|
|
Windows with shard 2/4 / Node v20.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
Windows with shard 2/4 / Node v20.x
The operation was canceled.
|
|
Windows with shard 3/4 / Node v16.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
Windows with shard 3/4 / Node v16.x
The operation was canceled.
|
|
macOS with shard 2/3 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
macOS with shard 2/3 / Node v22.x
The operation was canceled.
|
|
Windows with shard 4/4 / Node v16.x
Canceling since a higher priority waiting request for 'Node CI-use-compile-function' exists
|
|
Windows with shard 4/4 / Node v16.x
The operation was canceled.
|
|
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
|
|
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
|
|
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 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 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 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 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 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
|
|
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 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
|
|
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
|
|
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 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 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 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 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 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
|
|
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 v18.x
Attempt 1 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
|