You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4107d4a
Browse filesBrowse the repository at this point in the historyBrowse files
Two changes prompted by an opaque, repeatedly-reproducing CI failure in
75_index_status_offline.sh (a cold `mcpp self env` in a fresh MCPP_HOME whose
index/sandbox bootstrap fails fast — root cause swallowed in non-verbose logs;
verified NOT related to the feature/capability work, it fails identically on
main):
1. MCPP_VERBOSE env override (src/cli.cppm): MCPP_VERBOSE=<non-empty,!=0> turns
on verbose logging for EVERY mcpp invocation, including those nested inside
e2e test scripts that call $MCPP without flags. An explicit --quiet still
wins. Set MCPP_VERBOSE: "1" in all CI workflows (ci-linux, ci-linux-e2e,
ci-macos, ci-windows, cross-build-test, ci-fresh-install,
ci-aarch64-fresh-install) so failures carry full diagnostics. Complements the
existing MCPP_LOG_LEVEL (which only sets the FILE log level, not stderr).
2. update_index retry (src/xlings.cppm): the index sync is a network git op;
a single transient blip otherwise fails cold init outright. Bounded retry
with linear backoff (3 attempts, 2s/4s). Success returns on the first
attempt — zero added latency in steady state; only a real failure pays the
backoff. Retry notices go through mcpp::log::verbose (file always, stderr
under MCPP_VERBOSE).
This PR's own e2e CI run carries MCPP_VERBOSE=1, so it surfaces the real cause
of the 75 bootstrap failure for a targeted follow-up.
0 commit comments