feat(CLI): --maxRelatedTestsDepth flag to control the depth of related test in --findRelatedTests #14433
Triggered via pull request
February 8, 2025 06:12
Status
Cancelled
Total duration
9m 44s
Artifacts
–
nodejs.yml
on: pull_request
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
21s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
18s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
1m 16s
TypeScript Compatibility
5m 32s
Typecheck Examples and Tests
4m 10s
Lint
1m 38s
Validate Yarn dependencies and constraints
17s
Node LTS on Ubuntu with leak detection
46s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
102 errors and 20 warnings
Lint:
e2e/__tests__/findRelatedFiles.test.ts#L276
Strings must use singlequote
|
Lint:
e2e/__tests__/findRelatedFiles.test.ts#L277
Strings must use singlequote
|
Lint:
e2e/__tests__/findRelatedFiles.test.ts#L278
Strings must use singlequote
|
Lint:
e2e/__tests__/findRelatedFiles.test.ts#L279
Strings must use singlequote
|
Lint:
e2e/__tests__/findRelatedFiles.test.ts#L280
Strings must use singlequote
|
Lint:
e2e/__tests__/findRelatedFiles.test.ts#L286
Replace `·jest:·{·testEnvironment:·'node'·}·` with `jest:·{testEnvironment:·'node'}`
|
|
Lint:
e2e/__tests__/findRelatedFiles.test.ts#L289
Replace `·stderr·}·=·runJest(DIR,·[`--maxRelatedTestsDepth=${depth}`,·'--findRelatedTests',·'a.js'` with `stderr}·=·runJest(DIR,·[⏎········`--maxRelatedTestsDepth=${depth}`,⏎········'--findRelatedTests',⏎········'a.js',⏎······`
|
|
Lint:
e2e/__tests__/findRelatedFiles.test.ts#L291
Use `for…of` instead of `.forEach(…)`
|
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)
|
on node >=23.6 › invalid JS in jest.config.ts (node with native TS support):
e2e/__tests__/jest.config.ts.test.ts#L158
expect(received).toMatchSnapshot()
Snapshot name: `on node >=23.6 invalid JS in jest.config.ts (node with native TS support) 1`
- Snapshot - 11
+ Received + 0
- Error: Jest: Failed to parse the TypeScript config file <<REPLACED>>
- SyntaxError [ERR_INVALID_TYPESCRIPT_SYNTAX]: x Expected ';', got 'string literal (ll break this file yo, 'll break this file yo)'
- ,----
- 1 | export default i'll break this file yo
- : ^^^^^^^^^^^^^^^^^^^^^^
- `----
- x Unterminated string constant
- ,----
- 1 | export default i'll break this file yo
- : ^^^^^^^^^^^^^^^^^^^^^^
- `----
at Object.toMatchSnapshot (e2e/__tests__/jest.config.ts.test.ts:158:7)
|
on node >=23.6 › invalid JS in jest.config.ts (node with native TS support):
e2e/__tests__/jest.config.ts.test.ts#L158
expect(received).toMatchSnapshot()
Snapshot name: `on node >=23.6 invalid JS in jest.config.ts (node with native TS support) 1`
- Snapshot - 11
+ Received + 0
- Error: Jest: Failed to parse the TypeScript config file <<REPLACED>>
- SyntaxError [ERR_INVALID_TYPESCRIPT_SYNTAX]: x Expected ';', got 'string literal (ll break this file yo, 'll break this file yo)'
- ,----
- 1 | export default i'll break this file yo
- : ^^^^^^^^^^^^^^^^^^^^^^
- `----
- x Unterminated string constant
- ,----
- 1 | export default i'll break this file yo
- : ^^^^^^^^^^^^^^^^^^^^^^
- `----
at Object.toMatchSnapshot (e2e/__tests__/jest.config.ts.test.ts:158:7)
|
on node >=23.6 › invalid JS in jest.config.ts (node with native TS support):
e2e/__tests__/jest.config.ts.test.ts#L158
expect(received).toMatchSnapshot()
Snapshot name: `on node >=23.6 invalid JS in jest.config.ts (node with native TS support) 1`
- Snapshot - 11
+ Received + 0
- Error: Jest: Failed to parse the TypeScript config file <<REPLACED>>
- SyntaxError [ERR_INVALID_TYPESCRIPT_SYNTAX]: x Expected ';', got 'string literal (ll break this file yo, 'll break this file yo)'
- ,----
- 1 | export default i'll break this file yo
- : ^^^^^^^^^^^^^^^^^^^^^^
- `----
- x Unterminated string constant
- ,----
- 1 | export default i'll break this file yo
- : ^^^^^^^^^^^^^^^^^^^^^^
- `----
at Object.toMatchSnapshot (e2e/__tests__/jest.config.ts.test.ts:158:7)
|
Ubuntu with shard 1/4 / Node v23.x
Final attempt failed. Child_process exited with error code 1
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
Node LTS on Ubuntu with coverage (4/4)
Final attempt failed. Child_process exited with error code 1
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
macOS with shard 3/3 / Node LTS using jest-jasmine2
Final attempt failed. Child_process exited with error code 1
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
Ubuntu with shard 4/4 / Node LTS using jest-jasmine2
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-maxRelatedTestsDepth' exists
|
Windows with shard 2/4 / Node v23.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
Windows with shard 2/4 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
Windows with shard 3/4 / Node v20.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
Windows with shard 3/4 / Node v18.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
Windows with shard 3/4 / Node v23.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
Windows with shard 3/4 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
Windows with shard 4/4 / Node v16.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
Windows with shard 3/4 / Node v16.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
Windows with shard 3/4 / Node LTS using jest-jasmine2
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
Windows with shard 4/4 / Node v18.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
Windows with shard 4/4 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
Windows with shard 4/4 / Node v20.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
Windows with shard 4/4 / Node v23.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
Windows with shard 4/4 / Node LTS using jest-jasmine2
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
Ubuntu with shard 4/4 / Node v16.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
Ubuntu with shard 4/4 / Node v16.x
The operation was canceled.
|
Ubuntu with shard 4/4 / Node v18.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
Ubuntu with shard 4/4 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
Ubuntu with shard 4/4 / Node v18.x
The operation was canceled.
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
Ubuntu with shard 4/4 / Node v22.x
The operation was canceled.
|
macOS with shard 3/3 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
macOS with shard 3/3 / Node v22.x
The operation was canceled.
|
Windows with shard 2/4 / Node v20.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
Windows with shard 1/4 / Node LTS using jest-jasmine2
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
Windows with shard 2/4 / Node v20.x
A task was canceled.
|
Windows with shard 1/4 / Node LTS using jest-jasmine2
The operation was canceled.
|
Ubuntu with shard 4/4 / Node v23.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
Ubuntu with shard 4/4 / Node v23.x
The operation was canceled.
|
Windows with shard 2/4 / Node v18.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
Windows with shard 2/4 / Node v18.x
The operation was canceled.
|
Windows with shard 1/4 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
can press "u" to update snapshots:
e2e/__tests__/watchModeUpdateSnapshot.test.ts#L50
expect(received).toMatchSnapshot(hint)
Snapshot name: `can press "u" to update snapshots: test results 1`
- Snapshot - 0
+ Received + 1
@@ -14,7 +14,8 @@
| ^
at Object.toMatchSnapshot (__tests__/bar.spec.js:1:35)
› 1 snapshot failed.
+ 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.
Snapshot Summary
› 1 snapshot failed from 1 test suite. Inspect your code changes or press `u` to update them."
at Object.toMatchSnapshot (e2e/__tests__/watchModeUpdateSnapshot.test.ts:50:18)
|
Windows with shard 1/4 / Node v22.x
The operation was canceled.
|
macOS with shard 3/3 / Node v18.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
macOS with shard 3/3 / Node v18.x
The operation was canceled.
|
Windows with shard 1/4 / Node v18.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
Windows with shard 1/4 / Node v18.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-maxRelatedTestsDepth' exists
|
Windows with shard 2/4 / Node LTS using jest-jasmine2
The operation was canceled.
|
macOS with shard 3/3 / Node v20.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
macOS with shard 3/3 / Node v20.x
The operation was canceled.
|
Windows with shard 2/4 / Node v16.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
Windows with shard 2/4 / Node v16.x
The operation was canceled.
|
macOS with shard 1/3 / Node v23.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
on node >=23.6 › invalid JS in jest.config.ts (node with native TS support):
e2e/__tests__/jest.config.ts.test.ts#L158
expect(received).toMatchSnapshot()
Snapshot name: `on node >=23.6 invalid JS in jest.config.ts (node with native TS support) 1`
- Snapshot - 11
+ Received + 0
- Error: Jest: Failed to parse the TypeScript config file <<REPLACED>>
- SyntaxError [ERR_INVALID_TYPESCRIPT_SYNTAX]: x Expected ';', got 'string literal (ll break this file yo, 'll break this file yo)'
- ,----
- 1 | export default i'll break this file yo
- : ^^^^^^^^^^^^^^^^^^^^^^
- `----
- x Unterminated string constant
- ,----
- 1 | export default i'll break this file yo
- : ^^^^^^^^^^^^^^^^^^^^^^
- `----
at Object.toMatchSnapshot (e2e/__tests__/jest.config.ts.test.ts:158:7)
|
on node >=23.6 › invalid JS in jest.config.ts (node with native TS support):
e2e/__tests__/jest.config.ts.test.ts#L158
expect(received).toMatchSnapshot()
Snapshot name: `on node >=23.6 invalid JS in jest.config.ts (node with native TS support) 1`
- Snapshot - 11
+ Received + 0
- Error: Jest: Failed to parse the TypeScript config file <<REPLACED>>
- SyntaxError [ERR_INVALID_TYPESCRIPT_SYNTAX]: x Expected ';', got 'string literal (ll break this file yo, 'll break this file yo)'
- ,----
- 1 | export default i'll break this file yo
- : ^^^^^^^^^^^^^^^^^^^^^^
- `----
- x Unterminated string constant
- ,----
- 1 | export default i'll break this file yo
- : ^^^^^^^^^^^^^^^^^^^^^^
- `----
at Object.toMatchSnapshot (e2e/__tests__/jest.config.ts.test.ts:158:7)
|
on node >=23.6 › invalid JS in jest.config.ts (node with native TS support):
e2e/__tests__/jest.config.ts.test.ts#L158
expect(received).toMatchSnapshot()
Snapshot name: `on node >=23.6 invalid JS in jest.config.ts (node with native TS support) 1`
- Snapshot - 11
+ Received + 0
- Error: Jest: Failed to parse the TypeScript config file <<REPLACED>>
- SyntaxError [ERR_INVALID_TYPESCRIPT_SYNTAX]: x Expected ';', got 'string literal (ll break this file yo, 'll break this file yo)'
- ,----
- 1 | export default i'll break this file yo
- : ^^^^^^^^^^^^^^^^^^^^^^
- `----
- x Unterminated string constant
- ,----
- 1 | export default i'll break this file yo
- : ^^^^^^^^^^^^^^^^^^^^^^
- `----
at Object.toMatchSnapshot (e2e/__tests__/jest.config.ts.test.ts:158:7)
|
Ubuntu with shard 4/4 / Node v20.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
macOS with shard 1/3 / Node v23.x
The operation was canceled.
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
Ubuntu with shard 4/4 / Node v20.x
The operation was canceled.
|
macOS with shard 3/3 / Node v16.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
prints the config object:
undefined#L1
expect(received).toMatchSnapshot()
Snapshot name: `prints the config object 1`
- Snapshot - 0
+ Received + 1
@@ -97,10 +97,11 @@
"json": false,
"lastCommit": false,
"listTests": false,
"logHeapUsage": false,
"maxConcurrency": 5,
+ "maxRelatedTestsDepth": null,
"maxWorkers": 2,
"noStackTrace": false,
"nonFlagArgs": [],
"notify": false,
"notifyMode": "failure-change",
at Object.toMatchSnapshot (packages/jest-core/src/lib/__tests__/logDebugMessages.test.ts:64:19)
|
macOS with shard 3/3 / Node v16.x
The operation was canceled.
|
Windows with shard 1/4 / Node v23.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
on node >=23.6 › invalid JS in jest.config.ts (node with native TS support):
e2e/__tests__/jest.config.ts.test.ts#L158
expect(received).toMatchSnapshot()
Snapshot name: `on node >=23.6 invalid JS in jest.config.ts (node with native TS support) 1`
- Snapshot - 11
+ Received + 0
- Error: Jest: Failed to parse the TypeScript config file <<REPLACED>>
- SyntaxError [ERR_INVALID_TYPESCRIPT_SYNTAX]: x Expected ';', got 'string literal (ll break this file yo, 'll break this file yo)'
- ,----
- 1 | export default i'll break this file yo
- : ^^^^^^^^^^^^^^^^^^^^^^
- `----
- x Unterminated string constant
- ,----
- 1 | export default i'll break this file yo
- : ^^^^^^^^^^^^^^^^^^^^^^
- `----
at Object.toMatchSnapshot (e2e/__tests__/jest.config.ts.test.ts:158:7)
|
Windows with shard 1/4 / Node v23.x
The operation was canceled.
|
Windows with shard 1/4 / Node v20.x
Canceling since a higher priority waiting request for 'Node CI-maxRelatedTestsDepth' exists
|
Windows with shard 1/4 / Node v20.x
The operation was canceled.
|
macOS with shard 2/3 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Ubuntu with shard 1/4 / Node v23.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Ubuntu with shard 1/4 / Node v23.x
Attempt 2 failed. Reason: Child_process exited with error code 1
|
Node LTS on Ubuntu with coverage (4/4)
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Node LTS on Ubuntu with coverage (4/4)
Attempt 2 failed. Reason: Child_process exited with error code 1
|
macOS with shard 3/3 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
|
macOS with shard 3/3 / Node LTS using jest-jasmine2
Attempt 2 failed. Reason: Child_process exited with error code 1
|
Ubuntu with shard 4/4 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Ubuntu with shard 4/4 / Node LTS using jest-jasmine2
Attempt 2 failed. Reason: Child_process exited with error code 1
|
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
|
Ubuntu with shard 4/4 / Node v18.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Ubuntu with shard 4/4 / Node v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Ubuntu with shard 4/4 / Node v22.x
Attempt 2 failed. Reason: Child_process exited with error code 1
|
Ubuntu with shard 4/4 / Node v23.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Ubuntu with shard 4/4 / Node v23.x
Attempt 2 failed. Reason: Child_process exited with error code 1
|
macOS with shard 1/3 / Node v23.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
macOS with shard 1/3 / Node v23.x
Attempt 2 failed. Reason: Child_process exited with error code 1
|
Ubuntu with shard 4/4 / Node v20.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Ubuntu with shard 4/4 / Node v20.x
Attempt 2 failed. Reason: Child_process exited with error code 1
|