Expand typecheck fuzz builtin coverage#9622
Open
rtfeldman wants to merge 44 commits into
Open
Conversation
rtfeldman
changed the title
…ts-9638' into fuzz-types
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
1 participant
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.
Adds a typecheck fuzz target that turns fuzzer bytes into typed Roc modules and runs them through BuildEnv. The generator uses a compile-time inventory of public builtin associated functions, validates generated coverage against Builtin.roc, and exercises a broader slice of builtins, including hashing, dict capacity operations, hasher writes, and current string/list/iter APIs.
CI now runs deterministic repro inputs for tokenize, parse, canonicalize, and typecheck from the same fuzz seed step. The seed is keyed by the PR head SHA and target name, and each target prints its seed and base64 input so reruns do not change the input while external fuzz-output collection can associate logs with the target. MiniCI also supports per-job harness args so eval keeps producing its JSON stats while using an explicit timeout for its long-running cases.