Skip to content

test: migrate remaining test loops (#9402) #1

test: migrate remaining test loops (#9402)

test: migrate remaining test loops (#9402) #1

Triggered via push August 18, 2026 06:10
Status Failure
Total duration 26m 29s
Artifacts
ubuntu-2604-contract
1m 18s
ubuntu-2604-contract
Matrix: macos-vitest
Matrix: wsl-vitest
Fit to window
Zoom out
Zoom in

Annotations

35 errors and 8 warnings
macOS compatibility (3/4)
Process completed with exit code 1.
[integration] test/cli/destroy-detach-order.test.ts > CLI dispatch > detaches every per-sandbox provider before sandbox delete on destroy: test/cli/destroy-detach-order.test.ts#L67
AssertionError: Deleting sandbox 'alpha'... [services] cloudflared was not running [services] Stopping in-sandbox OpenClaw gateway (sandbox: alpha)... [services] OpenClaw gateway stopped inside sandbox. [services] cloudflared was not running [services] All services stopped. Error: spawnSync /Users/runner/hostedtoolcache/node/22.23.1/arm64/bin/node ETIMEDOUT: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ test/cli/destroy-detach-order.test.ts:67:31
[e2e-support] test/e2e/support/lifecycle-user-service.test.ts > managed OpenShell gateway user-service restart > selects a marked unit from an absolute custom XDG config root: test/e2e/support/lifecycle-user-service.test.ts#L231
Error: Command failed: sh -lc set -eu if [ "$(uname -s)" = Darwin ] && command -v brew >/dev/null 2>&1 && brew list --formula openshell >/dev/null 2>&1; then brew info --json=v2 openshell | grep -Eq '"tap"[[:space:]]*:[[:space:]]*"nvidia/openshell"' || exit 1 brew services restart openshell exit 0 fi if ! command -v systemctl >/dev/null 2>&1; then exit 75; fi service=openshell-gateway if ! systemctl --user cat "$service" >/dev/null 2>&1; then case "${XDG_CONFIG_HOME:-}" in /*) config_home="$XDG_CONFIG_HOME" ;; *) config_home="$HOME/.config" ;; esac unit="$config_home/systemd/user/nemoclaw-openshell-gateway.service" if [ ! -f "$unit" ]; then exit 75; fi grep -Fxq '# NEMOCLAW_MANAGED_OPENSHELL_GATEWAY=1' "$unit" || exit 75 service=nemoclaw-openshell-gateway fi systemctl --user is-enabled "$service" >/dev/null systemctl --user daemon-reload systemctl --user restart "$service" Error: Refusing to load formula nvidia/openshell/openshell from untrusted tap nvidia/openshell. Run `brew trust --formula nvidia/openshell/openshell` or `brew trust nvidia/openshell` to trust it. ❯ test/e2e/support/lifecycle-user-service.test.ts:231:7 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { status: 1, signal: null, output: [ null, '<Buffer(0) ...>', '<Buffer(196) ...>' ], pid: 85141, stdout: '<Buffer(0) ...>', stderr: '<Buffer(196) ...>' }
[e2e-support] test/e2e/support/lifecycle-user-service.test.ts > reboot lifecycle OpenShell gateway user-service fixture > uses an existing upstream service without staging a NemoClaw unit: test/e2e/support/lifecycle-user-service.test.ts#L101
Error: Command failed: bash -lc set -eu marker='# NEMOCLAW_MANAGED_OPENSHELL_GATEWAY=1' result_prefix='NEMOCLAW_E2E_GATEWAY_USER_SERVICE=' installer=$1 if [ "$(uname -s)" != Linux ]; then exit 75; fi if ! command -v systemctl >/dev/null 2>&1; then exit 75; fi case "${XDG_CONFIG_HOME:-}" in /*) config_home="$XDG_CONFIG_HOME" ;; *) config_home="$HOME/.config" ;; esac unit="$config_home/systemd/user/nemoclaw-openshell-gateway.service" had_marked_unit=0 if [ -f "$unit" ] && grep -Fxq "$marker" "$unit"; then had_marked_unit=1; fi created=0 cleanup_failed_stage() { status=$? trap - EXIT if [ "$status" -ne 0 ] && [ "$created" -eq 1 ] && [ ! -L "$unit" ] && [ -f "$unit" ] && grep -Fxq "$marker" "$unit"; then rm -f -- "$unit" systemctl --user daemon-reload >/dev/null 2>&1 || true fi if declare -F _global_cleanup >/dev/null 2>&1; then _global_cleanup; fi exit "$status" } trap cleanup_failed_stage EXIT if [ ! -f "$installer" ] || [ -L "$installer" ]; then printf "NemoClaw installer is unavailable: %s\n" "$installer" >&2 exit 1 fi source "$installer" trap cleanup_failed_stage EXIT if [ "$had_marked_unit" -eq 0 ]; then created=1; fi install_nemoclaw_openshell_gateway_user_service systemctl --user daemon-reload if systemctl --user cat openshell-gateway >/dev/null 2>&1; then printf '%s%s\n' "$result_prefix" upstream trap - EXIT exit 0 fi if [ ! -f "$unit" ] || ! grep -Fxq "$marker" "$unit"; then exit 75; fi if [ "$had_marked_unit" -eq 0 ]; then outcome=staged; else outcome=existing; fi systemctl --user enable nemoclaw-openshell-gateway >/dev/null printf '%s%s\n' "$result_prefix" "$outcome" trap - EXIT stage-service /Users/runner/work/NemoClaw/NemoClaw/scripts/install.sh ❯ test/e2e/support/lifecycle-user-service.test.ts:101:22 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { status: 75, signal: null, output: [ null, '', '' ], pid: 85118, stdout: '', stderr: '' }
[e2e-support] test/e2e/support/lifecycle-user-service.test.ts > reboot lifecycle OpenShell gateway user-service fixture > stages, enables, and removes the repository service without installer cleanup: test/e2e/support/lifecycle-user-service.test.ts#L54
Error: Command failed: bash -lc set -eu marker='# NEMOCLAW_MANAGED_OPENSHELL_GATEWAY=1' result_prefix='NEMOCLAW_E2E_GATEWAY_USER_SERVICE=' installer=$1 if [ "$(uname -s)" != Linux ]; then exit 75; fi if ! command -v systemctl >/dev/null 2>&1; then exit 75; fi case "${XDG_CONFIG_HOME:-}" in /*) config_home="$XDG_CONFIG_HOME" ;; *) config_home="$HOME/.config" ;; esac unit="$config_home/systemd/user/nemoclaw-openshell-gateway.service" had_marked_unit=0 if [ -f "$unit" ] && grep -Fxq "$marker" "$unit"; then had_marked_unit=1; fi created=0 cleanup_failed_stage() { status=$? trap - EXIT if [ "$status" -ne 0 ] && [ "$created" -eq 1 ] && [ ! -L "$unit" ] && [ -f "$unit" ] && grep -Fxq "$marker" "$unit"; then rm -f -- "$unit" systemctl --user daemon-reload >/dev/null 2>&1 || true fi if declare -F _global_cleanup >/dev/null 2>&1; then _global_cleanup; fi exit "$status" } trap cleanup_failed_stage EXIT if [ ! -f "$installer" ] || [ -L "$installer" ]; then printf "NemoClaw installer is unavailable: %s\n" "$installer" >&2 exit 1 fi source "$installer" trap cleanup_failed_stage EXIT if [ "$had_marked_unit" -eq 0 ]; then created=1; fi install_nemoclaw_openshell_gateway_user_service systemctl --user daemon-reload if systemctl --user cat openshell-gateway >/dev/null 2>&1; then printf '%s%s\n' "$result_prefix" upstream trap - EXIT exit 0 fi if [ ! -f "$unit" ] || ! grep -Fxq "$marker" "$unit"; then exit 75; fi if [ "$had_marked_unit" -eq 0 ]; then outcome=staged; else outcome=existing; fi systemctl --user enable nemoclaw-openshell-gateway >/dev/null printf '%s%s\n' "$result_prefix" "$outcome" trap - EXIT stage-service /Users/runner/work/NemoClaw/NemoClaw/scripts/install.sh ❯ test/e2e/support/lifecycle-user-service.test.ts:54:22 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { status: 75, signal: null, output: [ null, '', '' ], pid: 85110, stdout: '', stderr: '' }
macOS compatibility (3/4)
E2E_LARGER_RUNNER_LABEL must be a 1-64 character workflow label using letters, digits, dots, underscores, or hyphens
[cli] src/lib/onboard/runtime-provider/docker-state-mutation.test.ts > Docker state mutation owner > publishes without retiring the host lifecycle fence: src/lib/onboard/runtime-provider/docker-operation-authority.ts#L380
Error: Docker operation could not resolve one absolute Docker executable. ❯ qualifyDockerExecutable src/lib/onboard/runtime-provider/docker-operation-authority.ts:380:11 ❯ createDockerOperationAuthority src/lib/onboard/runtime-provider/docker-operation-authority.ts:649:22 ❯ createContainerStateMutationHarness test/helpers/docker-state-mutation-harness.ts:369:9 ❯ createDockerStateMutationHarness test/helpers/docker-state-mutation-harness.ts:447:10 ❯ src/lib/onboard/runtime-provider/docker-state-mutation.test.ts:384:21
[cli] src/lib/onboard/runtime-provider/docker-state-mutation.test.ts > Docker state mutation owner > keeps the exact Docker fence active through rollback, activation, and release: src/lib/onboard/runtime-provider/docker-operation-authority.ts#L380
Error: Docker operation could not resolve one absolute Docker executable. ❯ qualifyDockerExecutable src/lib/onboard/runtime-provider/docker-operation-authority.ts:380:11 ❯ createDockerOperationAuthority src/lib/onboard/runtime-provider/docker-operation-authority.ts:649:22 ❯ createContainerStateMutationHarness test/helpers/docker-state-mutation-harness.ts:369:9 ❯ createDockerStateMutationHarness test/helpers/docker-state-mutation-harness.ts:447:10 ❯ src/lib/onboard/runtime-provider/docker-state-mutation.test.ts:219:21
[cli] src/lib/onboard/runtime-provider/docker-state-mutation.test.ts > Docker state mutation owner > uses the exact shared lifecycle-generation wire grammar: src/lib/onboard/runtime-provider/docker-operation-authority.ts#L380
Error: Docker operation could not resolve one absolute Docker executable. ❯ qualifyDockerExecutable src/lib/onboard/runtime-provider/docker-operation-authority.ts:380:11 ❯ createDockerOperationAuthority src/lib/onboard/runtime-provider/docker-operation-authority.ts:649:22 ❯ createContainerStateMutationHarness test/helpers/docker-state-mutation-harness.ts:369:9 ❯ createDockerStateMutationHarness test/helpers/docker-state-mutation-harness.ts:447:10 ❯ src/lib/onboard/runtime-provider/docker-state-mutation.test.ts:208:18
[cli] src/lib/onboard/runtime-provider/docker-state-mutation.test.ts > Docker runtime-provider state mutation surface > rejects ambiguous labeled runtime resolution before recording authority: src/lib/onboard/runtime-provider/docker-operation-authority.ts#L380
Error: Docker operation could not resolve one absolute Docker executable. ❯ qualifyDockerExecutable src/lib/onboard/runtime-provider/docker-operation-authority.ts:380:11 ❯ createDockerOperationAuthority src/lib/onboard/runtime-provider/docker-operation-authority.ts:649:22 ❯ createContainerStateMutationHarness test/helpers/docker-state-mutation-harness.ts:369:9 ❯ createDockerStateMutationHarness test/helpers/docker-state-mutation-harness.ts:447:10 ❯ src/lib/onboard/runtime-provider/docker-state-mutation.test.ts:191:21
[cli] src/lib/onboard/runtime-provider/docker-state-mutation.test.ts > Docker runtime-provider state mutation surface > requires preexisting persisted authority before resolving a later-phase runtime: src/lib/onboard/runtime-provider/docker-operation-authority.ts#L380
Error: Docker operation could not resolve one absolute Docker executable. ❯ qualifyDockerExecutable src/lib/onboard/runtime-provider/docker-operation-authority.ts:380:11 ❯ createDockerOperationAuthority src/lib/onboard/runtime-provider/docker-operation-authority.ts:649:22 ❯ createContainerStateMutationHarness test/helpers/docker-state-mutation-harness.ts:369:9 ❯ createDockerStateMutationHarness test/helpers/docker-state-mutation-harness.ts:447:10 ❯ src/lib/onboard/runtime-provider/docker-state-mutation.test.ts:178:21
[cli] src/lib/onboard/runtime-provider/docker-state-mutation.test.ts > Docker runtime-provider state mutation surface > proves a repeated successful release from its tombstone without Docker access: src/lib/onboard/runtime-provider/docker-operation-authority.ts#L380
Error: Docker operation could not resolve one absolute Docker executable. ❯ qualifyDockerExecutable src/lib/onboard/runtime-provider/docker-operation-authority.ts:380:11 ❯ createDockerOperationAuthority src/lib/onboard/runtime-provider/docker-operation-authority.ts:649:22 ❯ createContainerStateMutationHarness test/helpers/docker-state-mutation-harness.ts:369:9 ❯ createDockerStateMutationHarness test/helpers/docker-state-mutation-harness.ts:447:10 ❯ src/lib/onboard/runtime-provider/docker-state-mutation.test.ts:154:21
[cli] src/lib/onboard/runtime-provider/docker-state-mutation.test.ts > Docker runtime-provider state mutation surface > rejects a second same-sandbox mutation before another runtime lookup: src/lib/onboard/runtime-provider/docker-operation-authority.ts#L380
Error: Docker operation could not resolve one absolute Docker executable. ❯ qualifyDockerExecutable src/lib/onboard/runtime-provider/docker-operation-authority.ts:380:11 ❯ createDockerOperationAuthority src/lib/onboard/runtime-provider/docker-operation-authority.ts:649:22 ❯ createContainerStateMutationHarness test/helpers/docker-state-mutation-harness.ts:369:9 ❯ createDockerStateMutationHarness test/helpers/docker-state-mutation-harness.ts:447:10 ❯ src/lib/onboard/runtime-provider/docker-state-mutation.test.ts:129:21
[cli] src/lib/onboard/runtime-provider/docker-state-mutation.test.ts > Docker runtime-provider state mutation surface > preserves the isolated Vitest state root from the operation environment: src/lib/onboard/runtime-provider/docker-operation-authority.ts#L380
Error: Docker operation could not resolve one absolute Docker executable. ❯ qualifyDockerExecutable src/lib/onboard/runtime-provider/docker-operation-authority.ts:380:11 ❯ createDockerOperationAuthority src/lib/onboard/runtime-provider/docker-operation-authority.ts:649:22 ❯ createContainerStateMutationHarness test/helpers/docker-state-mutation-harness.ts:369:9 ❯ createDockerStateMutationHarness test/helpers/docker-state-mutation-harness.ts:447:10 ❯ src/lib/onboard/runtime-provider/docker-state-mutation.test.ts:108:21
[cli] src/lib/onboard/runtime-provider/docker-state-mutation.test.ts > Docker runtime-provider state mutation surface > returns null before first acquire without Docker or engine-authority access: src/lib/onboard/runtime-provider/docker-operation-authority.ts#L380
Error: Docker operation could not resolve one absolute Docker executable. ❯ qualifyDockerExecutable src/lib/onboard/runtime-provider/docker-operation-authority.ts:380:11 ❯ createDockerOperationAuthority src/lib/onboard/runtime-provider/docker-operation-authority.ts:649:22 ❯ createContainerStateMutationHarness test/helpers/docker-state-mutation-harness.ts:369:9 ❯ createDockerStateMutationHarness test/helpers/docker-state-mutation-harness.ts:447:10 ❯ src/lib/onboard/runtime-provider/docker-state-mutation.test.ts:89:21
[cli] src/lib/onboard/runtime-provider/docker-state-mutation.test.ts > Docker runtime-provider state mutation surface > resolves one full labeled runtime and records authority only on synchronous acquire: src/lib/onboard/runtime-provider/docker-operation-authority.ts#L380
Error: Docker operation could not resolve one absolute Docker executable. ❯ qualifyDockerExecutable src/lib/onboard/runtime-provider/docker-operation-authority.ts:380:11 ❯ createDockerOperationAuthority src/lib/onboard/runtime-provider/docker-operation-authority.ts:649:22 ❯ createContainerStateMutationHarness test/helpers/docker-state-mutation-harness.ts:369:9 ❯ createDockerStateMutationHarness test/helpers/docker-state-mutation-harness.ts:447:10 ❯ src/lib/onboard/runtime-provider/docker-state-mutation.test.ts:55:21
WSL compatibility (3/4)
Process completed with exit code 1.
WSL compatibility (3/4)
E2E_LARGER_RUNNER_LABEL must be a 1-64 character workflow label using letters, digits, dots, underscores, or hyphens
macOS compatibility (4/4)
Process completed with exit code 1.
[cli] src/lib/inference/llama-cpp/managed-status.test.ts > managed llama.cpp status > reports invalid Docker authority construction as a conflict: src/lib/inference/llama-cpp/managed-status.test.ts#L346
AssertionError: expected { …(6) } to match object { state: 'conflict', …(1) } (4 matching properties omitted from actual) - Expected + Received { - "detail": "Managed llama.cpp DOCKER_CONTEXT is invalid.", + "detail": "Managed llama.cpp could not resolve one absolute Docker executable.", "state": "conflict", } ❯ src/lib/inference/llama-cpp/managed-status.test.ts:346:7
[integration] test/exit-code-user-error-surfaces.test.ts > user-error/startup surfaces return non-zero exit (#5974) > upload to a nonexistent sandbox prints an error and exits non-zero: test/exit-code-user-error-surfaces.test.ts#L197
AssertionError: expected Error: spawnSync /Users/runner/hostedtool… { …(5) } to be undefined - Expected: undefined + Received: Error { "message": "spawnSync /Users/runner/hostedtoolcache/node/22.23.1/arm64/bin/node ETIMEDOUT", "errno": -60, "code": "ETIMEDOUT", "syscall": "spawnSync /Users/runner/hostedtoolcache/node/22.23.1/arm64/bin/node", "path": "/Users/runner/hostedtoolcache/node/22.23.1/arm64/bin/node", "spawnargs": [ "/Users/runner/work/NemoClaw/NemoClaw/bin/nemoclaw.js", "bug5974-missing-sb", "upload", "some-file.txt", ], } ❯ test/exit-code-user-error-surfaces.test.ts:197:21
[integration] test/exit-code-user-error-surfaces.test.ts > user-error/startup surfaces return non-zero exit (#5974) > share mount on a nonexistent sandbox prints an error and exits non-zero: test/exit-code-user-error-surfaces.test.ts#L197
AssertionError: expected Error: spawnSync /Users/runner/hostedtool… { …(5) } to be undefined - Expected: undefined + Received: Error { "message": "spawnSync /Users/runner/hostedtoolcache/node/22.23.1/arm64/bin/node ETIMEDOUT", "errno": -60, "code": "ETIMEDOUT", "syscall": "spawnSync /Users/runner/hostedtoolcache/node/22.23.1/arm64/bin/node", "path": "/Users/runner/hostedtoolcache/node/22.23.1/arm64/bin/node", "spawnargs": [ "/Users/runner/work/NemoClaw/NemoClaw/bin/nemoclaw.js", "bug5974-missing-sb", "share", "mount", "/sandbox/bad-typo-path", ], } ❯ test/exit-code-user-error-surfaces.test.ts:197:21
WSL compatibility (4/4)
Process completed with exit code 1.
[integration] test/onboard-fsm-live-slices.test.ts > live onboard FSM slice boundaries > leaves ordinary policy tiers non-authoritative in the runOnboard machine [case 1]: test/onboard-fsm-live-slices.test.ts#L509
SyntaxError: Unexpected token 'o', "[non-interac"... is not valid JSON ❯ runSliceProbe test/onboard-fsm-live-slices.test.ts:509:26 ❯ test/onboard-fsm-live-slices.test.ts:607:24
[integration] test/onboard-fsm-live-slices.test.ts > live onboard FSM slice boundaries > leaves ordinary policy tiers non-authoritative in the runOnboard machine [case 0]: test/onboard-fsm-live-slices.test.ts#L509
SyntaxError: Unexpected token 'o', "[non-interac"... is not valid JSON ❯ runSliceProbe test/onboard-fsm-live-slices.test.ts:509:26 ❯ test/onboard-fsm-live-slices.test.ts:607:24
[integration] test/onboard-fsm-live-slices.test.ts > live onboard FSM slice boundaries > bypasses the strict core runner when fresh state is already past the core entry: test/onboard-fsm-live-slices.test.ts#L509
SyntaxError: Unexpected token 'o', "[non-interac"... is not valid JSON ❯ runSliceProbe test/onboard-fsm-live-slices.test.ts:509:26 ❯ test/onboard-fsm-live-slices.test.ts:567:22
[integration] test/onboard-fsm-live-slices.test.ts > live onboard FSM slice boundaries > enters the strict initial runner at preflight on an exact-state resume: test/onboard-fsm-live-slices.test.ts#L509
SyntaxError: Unexpected token 'o', "[non-interac"... is not valid JSON ❯ runSliceProbe test/onboard-fsm-live-slices.test.ts:509:26 ❯ test/onboard-fsm-live-slices.test.ts:561:22
[integration] test/onboard-fsm-live-slices.test.ts > live onboard FSM slice boundaries > enters the final slice after the core slice reaches the branch state: test/onboard-fsm-live-slices.test.ts#L507
AssertionError: slice probe exited with status 1 error: spawnSync /Users/runner/hostedtoolcache/node/22.23.1/arm64/bin/node ETIMEDOUT stderr: Third-Party Software Notice - NemoClaw Installer ────────────────────────────────────────────────── NemoClaw is licensed under Apache 2.0 and automatically retrieves, accesses or interacts with third-party software and materials, including by deploying OpenClaw in an OpenShell sandbox. Those retrieved materials are not distributed with this software and are governed solely by separate terms, conditions and licenses. You are solely responsible for finding, reviewing and complying with all applicable terms, conditions, and licenses, and for verifying the security, integrity and suitability of any retrieved materials for your specific use case. This software is provided "AS IS", without warranty of any kind. The author makes no representations or warranties regarding any third-party software, and assumes no liability for any losses, damages, liabilities or legal consequences from your use or inability to use this software or any retrieved materials. Use this software and the retrieved materials at your own risk. OpenClaw security guidance https://docs.openclaw.ai/gateway/security [non-interactive] Third-party software notice accepted via --yes-i-accept-third-party-software. stdout: [non-interactive] Agent: OpenClaw 1 !== 0 - Expected + Received - 0 + 1 ❯ runSliceProbe test/onboard-fsm-live-slices.test.ts:507:12 ❯ test/onboard-fsm-live-slices.test.ts:546:22
[integration] test/onboard-fsm-live-slices.test.ts > live onboard FSM slice boundaries > enters the core slice after the initial slice reaches provider selection: test/onboard-fsm-live-slices.test.ts#L509
SyntaxError: Unexpected token 'o', "[non-interac"... is not valid JSON ❯ runSliceProbe test/onboard-fsm-live-slices.test.ts:509:26 ❯ test/onboard-fsm-live-slices.test.ts:542:22
[integration] test/onboard-fsm-live-slices.test.ts > live onboard FSM slice boundaries > enters the initial slice on fresh onboard runs: test/onboard-fsm-live-slices.test.ts#L509
SyntaxError: Unexpected token 'o', "[non-interac"... is not valid JSON ❯ runSliceProbe test/onboard-fsm-live-slices.test.ts:509:26 ❯ test/onboard-fsm-live-slices.test.ts:534:22
[e2e-support] test/e2e/support/standard-profile-workflow-boundary.test.ts > standard E2E execution profile > writes normalized evidence and rejects successful empty runs: test/e2e/support/standard-profile-workflow-boundary.test.ts#L258
AssertionError: find: -printf: unknown primary or operator : expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ test/e2e/support/standard-profile-workflow-boundary.test.ts:258:46
[e2e-support] test/e2e/support/cli-artifact-workflow-boundary.test.ts > exact-commit CLI artifact workflow boundary > accepts matching artifact, candidate source, and workflow identities: test/e2e/support/cli-artifact-workflow-boundary.test.ts#L616
AssertionError: matching artifact identity validation failed: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ test/e2e/support/cli-artifact-workflow-boundary.test.ts:616:75
[installer-integration] test/install-openshell-e2e-artifact.test.ts > OpenShell retained E2E artifact installation > blocks network fallback when a retained asset is a symbolic link (#9051): test/install-openshell-e2e-artifact.test.ts#L134
AssertionError: expected 'shasum: WARNING: 1 computed checksum …' to contain 'Network fallback is disabled for reta…' - Expected + Received - Network fallback is disabled for retained OpenShell assets + shasum: WARNING: 1 computed checksum did NOT match + [install] SHA-256 checksum verification failed for openshell-x86_64-unknown-linux-musl.tar.gz + ❯ test/install-openshell-e2e-artifact.test.ts:134:29
WSL compatibility (1/4)
Process completed with exit code 1.
WSL compatibility (2/4)
Process completed with exit code 1.
macOS compatibility (3/4)
The following taps are not trusted: aws/tap Homebrew is currently ignoring formulae, casks and commands from these taps because tap trust is required. Untap them with: brew untap aws/tap Trust specific formulae, casks and commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> Whole-tap trust is broader and includes all current and future formulae, casks and commands from the listed taps. Trust whole taps with: brew trust aws/tap To disable trust checks: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release. For more information, see: https://docs.brew.sh/Tap-Trust
macOS compatibility (3/4)
The following taps are not trusted: aws/tap Homebrew is currently ignoring formulae, casks and commands from these taps because tap trust is required. Untap them with: brew untap aws/tap Trust specific formulae, casks and commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> Whole-tap trust is broader and includes all current and future formulae, casks and commands from the listed taps. Trust whole taps with: brew trust aws/tap To disable trust checks: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release. For more information, see: https://docs.brew.sh/Tap-Trust
macOS compatibility (1/4)
The following taps are not trusted: aws/tap Homebrew is currently ignoring formulae, casks and commands from these taps because tap trust is required. Untap them with: brew untap aws/tap Trust specific formulae, casks and commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> Whole-tap trust is broader and includes all current and future formulae, casks and commands from the listed taps. Trust whole taps with: brew trust aws/tap To disable trust checks: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release. For more information, see: https://docs.brew.sh/Tap-Trust
macOS compatibility (1/4)
The following taps are not trusted: aws/tap Homebrew is currently ignoring formulae, casks and commands from these taps because tap trust is required. Untap them with: brew untap aws/tap Trust specific formulae, casks and commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> Whole-tap trust is broader and includes all current and future formulae, casks and commands from the listed taps. Trust whole taps with: brew trust aws/tap To disable trust checks: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release. For more information, see: https://docs.brew.sh/Tap-Trust
macOS compatibility (4/4)
The following taps are not trusted: aws/tap Homebrew is currently ignoring formulae, casks and commands from these taps because tap trust is required. Untap them with: brew untap aws/tap Trust specific formulae, casks and commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> Whole-tap trust is broader and includes all current and future formulae, casks and commands from the listed taps. Trust whole taps with: brew trust aws/tap To disable trust checks: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release. For more information, see: https://docs.brew.sh/Tap-Trust
macOS compatibility (4/4)
The following taps are not trusted: aws/tap Homebrew is currently ignoring formulae, casks and commands from these taps because tap trust is required. Untap them with: brew untap aws/tap Trust specific formulae, casks and commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> Whole-tap trust is broader and includes all current and future formulae, casks and commands from the listed taps. Trust whole taps with: brew trust aws/tap To disable trust checks: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release. For more information, see: https://docs.brew.sh/Tap-Trust
macOS compatibility (2/4)
The following taps are not trusted: aws/tap Homebrew is currently ignoring formulae, casks and commands from these taps because tap trust is required. Untap them with: brew untap aws/tap Trust specific formulae, casks and commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> Whole-tap trust is broader and includes all current and future formulae, casks and commands from the listed taps. Trust whole taps with: brew trust aws/tap To disable trust checks: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release. For more information, see: https://docs.brew.sh/Tap-Trust
macOS compatibility (2/4)
The following taps are not trusted: aws/tap Homebrew is currently ignoring formulae, casks and commands from these taps because tap trust is required. Untap them with: brew untap aws/tap Trust specific formulae, casks and commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> Whole-tap trust is broader and includes all current and future formulae, casks and commands from the listed taps. Trust whole taps with: brew trust aws/tap To disable trust checks: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release. For more information, see: https://docs.brew.sh/Tap-Trust