Skip to content
CI

Use more constants #2846

Sign in to view logs

Use more constants

Use more constants #2846

Triggered via push September 19, 2025 02:28
@jdaltonjdalton
pushed 581bfe9
main
Status Failure
Total duration 4m 21s
Artifacts –

test.yml

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

Annotations

14 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#L707
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ src/commands/optimize/cmd-optimize.test.mts:707:22
src/commands/optimize/cmd-optimize.test.mts > socket optimize > non dry-run tests > should handle npm projects with cwd correctly: `optimize . --config {"apiToken":"fake-token"}`: test/utils.mts#L78
Error: Test timed out in 30000ms. 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:78:3 ❯ src/commands/optimize/cmd-optimize.test.mts:569:5
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#L552
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ src/commands/optimize/cmd-optimize.test.mts:552: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#L525
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ src/commands/optimize/cmd-optimize.test.mts:525: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#L498
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ timeout src/commands/optimize/cmd-optimize.test.mts:498: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#L464
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ timeout src/commands/optimize/cmd-optimize.test.mts:464: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#L429
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ src/commands/optimize/cmd-optimize.test.mts:429: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#L394
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ src/commands/optimize/cmd-optimize.test.mts:394:24
test (20, ubuntu-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 (22, windows-latest)
The operation was canceled.
test (22, 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 (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
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