Repository navigation
fix(ci): the android verify step can fail on a SIGPIPE that says nothing about the APK - #56
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
release #18(tagv0.2.8) failed inandroid (arm64-v8a)at stepverify, exit 1 — with a docs-only change, and the same code path was green inv0.2.7. The step does:grep -qexits the moment it matches, which closes the pipe;unzipthen dies of SIGPIPE (141), andpipefailturns 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 … | grepsites inrpm-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.