Skip to content
CI

fix: handle pnpm frozen-lockfile in CI for optimize command #2836

Sign in to view logs

fix: handle pnpm frozen-lockfile in CI for optimize command

fix: handle pnpm frozen-lockfile in CI for optimize command #2836

Triggered via push September 18, 2025 17:47
@jdaltonjdalton
pushed a726d75
main
Status Failure
Total duration 4m 20s
Artifacts –

test.yml

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

Annotations

12 errors and 3 notices
test (24, windows-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 handle optimize with both --pin and --prod flags: `optimize . --pin --prod --config {"apiToken":"fake-token"}`: src/commands/optimize/cmd-optimize.test.mts#L467
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ timeout src/commands/optimize/cmd-optimize.test.mts:467:22
src/commands/optimize/cmd-optimize.test.mts > socket optimize > non dry-run tests > should optimize with --prod flag and modify files: `optimize . --prod --config {"apiToken":"fake-token"}`: src/commands/optimize/cmd-optimize.test.mts#L433
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ timeout src/commands/optimize/cmd-optimize.test.mts:433:24
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, windows-latest)
The operation was canceled.
test (22, windows-latest)
The strategy configuration was canceled because "test._24_windows-latest" failed
test (20, windows-latest)
The operation was canceled.
test (20, windows-latest)
The strategy configuration was canceled because "test._24_windows-latest" failed
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 (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 (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