Track interesting_origin correctly in fuzz_one_input#4748
Merged
Zac-HD merged 1 commit intoMay 27, 2026
Conversation
fuzz_one_input calls execute_once directly, bypassing the engine's _execute_once_for_engine which is where data.interesting_origin is normally set. As a result data.interesting_origin was always None, so distinct failures collapsed into a single database slot (only the globally-smallest example was kept) and observability reports omitted the interesting_origin. Compute the InterestingOrigin in fuzz_one_input's failure path so that the smallest example of each distinct origin is saved and observations report the correct origin. https://claude.ai/code/session_01VWEZqU3h6yG8QFan4Du6Mk
Liam-DeVoe
approved these changes
May 27, 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
3 participants
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_one_inputcallsexecute_oncedirectly, bypassing the engine's_execute_once_for_enginewhich is wheredata.interesting_originis normally set. As a result,data.interesting_originwas always None, so distinct failures collapsed into a single database slot (only the globally-smallest example was kept) and observability reports omitted the interesting_origin.Compute the
InterestingOrigininfuzz_one_input's failure path so that the smallest example of each distinct origin is saved and observations report the correct origin.Fixes #4420.