chore(deps): update dependency graphql-request to v7 #13660
nodejs.yml
on: pull_request
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
1m 5s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
1m 49s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
1m 59s
TypeScript Compatibility
6m 13s
Typecheck Examples and Tests
4m 13s
Lint
1m 47s
Validate Yarn dependencies and constraints
14s
Node LTS on Ubuntu with leak detection
1m 5s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
4 errors and 7 warnings
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 "t" to filter by test name:
e2e/__tests__/watchModePatterns.test.ts#L70
expect(received).toMatchSnapshot(hint)
Snapshot name: `can press "t" to filter by test name: test results 2`
- Snapshot - 0
+ Received + 2
PASS __tests__/bar.spec.js
+ 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__/watchModePatterns.test.ts:70:18)
|
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 2`
- Snapshot - 0
+ Received + 1
PASS __tests__/bar.spec.js
✓ bar
› 1 snapshot updated.
+ 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 updated from 1 test suite.
at Object.toMatchSnapshot (e2e/__tests__/watchModeUpdateSnapshot.test.ts:50:18)
|
--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)
|
Node LTS on Ubuntu with coverage (4/4)
Codecov: Failed to properly create commit: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1
|
Node LTS on Ubuntu with coverage (1/4)
Codecov: Failed to properly create commit: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1
|
Node LTS on Ubuntu with coverage (3/4)
Codecov: Failed to properly create commit: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1
|
Node LTS on Ubuntu with coverage (2/4)
Codecov: Failed to properly create commit: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit 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 v20.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 2/4 / Node v20.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|