Repository navigation
test(fuzz): retry an interrupted crash copy and report why a copy failed (#564) - #567
Merged
Merged
Conversation
…led (#564) The nightly ops_sequence run failed with 'step 3: copy failed' after 83k executions; the input passes alone and in 5000 repeats. libFuzzer's -timeout alarm (ITIMER_REAL, no SA_RESTART) can interrupt syscalls, and the message dropped the io::Error. crash_copy now retries Interrupted and names the file and error kind. Adds the input as a corpus seed and as a model-based test. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016QAt9R1aSPQG7rV5ouFDMU
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Nightly
ops_sequenceon v3 (run 38318336648) failed withstep 3: copy failedafter ~83k executions. The saved input is one transact followed by eightCrashsteps. It passes on its own and in 5,000 repeats locally, and there was no fd or temp-dir leak while fuzzing. So the failure came from the environment, and the message threw away theio::Error.libFuzzer's
-timeoutalarm (setitimer(ITIMER_REAL)every 31 s, handler installed withSA_SIGINFOand noSA_RESTART, seeFuzzerUtilPosix.cpp) can interrupt syscalls.std::fs::copydoesn't retryEINTRin every path.crash_copy(shared bymodel_based_testand the fuzz target) retriesErrorKind::Interrupted. Any other error now names the file (database file or WAL) and the error kind, so a repeat can be diagnosed.tests/model_based_test.rs: the Nightly fuzz failure (v3) #564 sequence (repeated_crash_copies_match_model) and the error message (crash_copy_names_the_failing_file).fuzz/corpus/ops_sequence/seed_564_repeated_crash_copies.bin.Test-harness only; no library change. #564 can be closed once the next v3 nightly is clean.
🤖 Generated with Claude Code
https://claude.ai/code/session_016QAt9R1aSPQG7rV5ouFDMU