mirror of
https://github.com/alexbelgium/hassio-addons.git
synced 2026-08-20 20:07:20 +02:00
d70a76298a
A single failing matrix leg in the builder reverts the entire push, so any transient error inside a build silently undoes a good version bump. Observed on zoneminder 1.38.4 (run 31678876409, attempt 1): the aarch64 leg failed after 44 s inside the ha_autoapps.sh layer with curl: (92) HTTP/2 stream 1 was not closed cleanly: REFUSED_STREAM (err 7) gzip: stdin: unexpected end of file tar: Error is not recoverable: exiting now while the amd64 leg built and pushed 1.38.4 to GHCR. revert-on-failure then pushed 0ee26fc72 reverting the bump; a manual re-run of the same source went fully green. Because that re-run flips the run conclusion to success, these incidents do not even show up in run-conclusion statistics. The build-image step is now run tolerantly (continue-on-error) and repeated once when the first attempt fails. Only a second failure reaches revert-on-failure, so genuinely broken add-ons are still reverted, one build later than before. The retry is unconditional rather than gated on the log text looking transient: BuildKit reformats error strings and registry/runner failures spell themselves many different ways, so a text classifier would eventually stop reverting real breakage. It is also cheap - the add-ons that fail deterministically on every push (ente, comixed, binance-trading-bot) each fail in 16-34 s. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>