test: add fault injection test for abrupt client crash during write - #1915
emersonbusson wants to merge 1 commit into
Conversation
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
Closed in favor of PR #2085 consolidation. |
Understood. Acknowledging that this work is now obsolete and stopping work on this task. |
Summary
Added fault injection test simulating an abrupt client crash (SIGKILL/broken pipe) during an active multi-megabyte write, to ensure
BrokerCorecorrectly implements failsafe defaults and properly freezes, then eventually cleans up leases after TTL. This fulfills theipc-resiliencepillar requirements.Commits
Files
crates/ramshared-wsl2d/src/broker_srv.rsValidation
cargo test -p ramshared-wsl2d broker_srvpassescargo clippy -- -D warningspassesRisk/rollback
Issue
Fixes #4
Owner
ResilienceChaos100
Labels
type:test, area:ramshared
Validation
cargo test -p ramshared-wsl2d broker_srvruns correctly.cargo clippy -- -D warningsruns without warnings.Rollback trigger
Test failure.
PR created automatically by Jules for task 12531414567457037606 started by @emersonbusson