Skip to content

fix(ci): the android verify step can fail on a SIGPIPE that says nothing about the APK - #56

Merged
openviewmobile merged 1 commit into
mainfrom
fix/sigpipe-grep
Nov 10, 2026
Merged

openviewmobile merged 1 commit into
mainfrom
fix/sigpipe-grep

Conversation

@openviewmobile

Copy link
Copy Markdown
Owner

release #18 (tag v0.2.8) failed in android (arm64-v8a) at step verify, exit 1 — with a docs-only change, and the same code path was green in v0.2.7. The step does:

set -euo pipefail
unzip -l "$APK" | grep -q "lib/arm64-v8a/libsynochatpunch.so"

grep -q exits the moment it matches, which closes the pipe; unzip then dies of SIGPIPE (141), and pipefail turns that into a failed pipeline — so the check can report "the library is missing" for an APK that contains it, depending on whether the match lands before the writer finishes. The list is now written to a file and matched there.

Applied the same shape to the two rpm --checksig … | grep sites in rpm-smoke.yml, which have the same hazard.

I could not read the runner log (the job page would not render and the API was rate-limited); the inference comes from the step's own text plus the fact that the only changes in this release are docs, a shell script and a version string. v0.2.8's tag will be re-pointed at the merge commit and its release re-run, so the failure either disappears (SIGPIPE, as diagnosed) or shows a real message.

@openviewmobile
openviewmobile merged commit b8b5812 into main Nov 10, 2026
3 of 4 checks passed
@openviewmobile
openviewmobile deleted the fix/sigpipe-grep branch November 10, 2026 08:04
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.

1 participant