Skip to content

fix(ci): lane_claim step died silent under bash -e before its verdict — canonical RC guard #16222

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
myia-ai-01 merged 1 commit into from
Sep 15, 2026
Merged

fix(ci): lane_claim step died silent under bash -e before its verdict — canonical RC guard #16222

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions .github/workflows/always-on-guards.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1077,10 +1077,17 @@ jobs:
echo "::warning::closingIssuesReferences fetch failed; falling back to regex finder (#10323)."
fi

# Le shell par defaut du runner est `bash -e -o pipefail` ; le
# `set -uo pipefail` ci-dessus n'y retire PAS -e. Sans le guard
# `&& RC=0 || RC=$?` (la convention des gardes freres
# variation_prev_guard / variation_adjacency_guard ci-dessus), un
# exit non nul du helper (1 = BLOCK legitime, 2 = caller error)
# tuait le step AVANT l'affichage du verdict et le commentaire de
# resolution (RELEASED/OVERRIDE/48 h) : blocage muet, diagnostique
# a la main sur #15846.
python3 scripts/ci/lane_claim_required.py \
--body-file /tmp/pr_body.txt "${PR_CREFS_ARG[@]}" \
> /tmp/verdict.json 2>/tmp/verdict.err
RC=$?
> /tmp/verdict.json 2>/tmp/verdict.err && RC=0 || RC=$?

if [ -s /tmp/verdict.err ]; then
echo "--- helper stderr ---"
Expand Down
Loading