Skip to content
E2E Tests

upgrading coana to version 14.12.197 #348

Sign in to view logs

upgrading coana to version 14.12.197

upgrading coana to version 14.12.197 #348

Triggered via pull request March 13, 2026 10:35
@mtorpmtorp
opened #1120
coana-14.12.197
Status Failure
Total duration 13m 22s
Artifacts –

e2e-tests.yml

on: pull_request
Matrix: e2e-tests
Fit to window
Zoom out
Zoom in

Annotations

32 errors and 3 warnings
src/commands/scan/cmd-scan-reach.e2e.test.mts > socket scan reach (E2E tests) > npm-test-workspace-mono > should run reachability analysis with excluded paths: `scan reach . --reach-debug --no-interactive --reach-disable-analytics --reach-exclude-paths packages/package-b`: src/commands/scan/cmd-scan-reach.e2e.test.mts#L437
AssertionError: should exit with code 0: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ retry src/commands/scan/cmd-scan-reach.e2e.test.mts:437:51
src/commands/scan/cmd-scan-reach.e2e.test.mts > socket scan reach (E2E tests) > npm-test-workspace-mono > should run reachability analysis with excluded paths: `scan reach . --reach-debug --no-interactive --reach-disable-analytics --reach-exclude-paths packages/package-b`: src/commands/scan/cmd-scan-reach.e2e.test.mts#L437
AssertionError: should exit with code 0: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ retry src/commands/scan/cmd-scan-reach.e2e.test.mts:437: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 ❯ retry src/commands/scan/cmd-scan-reach.e2e.test.mts:283: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 ❯ retry src/commands/scan/cmd-scan-reach.e2e.test.mts:283: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 ❯ retry src/commands/scan/cmd-scan-reach.e2e.test.mts:283:51
src/commands/fix/cmd-fix.e2e.test.mts > socket fix (E2E tests) > Python projects > should fix all vulnerabilities in Python project: `fix .`: src/commands/fix/cmd-fix.e2e.test.mts#L524
AssertionError: django should be upgraded from 3.0.0 to 3.0.0: expected 0 to be greater than 0 ❯ timeout src/commands/fix/cmd-fix.e2e.test.mts:524:13
src/commands/fix/cmd-fix.e2e.test.mts > socket fix (E2E tests) > JavaScript projects > should convert CVE to GHSA and fix JavaScript project: `fix --id CVE-2021-23337 .`: src/commands/fix/cmd-fix.e2e.test.mts#L375
AssertionError: should exit with code 0: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ timeout src/commands/fix/cmd-fix.e2e.test.mts:375:51
src/commands/fix/cmd-fix.e2e.test.mts > socket fix (E2E tests) > JavaScript projects > should fix specific GHSA vulnerability in JavaScript project: `fix --id GHSA-35jh-r3h4-6jhm .`: src/commands/fix/cmd-fix.e2e.test.mts#L317
AssertionError: should exit with code 0: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ timeout src/commands/fix/cmd-fix.e2e.test.mts:317:51
src/commands/fix/cmd-fix.e2e.test.mts > socket fix (E2E tests) > JavaScript projects > should fix vulnerabilities and write output file with fixes result: `fix --output-file socket-fix-output.json .`: src/commands/fix/cmd-fix.e2e.test.mts#L256
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:256: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 (22, ubuntu-latest)
The strategy configuration was canceled because "e2e-tests._20_ubuntu-latest" failed
src/commands/scan/cmd-scan-reach.e2e.test.mts > socket scan reach (E2E tests) > npm-test-workspace-mono > should run reachability analysis with excluded paths: `scan reach . --reach-debug --no-interactive --reach-disable-analytics --reach-exclude-paths packages/package-b`: src/commands/scan/cmd-scan-reach.e2e.test.mts#L437
AssertionError: should exit with code 0: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ retry src/commands/scan/cmd-scan-reach.e2e.test.mts:437:51
src/commands/scan/cmd-scan-reach.e2e.test.mts > socket scan reach (E2E tests) > npm-test-workspace-mono > should run reachability analysis with excluded paths: `scan reach . --reach-debug --no-interactive --reach-disable-analytics --reach-exclude-paths packages/package-b`: src/commands/scan/cmd-scan-reach.e2e.test.mts#L437
AssertionError: should exit with code 0: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ retry src/commands/scan/cmd-scan-reach.e2e.test.mts:437: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 ❯ retry src/commands/scan/cmd-scan-reach.e2e.test.mts:283: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 ❯ retry src/commands/scan/cmd-scan-reach.e2e.test.mts:283: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 ❯ retry src/commands/scan/cmd-scan-reach.e2e.test.mts:283:51
src/commands/fix/cmd-fix.e2e.test.mts > socket fix (E2E tests) > Python projects > should fix all vulnerabilities in Python project: `fix .`: src/commands/fix/cmd-fix.e2e.test.mts#L524
AssertionError: django should be upgraded from 3.0.0 to 3.0.0: expected 0 to be greater than 0 ❯ timeout src/commands/fix/cmd-fix.e2e.test.mts:524:13
src/commands/fix/cmd-fix.e2e.test.mts > socket fix (E2E tests) > JavaScript projects > should convert CVE to GHSA and fix JavaScript project: `fix --id CVE-2021-23337 .`: src/commands/fix/cmd-fix.e2e.test.mts#L375
AssertionError: should exit with code 0: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ timeout src/commands/fix/cmd-fix.e2e.test.mts:375:51
src/commands/fix/cmd-fix.e2e.test.mts > socket fix (E2E tests) > JavaScript projects > should fix specific GHSA vulnerability in JavaScript project: `fix --id GHSA-35jh-r3h4-6jhm .`: src/commands/fix/cmd-fix.e2e.test.mts#L317
AssertionError: should exit with code 0: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ timeout src/commands/fix/cmd-fix.e2e.test.mts:317:51
src/commands/fix/cmd-fix.e2e.test.mts > socket fix (E2E tests) > JavaScript projects > should fix vulnerabilities and write output file with fixes result: `fix --output-file socket-fix-output.json .`: src/commands/fix/cmd-fix.e2e.test.mts#L256
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:256: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 (24, ubuntu-latest)
The strategy configuration was canceled because "e2e-tests._20_ubuntu-latest" failed
src/commands/scan/cmd-scan-reach.e2e.test.mts > socket scan reach (E2E tests) > npm-test-workspace-mono > should run reachability analysis with excluded paths: `scan reach . --reach-debug --no-interactive --reach-disable-analytics --reach-exclude-paths packages/package-b`: src/commands/scan/cmd-scan-reach.e2e.test.mts#L437
AssertionError: should exit with code 0: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ retry src/commands/scan/cmd-scan-reach.e2e.test.mts:437:51
src/commands/scan/cmd-scan-reach.e2e.test.mts > socket scan reach (E2E tests) > npm-test-workspace-mono > should run reachability analysis with excluded paths: `scan reach . --reach-debug --no-interactive --reach-disable-analytics --reach-exclude-paths packages/package-b`: src/commands/scan/cmd-scan-reach.e2e.test.mts#L437
AssertionError: should exit with code 0: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ retry src/commands/scan/cmd-scan-reach.e2e.test.mts:437: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 ❯ retry src/commands/scan/cmd-scan-reach.e2e.test.mts:283: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 ❯ retry src/commands/scan/cmd-scan-reach.e2e.test.mts:283: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 ❯ retry src/commands/scan/cmd-scan-reach.e2e.test.mts:283:51
src/commands/fix/cmd-fix.e2e.test.mts > socket fix (E2E tests) > Python projects > should fix all vulnerabilities in Python project: `fix .`: test/utils.mts#L153
Error: Test timed out in 120000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ cmdit test/utils.mts:153:3 ❯ src/commands/fix/cmd-fix.e2e.test.mts:474:5
src/commands/fix/cmd-fix.e2e.test.mts > socket fix (E2E tests) > JavaScript projects > should convert CVE to GHSA and fix JavaScript project: `fix --id CVE-2021-23337 .`: src/commands/fix/cmd-fix.e2e.test.mts#L375
AssertionError: should exit with code 0: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ timeout src/commands/fix/cmd-fix.e2e.test.mts:375:51
src/commands/fix/cmd-fix.e2e.test.mts > socket fix (E2E tests) > JavaScript projects > should fix specific GHSA vulnerability in JavaScript project: `fix --id GHSA-35jh-r3h4-6jhm .`: src/commands/fix/cmd-fix.e2e.test.mts#L317
AssertionError: should exit with code 0: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ timeout src/commands/fix/cmd-fix.e2e.test.mts:317:51
src/commands/fix/cmd-fix.e2e.test.mts > socket fix (E2E tests) > JavaScript projects > should fix vulnerabilities and write output file with fixes result: `fix --output-file socket-fix-output.json .`: src/commands/fix/cmd-fix.e2e.test.mts#L256
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:256:13
src/commands/fix/cmd-fix.e2e.test.mts > socket fix (E2E tests) > JavaScript projects > should fix all vulnerabilities in JavaScript project: `fix .`: test/utils.mts#L153
Error: Test timed out in 120000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ cmdit test/utils.mts:153:3 ❯ src/commands/fix/cmd-fix.e2e.test.mts:147:5
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/
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 (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/