Skip to content
CI

fix: Add fallback for npm exec path detection #2835

Sign in to view logs

fix: Add fallback for npm exec path detection

fix: Add fallback for npm exec path detection #2835

Triggered via push September 18, 2025 17:34
@jdaltonjdalton
pushed 73ca633
main
Status Failure
Total duration 3m 50s
Artifacts –

test.yml

on: push
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

22 errors and 3 notices
test (22, windows-latest)
The operation was canceled.
test (22, windows-latest)
The strategy configuration was canceled because "test._24_ubuntu-latest" failed
test (24, windows-latest)
The operation was canceled.
test (24, windows-latest)
The strategy configuration was canceled because "test._24_ubuntu-latest" failed
test (20, windows-latest)
The operation was canceled.
test (20, windows-latest)
The strategy configuration was canceled because "test._24_ubuntu-latest" failed
test (22, ubuntu-latest)
The operation was canceled.
src/commands/scan/cmd-scan-reach.test.mts > socket scan reach > error handling and usability tests > should show clear error for non-existent directory: `scan reach /nonexistent/directory --org fakeOrg --config {"apiToken":"fake-token"}`: src/commands/scan/cmd-scan-reach.test.mts#L732
AssertionError: expected '_____ _ _ /-----…' to match /no eligible files|file.*dir.*must co…/i - Expected: /no eligible files|file.*dir.*must contain|not.*found/i + Received: "_____ _ _ /--------------- | __|___ ___| |_ ___| |_ | Socket.dev CLI ver <redacted> |__ | * | _| '_| -_| _| | Node: <redacted>, API token: <redacted>, --org: fakeOrg |_____|___|___|_,_|___|_|.dev | Command: `socket scan reach`, cwd: <redacted> Requesting supported scan file types from API... \\xd7 An error was thrown while requesting supported scan file types \\xd7 Socket API error: Unexpected Socket API error: Request timeout" ❯ src/commands/scan/cmd-scan-reach.test.mts:732:24
src/commands/optimize/cmd-optimize.test.mts > socket optimize > error handling and usability tests > should handle invalid API token gracefully: `optimize . --config {"apiToken":"invalid-token-format"}`: src/commands/optimize/cmd-optimize.test.mts#L670
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ src/commands/optimize/cmd-optimize.test.mts:670:22
src/commands/optimize/cmd-optimize.test.mts > socket optimize > non dry-run tests > should handle optimize with --markdown output format: `optimize . --markdown --config {"apiToken":"fake-token"}`: src/commands/optimize/cmd-optimize.test.mts#L515
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ src/commands/optimize/cmd-optimize.test.mts:515:22
src/commands/optimize/cmd-optimize.test.mts > socket optimize > non dry-run tests > should handle optimize with --json output format: `optimize . --json --config {"apiToken":"fake-token"}`: src/commands/optimize/cmd-optimize.test.mts#L494
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ src/commands/optimize/cmd-optimize.test.mts:494:22
src/commands/optimize/cmd-optimize.test.mts > socket optimize > non dry-run tests > should optimize with --pin flag and modify files: `optimize . --pin --config {"apiToken":"fake-token"}`: src/commands/optimize/cmd-optimize.test.mts#L398
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ src/commands/optimize/cmd-optimize.test.mts:398:24
src/commands/optimize/cmd-optimize.test.mts > socket optimize > non dry-run tests > should optimize packages and modify package.json: `optimize . --config {"apiToken":"fake-token"}`: src/commands/optimize/cmd-optimize.test.mts#L363
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ src/commands/optimize/cmd-optimize.test.mts:363:24
test (22, ubuntu-latest)
The strategy configuration was canceled because "test._24_ubuntu-latest" failed
test (24, ubuntu-latest)
Process completed with exit code 1.
src/commands/optimize/cmd-optimize.test.mts > socket optimize > error handling and usability tests > should handle invalid API token gracefully: `optimize . --config {"apiToken":"invalid-token-format"}`: src/commands/optimize/cmd-optimize.test.mts#L670
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ src/commands/optimize/cmd-optimize.test.mts:670:22
src/commands/optimize/cmd-optimize.test.mts > socket optimize > non dry-run tests > should handle optimize with --markdown output format: `optimize . --markdown --config {"apiToken":"fake-token"}`: src/commands/optimize/cmd-optimize.test.mts#L515
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ src/commands/optimize/cmd-optimize.test.mts:515:22
src/commands/optimize/cmd-optimize.test.mts > socket optimize > non dry-run tests > should handle optimize with --json output format: `optimize . --json --config {"apiToken":"fake-token"}`: src/commands/optimize/cmd-optimize.test.mts#L494
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ src/commands/optimize/cmd-optimize.test.mts:494:22
src/commands/optimize/cmd-optimize.test.mts > socket optimize > non dry-run tests > should optimize with --pin flag and modify files: `optimize . --pin --config {"apiToken":"fake-token"}`: src/commands/optimize/cmd-optimize.test.mts#L398
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ src/commands/optimize/cmd-optimize.test.mts:398:24
src/commands/optimize/cmd-optimize.test.mts > socket optimize > non dry-run tests > should optimize packages and modify package.json: `optimize . --config {"apiToken":"fake-token"}`: src/commands/optimize/cmd-optimize.test.mts#L363
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ src/commands/optimize/cmd-optimize.test.mts:363:24
test (20, ubuntu-latest)
The operation was canceled.
test (20, ubuntu-latest)
The strategy configuration was canceled because "test._24_ubuntu-latest" failed
test (22, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
test (24, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
test (20, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677