Latest Results
test(parity): assert exception message text in C-vs-Py fuzz
The generative parity fuzz reduced each call to (kind, ExceptionTypeName),
discarding the exception message. That left the message-text divergence
class — same exception type, different wording — invisible to the fuzz, the
same blind spot the type-only matrix has.
Now that #221/#226 (non-ASCII rejection) and #227 (repr-quoted wrong-length
ValueError, matching the C %R) have aligned the last divergent messages, every
malformed input the fuzz generates raises a byte-identical message in both
impls. _run now captures str(exc), so the existing 5-seed x 4000-iteration
corpus doubles as a regression guard for message text across the whole
deterministic decode/encode/type-check surface — at zero new runtime cost.
Verified offline against a freshly built C extension: a 50k+ input differential
(wrong-type, wrong-length, invalid-char, non-ASCII, bytes-length) found 0
message-text divergences before tightening the assertion.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>bluetoothbot:koan/fuzz-assert-message-text Latest Branches
0%
dependabot/github_actions/github-actions-f36a1d2b6e 0%
pre-commit-ci-update-config 0%
dependabot/pip/pytest-codspeed-5.0.3 © 2026 CodSpeed Technology