Skip to content

chore: update eslint-plugin-unicorn #14158

chore: update eslint-plugin-unicorn

chore: update eslint-plugin-unicorn #14158

Triggered via pull request October 4, 2024 07:30
Status Failure
Total duration 17m 9s
Artifacts

nodejs.yml

on: pull_request
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
52s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
1m 18s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
1m 21s
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
TypeScript Compatibility
5m 35s
TypeScript Compatibility
Typecheck Examples and Tests
4m 6s
Typecheck Examples and Tests
Lint
1m 47s
Lint
Validate Yarn dependencies and constraints
16s
Validate Yarn dependencies and constraints
Node LTS on Ubuntu with leak detection
1m 12s
Node LTS on Ubuntu with leak detection
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Fit to window
Zoom out
Zoom in

Annotations

49 errors and 21 warnings
Wrong globals for environment › on node <=18 › print useful error for navigator: e2e/__tests__/wrongEnv.test.ts#L15
expect(received).toMatchSnapshot() Snapshot name: `Wrong globals for environment on node <=18 print useful error for navigator 1` - Snapshot - 7 + Received + 7 @@ -8,14 +8,14 @@ The error below may be caused by using the wrong test environment, see https://jestjs.io/docs/configuration#testenvironment-string. Consider using the "jsdom" test environment. ReferenceError: navigator is not defined - 30 | + 31 | - 31 | test('use navigator', () => { + 32 | test('use navigator', () => { - > 32 | const userAgent = navigator.userAgent; + > 33 | const userAgent = navigator.userAgent; | ^ - 33 | + 34 | - 34 | console.log(userAgent); + 35 | console.log(userAgent); - 35 | + 36 | - at Object.navigator (__tests__/node.js:32:21)" + at Object.navigator (__tests__/node.js:33:21)" at toMatchSnapshot (e2e/__tests__/wrongEnv.test.ts:15:46) at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:30:7)
Wrong globals for environment › on node <=18 › print useful error for navigator: e2e/__tests__/wrongEnv.test.ts#L15
expect(received).toMatchSnapshot() Snapshot name: `Wrong globals for environment on node <=18 print useful error for navigator 1` - Snapshot - 7 + Received + 7 @@ -8,14 +8,14 @@ The error below may be caused by using the wrong test environment, see https://jestjs.io/docs/configuration#testenvironment-string. Consider using the "jsdom" test environment. ReferenceError: navigator is not defined - 30 | + 31 | - 31 | test('use navigator', () => { + 32 | test('use navigator', () => { - > 32 | const userAgent = navigator.userAgent; + > 33 | const userAgent = navigator.userAgent; | ^ - 33 | + 34 | - 34 | console.log(userAgent); + 35 | console.log(userAgent); - 35 | + 36 | - at Object.navigator (__tests__/node.js:32:21)" + at Object.navigator (__tests__/node.js:33:21)" at toMatchSnapshot (e2e/__tests__/wrongEnv.test.ts:15:46) at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:30:7)
Wrong globals for environment › on node <=18 › print useful error for navigator: e2e/__tests__/wrongEnv.test.ts#L15
expect(received).toMatchSnapshot() Snapshot name: `Wrong globals for environment on node <=18 print useful error for navigator 1` - Snapshot - 7 + Received + 7 @@ -8,14 +8,14 @@ The error below may be caused by using the wrong test environment, see https://jestjs.io/docs/configuration#testenvironment-string. Consider using the "jsdom" test environment. ReferenceError: navigator is not defined - 30 | + 31 | - 31 | test('use navigator', () => { + 32 | test('use navigator', () => { - > 32 | const userAgent = navigator.userAgent; + > 33 | const userAgent = navigator.userAgent; | ^ - 33 | + 34 | - 34 | console.log(userAgent); + 35 | console.log(userAgent); - 35 | + 36 | - at Object.navigator (__tests__/node.js:32:21)" + at Object.navigator (__tests__/node.js:33:21)" at toMatchSnapshot (e2e/__tests__/wrongEnv.test.ts:15:46) at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:30:7)
Ubuntu with shard 2/4 / Node v18.x
Final attempt failed. Child_process exited with error code 1
Wrong globals for environment › on node <=18 › print useful error for navigator: e2e/__tests__/wrongEnv.test.ts#L15
expect(received).toMatchSnapshot() Snapshot name: `Wrong globals for environment on node <=18 print useful error for navigator 1` - Snapshot - 7 + Received + 7 @@ -8,14 +8,14 @@ The error below may be caused by using the wrong test environment, see https://jestjs.io/docs/configuration#testenvironment-string. Consider using the "jsdom" test environment. ReferenceError: navigator is not defined - 30 | + 31 | - 31 | test('use navigator', () => { + 32 | test('use navigator', () => { - > 32 | const userAgent = navigator.userAgent; + > 33 | const userAgent = navigator.userAgent; | ^ - 33 | + 34 | - 34 | console.log(userAgent); + 35 | console.log(userAgent); - 35 | + 36 | - at Object.navigator (__tests__/node.js:32:21)" + at Object.navigator (__tests__/node.js:33:21)" at toMatchSnapshot (e2e/__tests__/wrongEnv.test.ts:15:46) at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:30:7)
Wrong globals for environment › on node <=18 › print useful error for navigator: e2e/__tests__/wrongEnv.test.ts#L15
expect(received).toMatchSnapshot() Snapshot name: `Wrong globals for environment on node <=18 print useful error for navigator 1` - Snapshot - 7 + Received + 7 @@ -8,14 +8,14 @@ The error below may be caused by using the wrong test environment, see https://jestjs.io/docs/configuration#testenvironment-string. Consider using the "jsdom" test environment. ReferenceError: navigator is not defined - 30 | + 31 | - 31 | test('use navigator', () => { + 32 | test('use navigator', () => { - > 32 | const userAgent = navigator.userAgent; + > 33 | const userAgent = navigator.userAgent; | ^ - 33 | + 34 | - 34 | console.log(userAgent); + 35 | console.log(userAgent); - 35 | + 36 | - at Object.navigator (__tests__/node.js:32:21)" + at Object.navigator (__tests__/node.js:33:21)" at toMatchSnapshot (e2e/__tests__/wrongEnv.test.ts:15:46) at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:30:7)
Wrong globals for environment › on node <=18 › print useful error for navigator: e2e/__tests__/wrongEnv.test.ts#L15
expect(received).toMatchSnapshot() Snapshot name: `Wrong globals for environment on node <=18 print useful error for navigator 1` - Snapshot - 7 + Received + 7 @@ -8,14 +8,14 @@ The error below may be caused by using the wrong test environment, see https://jestjs.io/docs/configuration#testenvironment-string. Consider using the "jsdom" test environment. ReferenceError: navigator is not defined - 30 | + 31 | - 31 | test('use navigator', () => { + 32 | test('use navigator', () => { - > 32 | const userAgent = navigator.userAgent; + > 33 | const userAgent = navigator.userAgent; | ^ - 33 | + 34 | - 34 | console.log(userAgent); + 35 | console.log(userAgent); - 35 | + 36 | - at Object.navigator (__tests__/node.js:32:21)" + at Object.navigator (__tests__/node.js:33:21)" at toMatchSnapshot (e2e/__tests__/wrongEnv.test.ts:15:46) at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:30:7)
Ubuntu with shard 2/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)
Wrong globals for environment › on node <=18 › print useful error for navigator: e2e/__tests__/wrongEnv.test.ts#L15
expect(received).toMatchSnapshot() Snapshot name: `Wrong globals for environment on node <=18 print useful error for navigator 1` - Snapshot - 7 + Received + 7 @@ -8,14 +8,14 @@ The error below may be caused by using the wrong test environment, see https://jestjs.io/docs/configuration#testenvironment-string. Consider using the "jsdom" test environment. ReferenceError: navigator is not defined - 30 | + 31 | - 31 | test('use navigator', () => { + 32 | test('use navigator', () => { - > 32 | const userAgent = navigator.userAgent; + > 33 | const userAgent = navigator.userAgent; | ^ - 33 | + 34 | - 34 | console.log(userAgent); + 35 | console.log(userAgent); - 35 | + 36 | - at Object.navigator (__tests__/node.js:32:21)" + at Object.navigator (__tests__/node.js:33:21)" at toMatchSnapshot (e2e/__tests__/wrongEnv.test.ts:15:46) at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:30:7)
Wrong globals for environment › on node <=18 › print useful error for navigator: e2e/__tests__/wrongEnv.test.ts#L15
expect(received).toMatchSnapshot() Snapshot name: `Wrong globals for environment on node <=18 print useful error for navigator 1` - Snapshot - 7 + Received + 7 @@ -8,14 +8,14 @@ The error below may be caused by using the wrong test environment, see https://jestjs.io/docs/configuration#testenvironment-string. Consider using the "jsdom" test environment. ReferenceError: navigator is not defined - 30 | + 31 | - 31 | test('use navigator', () => { + 32 | test('use navigator', () => { - > 32 | const userAgent = navigator.userAgent; + > 33 | const userAgent = navigator.userAgent; | ^ - 33 | + 34 | - 34 | console.log(userAgent); + 35 | console.log(userAgent); - 35 | + 36 | - at Object.navigator (__tests__/node.js:32:21)" + at Object.navigator (__tests__/node.js:33:21)" at toMatchSnapshot (e2e/__tests__/wrongEnv.test.ts:15:46) at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:30:7)
Wrong globals for environment › on node <=18 › print useful error for navigator: e2e/__tests__/wrongEnv.test.ts#L15
expect(received).toMatchSnapshot() Snapshot name: `Wrong globals for environment on node <=18 print useful error for navigator 1` - Snapshot - 7 + Received + 7 @@ -8,14 +8,14 @@ The error below may be caused by using the wrong test environment, see https://jestjs.io/docs/configuration#testenvironment-string. Consider using the "jsdom" test environment. ReferenceError: navigator is not defined - 30 | + 31 | - 31 | test('use navigator', () => { + 32 | test('use navigator', () => { - > 32 | const userAgent = navigator.userAgent; + > 33 | const userAgent = navigator.userAgent; | ^ - 33 | + 34 | - 34 | console.log(userAgent); + 35 | console.log(userAgent); - 35 | + 36 | - at Object.navigator (__tests__/node.js:32:21)" + at Object.navigator (__tests__/node.js:33:21)" at toMatchSnapshot (e2e/__tests__/wrongEnv.test.ts:15:46) at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:30:7)
macOS with shard 1/3 / Node v16.x
Final attempt failed. Child_process exited with error code 1
Wrong globals for environment › on node <=18 › print useful error for navigator: e2e/__tests__/wrongEnv.test.ts#L15
expect(received).toMatchSnapshot() Snapshot name: `Wrong globals for environment on node <=18 print useful error for navigator 1` - Snapshot - 7 + Received + 7 @@ -8,14 +8,14 @@ The error below may be caused by using the wrong test environment, see https://jestjs.io/docs/configuration#testenvironment-string. Consider using the "jsdom" test environment. ReferenceError: navigator is not defined - 30 | + 31 | - 31 | test('use navigator', () => { + 32 | test('use navigator', () => { - > 32 | const userAgent = navigator.userAgent; + > 33 | const userAgent = navigator.userAgent; | ^ - 33 | + 34 | - 34 | console.log(userAgent); + 35 | console.log(userAgent); - 35 | + 36 | - at Object.navigator (__tests__/node.js:32:21)" + at Object.navigator (__tests__/node.js:33:21)" at toMatchSnapshot (e2e/__tests__/wrongEnv.test.ts:15:46) at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:30:7)
Wrong globals for environment › on node <=18 › print useful error for navigator: e2e/__tests__/wrongEnv.test.ts#L15
expect(received).toMatchSnapshot() Snapshot name: `Wrong globals for environment on node <=18 print useful error for navigator 1` - Snapshot - 7 + Received + 7 @@ -8,14 +8,14 @@ The error below may be caused by using the wrong test environment, see https://jestjs.io/docs/configuration#testenvironment-string. Consider using the "jsdom" test environment. ReferenceError: navigator is not defined - 30 | + 31 | - 31 | test('use navigator', () => { + 32 | test('use navigator', () => { - > 32 | const userAgent = navigator.userAgent; + > 33 | const userAgent = navigator.userAgent; | ^ - 33 | + 34 | - 34 | console.log(userAgent); + 35 | console.log(userAgent); - 35 | + 36 | - at Object.navigator (__tests__/node.js:32:21)" + at Object.navigator (__tests__/node.js:33:21)" at toMatchSnapshot (e2e/__tests__/wrongEnv.test.ts:15:46) at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:30:7)
Wrong globals for environment › on node <=18 › print useful error for navigator: e2e/__tests__/wrongEnv.test.ts#L15
expect(received).toMatchSnapshot() Snapshot name: `Wrong globals for environment on node <=18 print useful error for navigator 1` - Snapshot - 7 + Received + 7 @@ -8,14 +8,14 @@ The error below may be caused by using the wrong test environment, see https://jestjs.io/docs/configuration#testenvironment-string. Consider using the "jsdom" test environment. ReferenceError: navigator is not defined - 30 | + 31 | - 31 | test('use navigator', () => { + 32 | test('use navigator', () => { - > 32 | const userAgent = navigator.userAgent; + > 33 | const userAgent = navigator.userAgent; | ^ - 33 | + 34 | - 34 | console.log(userAgent); + 35 | console.log(userAgent); - 35 | + 36 | - at Object.navigator (__tests__/node.js:32:21)" + at Object.navigator (__tests__/node.js:33:21)" at toMatchSnapshot (e2e/__tests__/wrongEnv.test.ts:15:46) at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:30:7)
macOS with shard 1/3 / Node v18.x
Final attempt failed. Child_process exited with error code 1
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 1` - 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:51:18)
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 1` - Snapshot - 0 + Received + 1 PASS __tests__/bar.spec.js PASS __tests__/foo.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. at Object.toMatchSnapshot (e2e/__tests__/watchModePatterns.test.ts:70: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)
--findRelatedTests flag › generates coverage report for filename: node:internal/child_process#L511
Could not find test summary in the output. OUTPUT: PASS __tests__/a.test.js ✓ a (5 ms) node:events:497 throw er; // Unhandled 'error' event ^ Error: kill EPERM at ChildProcess.kill (node:internal/child_process:511:26) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) Emitted 'error' event on ChildProcess instance at: at ChildProcess.kill (node:internal/child_process:511:12) [... lines matching original stack trace ...] at processTimers (node:internal/timers:529:7) { errno: -4048, code: 'EPERM', syscall: 'kill' } Node.js v22.9.0 at extractSummary (e2e/Utils.ts:245:11) at Object.<anonymous> (e2e/__tests__/findRelatedFiles.test.ts:211:38)
--findRelatedTests flag › coverage configuration is applied correctly: node:internal/child_process#L511
Could not find test summary in the output. OUTPUT: PASS __tests__/a.test.js ✓ a (5 ms) node:events:497 throw er; // Unhandled 'error' event ^ Error: kill EPERM at ChildProcess.kill (node:internal/child_process:511:26) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) Emitted 'error' event on ChildProcess instance at: at ChildProcess.kill (node:internal/child_process:511:12) [... lines matching original stack trace ...] at processTimers (node:internal/timers:529:7) { errno: -4048, code: 'EPERM', syscall: 'kill' } Node.js v22.9.0 at extractSummary (e2e/Utils.ts:245:11) at Object.<anonymous> (e2e/__tests__/findRelatedFiles.test.ts:244:43)
handles a bad revision for "changedSince": e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
handles a bad revision for "changedSince": e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
gets changed files for hg: e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
gets changed files for hg: e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
monitors only root paths for hg: e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
monitors only root paths for hg: e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
Wrong globals for environment › on node <=18 › print useful error for navigator: e2e/__tests__/wrongEnv.test.ts#L15
expect(received).toMatchSnapshot() Snapshot name: `Wrong globals for environment on node <=18 print useful error for navigator 1` - Snapshot - 7 + Received + 7 @@ -8,14 +8,14 @@ The error below may be caused by using the wrong test environment, see https://jestjs.io/docs/configuration#testenvironment-string. Consider using the "jsdom" test environment. ReferenceError: navigator is not defined - 30 | + 31 | - 31 | test('use navigator', () => { + 32 | test('use navigator', () => { - > 32 | const userAgent = navigator.userAgent; + > 33 | const userAgent = navigator.userAgent; | ^ - 33 | + 34 | - 34 | console.log(userAgent); + 35 | console.log(userAgent); - 35 | + 36 | - at Object.navigator (__tests__/node.js:32:21)" + at Object.navigator (__tests__/node.js:33:21)" at toMatchSnapshot (e2e/__tests__/wrongEnv.test.ts:15:46) at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:30:7)
Wrong globals for environment › on node <=18 › print useful error for navigator: e2e/__tests__/wrongEnv.test.ts#L15
expect(received).toMatchSnapshot() Snapshot name: `Wrong globals for environment on node <=18 print useful error for navigator 1` - Snapshot - 7 + Received + 7 @@ -8,14 +8,14 @@ The error below may be caused by using the wrong test environment, see https://jestjs.io/docs/configuration#testenvironment-string. Consider using the "jsdom" test environment. ReferenceError: navigator is not defined - 30 | + 31 | - 31 | test('use navigator', () => { + 32 | test('use navigator', () => { - > 32 | const userAgent = navigator.userAgent; + > 33 | const userAgent = navigator.userAgent; | ^ - 33 | + 34 | - 34 | console.log(userAgent); + 35 | console.log(userAgent); - 35 | + 36 | - at Object.navigator (__tests__/node.js:32:21)" + at Object.navigator (__tests__/node.js:33:21)" at toMatchSnapshot (e2e/__tests__/wrongEnv.test.ts:15:46) at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:30:7)
handles a bad revision for "changedSince": e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
handles a bad revision for "changedSince": e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
Wrong globals for environment › on node <=18 › print useful error for navigator: e2e/__tests__/wrongEnv.test.ts#L15
expect(received).toMatchSnapshot() Snapshot name: `Wrong globals for environment on node <=18 print useful error for navigator 1` - Snapshot - 7 + Received + 7 @@ -8,14 +8,14 @@ The error below may be caused by using the wrong test environment, see https://jestjs.io/docs/configuration#testenvironment-string. Consider using the "jsdom" test environment. ReferenceError: navigator is not defined - 30 | + 31 | - 31 | test('use navigator', () => { + 32 | test('use navigator', () => { - > 32 | const userAgent = navigator.userAgent; + > 33 | const userAgent = navigator.userAgent; | ^ - 33 | + 34 | - 34 | console.log(userAgent); + 35 | console.log(userAgent); - 35 | + 36 | - at Object.navigator (__tests__/node.js:32:21)" + at Object.navigator (__tests__/node.js:33:21)" at toMatchSnapshot (e2e/__tests__/wrongEnv.test.ts:15:46) at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:30:7)
Wrong globals for environment › on node <=18 › print useful error for navigator: e2e/__tests__/wrongEnv.test.ts#L15
expect(received).toMatchSnapshot() Snapshot name: `Wrong globals for environment on node <=18 print useful error for navigator 1` - Snapshot - 7 + Received + 7 @@ -8,14 +8,14 @@ The error below may be caused by using the wrong test environment, see https://jestjs.io/docs/configuration#testenvironment-string. Consider using the "jsdom" test environment. ReferenceError: navigator is not defined - 30 | + 31 | - 31 | test('use navigator', () => { + 32 | test('use navigator', () => { - > 32 | const userAgent = navigator.userAgent; + > 33 | const userAgent = navigator.userAgent; | ^ - 33 | + 34 | - 34 | console.log(userAgent); + 35 | console.log(userAgent); - 35 | + 36 | - at Object.navigator (__tests__/node.js:32:21)" + at Object.navigator (__tests__/node.js:33:21)" at toMatchSnapshot (e2e/__tests__/wrongEnv.test.ts:15:46) at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:30:7)
Wrong globals for environment › on node <=18 › print useful error for navigator: e2e/__tests__/wrongEnv.test.ts#L15
expect(received).toMatchSnapshot() Snapshot name: `Wrong globals for environment on node <=18 print useful error for navigator 1` - Snapshot - 7 + Received + 7 @@ -8,14 +8,14 @@ The error below may be caused by using the wrong test environment, see https://jestjs.io/docs/configuration#testenvironment-string. Consider using the "jsdom" test environment. ReferenceError: navigator is not defined - 30 | + 31 | - 31 | test('use navigator', () => { + 32 | test('use navigator', () => { - > 32 | const userAgent = navigator.userAgent; + > 33 | const userAgent = navigator.userAgent; | ^ - 33 | + 34 | - 34 | console.log(userAgent); + 35 | console.log(userAgent); - 35 | + 36 | - at Object.navigator (__tests__/node.js:32:21)" + at Object.navigator (__tests__/node.js:33:21)" at toMatchSnapshot (e2e/__tests__/wrongEnv.test.ts:15:46) at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:30:7)
Windows with shard 2/4 / Node v16.x
Final attempt failed. Child_process exited with error code 1
processChild › handles circular inequality properly: undefined#L1
Timed out at timeoutKill (node_modules/execa/lib/kill.js:65:23)
processChild › handles circular inequality properly: e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\bigint-inequality-test' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/nonSerializableStructuresInequality.test.ts:48:10)
processChild › handles `Map`: e2e/__tests__/nonSerializableStructuresInequality.test.ts#L36
Process exited at waitUntil (e2e/__tests__/nonSerializableStructuresInequality.test.ts:36:9) at Object.testIn2Workers (e2e/__tests__/nonSerializableStructuresInequality.test.ts:56:35)
processChild › handles `Symbol`: undefined#L1
Timed out at timeoutKill (node_modules/execa/lib/kill.js:65:23)
processChild › handles `Symbol`: e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\bigint-inequality-test' at rmSync (e2e/Utils.ts:107:8) at Object.<anonymous> (e2e/__tests__/nonSerializableStructuresInequality.test.ts:48:10)
processChild › handles functions: e2e/__tests__/nonSerializableStructuresInequality.test.ts#L106
expect(received).toMatchSnapshot() Snapshot name: `processChild handles functions 1` - Snapshot - 16 + Received + 14 FAIL __tests__/test-1.js ● test expect(received).toEqual(expected) // deep equality - Expected: [Function fn2] + Expected: Symbol(b) - Received: [Function fn1] + Received: Symbol(a) - 2 | const fn1 = () => {}; - 3 | const fn2 = () => {}; + 1 | it('test', () => { - > 4 | expect(fn1).toEqual(fn2); + > 2 | expect(Symbol('a')).toEqual(Symbol('b')); - | ^ + | ^ - 5 | }); + 3 | }); - at Object.toEqual (__tests__/test-1.js:4:15) + at Object.toEqual (__tests__/test-1.js:2:23) FAIL __tests__/test-2.js ● test expect(received).toEqual(expected) // deep equality - Expected: [Function fn2] + Expected: Symbol(b) - Received: [Function fn1] + Received: Symbol(a) - 2 | const fn1 = () => {}; - 3 | const fn2 = () => {}; + 1 | it('test', () => { - > 4 | expect(fn1).toEqual(fn2); + > 2 | expect(Symbol('a')).toEqual(Symbol('b')); - | ^ + | ^ - 5 | }); + 3 | }); - at Object.toEqual (__tests__/test-2.js:4:15) + at Object.toEqual (__tests__/test-2.js:2:23) at Object.toMatchSnapshot (e2e/__tests__/nonSerializableStructuresInequality.test.ts:106:18)
processChild › handles mixed structure: e2e/__tests__/nonSerializableStructuresInequality.test.ts#L36
Process exited at waitUntil (e2e/__tests__/nonSerializableStructuresInequality.test.ts:36:9) at Object.testIn2Workers (e2e/__tests__/nonSerializableStructuresInequality.test.ts:111:35)
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)
Should throw if watchman used with haste.enableSymlinks: e2e/Utils.ts#L158
EEXIST: file already exists, symlink 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test\symlinked-files\test.js' -> 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test\test-files\test.js' at symlinkSync (e2e/Utils.ts:158:8) at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:30:16)
processChild › handles circular inequality properly: e2e/__tests__/nonSerializableStructuresInequality.test.ts#L36
Process exited at waitUntil (e2e/__tests__/nonSerializableStructuresInequality.test.ts:36:9) at Object.testIn2Workers (e2e/__tests__/nonSerializableStructuresInequality.test.ts:56:35)
processChild › handles circular inequality properly: undefined#L1
Timed out at timeoutKill (node_modules/execa/lib/kill.js:65:23)
processChild › handles circular inequality properly: undefined#L1
Timed out at timeoutKill (node_modules/execa/lib/kill.js:65:23)
Ubuntu with shard 2/4 / Node v18.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Ubuntu with shard 2/4 / Node v18.x
Attempt 2 failed. Reason: Child_process exited with error code 1
Ubuntu with shard 2/4 / Node v16.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Ubuntu with shard 2/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
macOS with shard 1/3 / Node v16.x
Attempt 1 failed. Reason: Child_process exited with error code 1
macOS with shard 1/3 / Node v16.x
Attempt 2 failed. Reason: Child_process exited with error code 1
macOS with shard 1/3 / Node v18.x
Attempt 1 failed. Reason: Child_process exited with error code 1
macOS with shard 1/3 / Node v18.x
Attempt 2 failed. Reason: Child_process exited with error code 1
Windows with shard 1/4 / Node v18.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 1/4 / Node v18.x
Attempt 2 failed. Reason: Child_process exited with error code 1
Windows with shard 2/4 / Node v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 2/4 / Node v22.x
Attempt 2 failed. Reason: Child_process exited with error code 1
Windows with shard 2/4 / Node v18.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 2/4 / Node v18.x
Attempt 2 failed. Reason: Child_process exited with error code 1
Windows with shard 2/4 / Node v16.x
Attempt 1 failed. Reason: Child_process exited with error code 1
Windows with shard 2/4 / 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 LTS using jest-jasmine2
Attempt 2 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 v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1