fix(ci): Stop bash -e from killing the conflict check silently
Tests / tests (push) Successful in 3m29s
Tests / tests (push) Successful in 3m29s
The `pacman -S` in the conflict check exits non-zero by design (a conflict fails in prepare, a clean list fails at the disabled download), and `OUT=$(...)` carries that status, so `bash -e` aborted the step before the output was inspected: exit 1 with no message on every run. Ignore the status and judge by the output, as intended. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
0e57df4360
commit
0ae2f036b7
@@ -350,7 +350,9 @@ jobs:
|
||||
if [ ${#PKGS[@]} -eq 0 ]; then
|
||||
echo "✅ No resolvable packages to check."
|
||||
else
|
||||
OUT=$(pac -S --noconfirm --root "$ROOT" --cachedir "$ROOT" "${PKGS[@]}" 2>&1)
|
||||
# pacman exits non-zero either way; judge by its output, not
|
||||
# its status (bash -e would otherwise kill the step silently)
|
||||
OUT=$(pac -S --noconfirm --root "$ROOT" --cachedir "$ROOT" "${PKGS[@]}" 2>&1) || true
|
||||
if grep -q 'failed to prepare transaction' <<< "$OUT"; then
|
||||
echo "------- Pacman Output -------"
|
||||
grep -vE '^(http|file|ftp)' <<< "$OUT" | tail -40
|
||||
|
||||
Reference in New Issue
Block a user