From ccc5d219419ddf55ed18c470ef04539a7ca6a6d0 Mon Sep 17 00:00:00 2001 From: Stephen Waits Date: Fri, 30 Oct 2026 01:44:55 -0600 Subject: [PATCH] test(cli): the staged-update test no longer asserts the staged folder is gone The gate on d326894c (twice green before): after the apply, the new host's next look staged 9.0.0 again within the test's window on the runner, since the test's newer program is this binary with bytes appended and its compiled version never catches up with the feed's. The program in place and the kept previous copy are the apply. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_01HS8WZziDnyxunC23MUxrLp --- crates/ledger-cli/tests/update.rs | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/crates/ledger-cli/tests/update.rs b/crates/ledger-cli/tests/update.rs index 8410e57..8aaafb4 100644 --- a/crates/ledger-cli/tests/update.rs +++ b/crates/ledger-cli/tests/update.rs @@ -917,7 +917,11 @@ fn the_host_stages_a_daily_update_and_the_next_start_applies_it() { wait_for(10, || sha256(&home.program()) == sha256(&next)), "the staged update wasn't applied" ); - assert!(wait_for(10, || !home.updates().join("staged").exists())); + // Whether `staged/` is gone is not asserted: the test's "newer" + // program is this binary with bytes appended, so its compiled version + // never catches up with the feed's, and the new host's next look (the + // knob makes it soon) may stage 9.0.0 again. The kept copy below and + // the program in place are what the apply means. assert!( home.updates() .join("previous")