fix(test): tighten diagnostics check exit code assertion in CLI core test #915

Merged
freemo merged 1 commits from fix/integration-cli-core-tolerant-rc into master 2026-03-14 00:43:51 +00:00

1 Commits

Author SHA1 Message Date
freemo 77a7813f0e fix(test): tighten diagnostics check exit code assertion in CLI core test
CI / benchmark-publish (pull_request) Has been skipped
CI / build (pull_request) Successful in 15s
CI / quality (pull_request) Successful in 17s
CI / e2e_tests (pull_request) Successful in 24s
CI / lint (pull_request) Successful in 29s
CI / security (pull_request) Successful in 31s
CI / typecheck (pull_request) Successful in 55s
CI / integration_tests (pull_request) Successful in 2m39s
CI / unit_tests (pull_request) Successful in 2m57s
CI / docker (pull_request) Successful in 11s
CI / coverage (pull_request) Successful in 5m14s
CI / lint (push) Successful in 12s
CI / build (push) Successful in 15s
CI / quality (push) Successful in 17s
CI / e2e_tests (push) Successful in 23s
CI / typecheck (push) Successful in 30s
CI / security (push) Successful in 30s
CI / benchmark-regression (push) Has been skipped
CI / unit_tests (push) Successful in 2m5s
CI / docker (push) Successful in 38s
CI / integration_tests (push) Successful in 2m44s
CI / coverage (push) Successful in 5m14s
CI / benchmark-publish (push) Has been cancelled
CI / benchmark-regression (pull_request) Successful in 36m14s
Replace the tolerant "rc == 0 or rc == 1" assertion with a strict
"rc == 0" check for the diagnostics --check command. In a clean test
environment, diagnostics should complete without finding errors, and the
previous assertion could not distinguish a legitimate diagnostic failure
from a command crash.
2026-03-14 00:37:34 +00:00