two more fuzzer-noise sources: Runner._on_sigint and http.cookiejar's own warning - #263
Merged
Merged
Conversation
… own warning Measured on a PyPy stdlib fleet (fusil-pypy311_fleet_03, 53 kept dirs); together these were 35 of 53 -- 66% -- of everything the fleet kept. 1. asyncio.runners.Runner._on_sigint (29 dirs, 55%). It is the SIGINT handler the Runner installs, and called directly as a fuzz target it unconditionally `raise KeyboardInterrupt()`. That is a BaseException, so it blows through the generated script's `except Exception` handlers and takes the session with it -- the same #192 class as signal.default_int_handler, blacklisted in #259, and reached here only because --test-private exposes the underscore-prefixed method. 2. http.cookiejar's "http.cookiejar bug!" warning (6 dirs). cookiejar.py:74 warns this, in its own words, when it meets a malformed cookie -- routine input for a fuzzer. The text carries the "bug" word (0.10): harmless alone, but enough to push a boring session over the threshold alongside another weak signal. It is the target's benign diagnostic, not a defect, so it joins the core ignore regexes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WhcpLoyjUWLbETGZnA9boj
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.
From triaging
fusil-pypy311_fleet_03. Together these were 35 of 53 kept dirs — 66% ofeverything that fleet kept.
1.
asyncio.runners.Runner._on_sigint— 29 dirs (55%)It is the SIGINT handler
Runnerinstalls. Called directly as a fuzz target itunconditionally does:
KeyboardInterruptis aBaseException, so it blows straight through the generated script'sexcept Exceptionhandlers and takes the session with it — the same #192 class assignal.default_int_handler(blacklisted in #259). Reached only because--test-privateexposes the underscore-prefixed method.
2.
http.cookiejar bug!— 6 dirshttp/cookiejar.py:74warns this, in its own words, when it meets a malformed cookie —routine input for a fuzzer:
The text carries the
bugword (0.10). Harmless on its own, but enough to push an otherwiseboring session over the threshold alongside another weak signal. It's the target's benign
diagnostic, not a defect, so it joins the core ignore regexes — and the test asserts a real
1.0 hit still scores afterwards.
Full suite green (1267); ruff clean.
🤖 Generated with Claude Code