Skip to content

Fix doctor failure summary severity - #1911

Merged
codeforester merged 1 commit into
mainfrom
bug/1895-20260808-doctor-failure-summary-severity
Aug 8, 2026
Merged

Fix doctor failure summary severity#1911
codeforester merged 1 commit into
mainfrom
bug/1895-20260808-doctor-failure-summary-severity

Conversation

@codeforester

Copy link
Copy Markdown
Collaborator

Summary

Raise the final blocking-issue summary from INFO to ERROR when basectl doctor fails.

Why

The command returned a non-zero status while its final count was hidden from warn/error-level log consumers. Both regular and CI-runtime text paths had this behavior.

Impact

Failed doctor runs now retain their final blocking-issue count in error-level output. Successful summaries remain INFO.

Root cause

Both failure branches called base_std_log_info immediately before returning 1.

Validation

  • bats cli/bash/commands/basectl/tests/doctor.bats (29 passed)
  • bats cli/bash/commands/basectl/tests/ci.bats (7 passed)
  • shellcheck cli/bash/commands/basectl/subcommands/doctor.sh
  • git diff --check origin/main...HEAD
  • Full local gate with the compatible Base CLI source: 945 passed, 1 skipped Python; 854 BATS

AI context

.ai-context/ is unchanged: this is a small diagnostic severity correction with no architecture or command-surface change.

Fixes #1895

@codeforester
codeforester requested a review from a team as a code owner August 8, 2026 20:56
@codeforester
codeforester merged commit 5d75c39 into main Aug 8, 2026
28 checks passed
@codeforester
codeforester deleted the bug/1895-20260808-doctor-failure-summary-severity branch August 8, 2026 21:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Doctor's failing summary is logged at INFO level, so it disappears under warn/error-level log filtering

1 participant