Repository navigation
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.
As title say it repairs CI
AI overview below
The fuzz run waited 24 hours for the retired Ubuntu 20.04 runner. Local container tests also exposed two failures that would follow runner assignment: a stale byteorder update and an incompatible unpinned honggfuzz. The commit repairs all three causes.
Syntax, actionlint, and generator checks passed. All nine fuzz targets passed on native arm64; an emulated amd64 run hit SIGBUS, so native x86_64 and hosted CI remain unverified.