upgrading coana to version 14.12.194 #335
mtorpAnnotations
14 errors and 3 warnings
|
e2e-tests (24, ubuntu-latest)
Process completed with exit code 1.
|
|
src/commands/scan/cmd-scan-reach.e2e.test.mts > socket scan reach (E2E tests) > multi-ecosystem filtering > should only analyze npm ecosystem when --reach-ecosystems npm is specified: `scan reach . --reach-debug --no-interactive --reach-ecosystems npm --reach-disable-analytics`:
src/commands/scan/cmd-scan-reach.e2e.test.mts#L1072
AssertionError: should exit with code 0: expected 1 to be +0 // Object.is equality
- Expected
+ Received
- 0
+ 1
❯ timeout src/commands/scan/cmd-scan-reach.e2e.test.mts:1072:51
|
|
src/commands/scan/cmd-scan-reach.e2e.test.mts > socket scan reach (E2E tests) > multi-ecosystem filtering > should only analyze pypi ecosystem when --reach-ecosystems pypi is specified: `scan reach . --reach-debug --no-interactive --reach-ecosystems pypi --reach-disable-analytics`:
src/commands/scan/cmd-scan-reach.e2e.test.mts#L970
AssertionError: should exit with code 0: expected 1 to be +0 // Object.is equality
- Expected
+ Received
- 0
+ 1
❯ timeout src/commands/scan/cmd-scan-reach.e2e.test.mts:970:51
|
|
e2e-tests (22, ubuntu-latest)
The strategy configuration was canceled because "e2e-tests._24_ubuntu-latest" failed
|
|
e2e-tests (22, ubuntu-latest)
Process completed with exit code 1.
|
|
src/commands/scan/cmd-scan-reach.e2e.test.mts > socket scan reach (E2E tests) > multi-ecosystem filtering > should only analyze npm ecosystem when --reach-ecosystems npm is specified: `scan reach . --reach-debug --no-interactive --reach-ecosystems npm --reach-disable-analytics`:
src/commands/scan/cmd-scan-reach.e2e.test.mts#L1072
AssertionError: should exit with code 0: expected 1 to be +0 // Object.is equality
- Expected
+ Received
- 0
+ 1
❯ timeout src/commands/scan/cmd-scan-reach.e2e.test.mts:1072:51
|
|
src/commands/scan/cmd-scan-reach.e2e.test.mts > socket scan reach (E2E tests) > multi-ecosystem filtering > should only analyze pypi ecosystem when --reach-ecosystems pypi is specified: `scan reach . --reach-debug --no-interactive --reach-ecosystems pypi --reach-disable-analytics`:
src/commands/scan/cmd-scan-reach.e2e.test.mts#L970
AssertionError: should exit with code 0: expected 1 to be +0 // Object.is equality
- Expected
+ Received
- 0
+ 1
❯ timeout src/commands/scan/cmd-scan-reach.e2e.test.mts:970:51
|
|
src/commands/scan/cmd-scan-reach.e2e.test.mts > socket scan reach (E2E tests) > npm-test-workspace-mono > should run reachability analysis on workspace mono project: `scan reach . --reach-debug --no-interactive --reach-disable-analytics`:
src/commands/scan/cmd-scan-reach.e2e.test.mts#L359
AssertionError: GHSA-fvqr-27wr-82fm should be reachable in packages/package-b: expected 'error' to be 'reachable' // Object.is equality
Expected: "reachable"
Received: "error"
❯ timeout src/commands/scan/cmd-scan-reach.e2e.test.mts:359:13
|
|
src/commands/fix/cmd-fix.e2e.test.mts > socket fix (E2E tests) > JavaScript projects > should fix all vulnerabilities in JavaScript project: `fix .`:
src/commands/fix/cmd-fix.e2e.test.mts#L188
AssertionError: lodash should be upgraded from 4.17.20 to 4.17.20: expected 0 to be greater than 0
❯ timeout src/commands/fix/cmd-fix.e2e.test.mts:188:13
|
|
e2e-tests (20, ubuntu-latest)
The strategy configuration was canceled because "e2e-tests._24_ubuntu-latest" failed
|
|
e2e-tests (20, ubuntu-latest)
Process completed with exit code 1.
|
|
src/commands/scan/cmd-scan-reach.e2e.test.mts > socket scan reach (E2E tests) > multi-ecosystem filtering > should only analyze npm ecosystem when --reach-ecosystems npm is specified: `scan reach . --reach-debug --no-interactive --reach-ecosystems npm --reach-disable-analytics`:
src/commands/scan/cmd-scan-reach.e2e.test.mts#L1072
AssertionError: should exit with code 0: expected 1 to be +0 // Object.is equality
- Expected
+ Received
- 0
+ 1
❯ timeout src/commands/scan/cmd-scan-reach.e2e.test.mts:1072:51
|
|
src/commands/scan/cmd-scan-reach.e2e.test.mts > socket scan reach (E2E tests) > multi-ecosystem filtering > should only analyze pypi ecosystem when --reach-ecosystems pypi is specified: `scan reach . --reach-debug --no-interactive --reach-ecosystems pypi --reach-disable-analytics`:
src/commands/scan/cmd-scan-reach.e2e.test.mts#L970
AssertionError: should exit with code 0: expected 1 to be +0 // Object.is equality
- Expected
+ Received
- 0
+ 1
❯ timeout src/commands/scan/cmd-scan-reach.e2e.test.mts:970:51
|
|
src/commands/scan/cmd-scan-reach.e2e.test.mts > socket scan reach (E2E tests) > npm-test-workspace-mono > should run reachability analysis on workspace mono project: `scan reach . --reach-debug --no-interactive --reach-disable-analytics`:
src/commands/scan/cmd-scan-reach.e2e.test.mts#L283
AssertionError: should exit with code 0: expected 1 to be +0 // Object.is equality
- Expected
+ Received
- 0
+ 1
❯ timeout src/commands/scan/cmd-scan-reach.e2e.test.mts:283:51
|
|
e2e-tests (24, ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
e2e-tests (22, ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
e2e-tests (20, ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|