Draft
fix: add integration build verification to catch fuzz build failures on PRs#47398
Conversation
…ilures Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix workflow failure in fuzz job on main
fix: add integration build verification to catch fuzz build failures on PRs
Jul 22, 2026
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.
Fuzz run #18583 on
mainfailed becauseFuzzSanitizeOutput(which builds with-tags=integration) couldn't compile due to an unusedassertimport inforbidden_fields_import_test.go. The root-cause import removal landed in94beb4a677; this PR adds a guard so the same class of failure is caught before reachingmain.Changes
testjob — addsgo test -run='^$' -tags=integration ./...after dependency verification. Compiles all integration-tagged test files on every push/PR without running any tests, exposing build errors (unused imports, missing symbols) that the regular-tags '!integration'step silently skips.fuzzjob — adds the same step as a pre-flight check before the fuzz matrix runs. Ensures integration-tagged files compile cleanly so a build failure surfaces with a clear error rather than a misleading fuzz-test failure.The underlying issue: regular CI excludes integration files; the fuzz job was the only thing that compiled them, and it ran only on
main.