fix(ci): use integration test binary for cat/tac spec tests in drift workflow#1842
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
bashkit | e294406 | Commit Preview URL Branch Preview URL |
Jun 02 2026, 09:58 AM |
…inputs Records the two libfuzzer crash artifacts found on May 28 and Jun 1 2026 (crash-b972... and crash-f87f...) as non-panic regression tests. The inputs contain embedded null bytes in arithmetic/command-substitution context; crashing was only reproduced under libfuzzer's sanitizer+smaller- stack configuration. Tests ensure the interpreter never panics on these inputs.
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.
Summary
coreutils-args-driftscheduled workflow:--test spec_testsdoes not exist as a standalone binary; spec tests live in theintegrationtest binary → change to--test integrationarithmetic_fuzzcrash inputs found by libfuzzer on May 28 and Jun 1 2026 (crash-b972... and crash-f87f...) — both contain embedded null bytes in arithmetic+command-substitution context; they only crash under libfuzzer's sanitizer/smaller-stack env, not incargo test, but the tests guard against future regressionsTest plan
arith_fuzz_crash_null_bytes_cmdsub_shoptandarith_fuzz_crash_null_bytes_array_subscripttests pass incargo test -p bashkit --test integrationCoreutils Args Driftrun succeeds after merge