test: remove impossible stale-file assertion from sigkill timing test
cleanup_stale_object_temps has a 60-second age gate to protect concurrent in-progress writes. A temp file left by a SIGKILL at T+100ms is ~100ms old and intentionally skipped. Asserting zero stale files immediately after a real SIGKILL is theater — the implementation never promised that.
The meaningful invariant (pre-kill objects are intact and readable) is kept. Stale-file cleanup is already properly tested in TestStartupGcObjectTemps where files are backdated past the age gate.
sha256:84db95c32aa904fb81eed2cba091dcc11ad41bc57871ccd219f69c5e9bae42f7
sha
sha256:4a769b40d2aa3d5afbe7ad8164c365bd3dd2e33b5aa3915a1a3ca298f90e90d6
snapshot
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:84db95c32aa904fb81eed2cba091dcc11ad41bc57871ccd219f69c5e9bae42f7 --body "your comment"
No comments yet. Be the first to start the discussion.