From 75e0c4bf6bf2a980ec2cd56d82520c1a57598b39 Mon Sep 17 00:00:00 2001 From: Tim Camise Date: Thu, 15 Oct 2026 14:16:33 -0700 Subject: [PATCH] test(core): tolerate main moving in the live s1 stack read s1-a is based on main, so GitHub correctly reports it behind once main advances. The live read now asserts only that the layers above it, which sit on fixture branches, need no rebase. Found by the first dispatched live run, where both toolchains failed on the old assertion. Refs: #23 --- crates/stack-stat-core/tests/live_gh.rs | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/crates/stack-stat-core/tests/live_gh.rs b/crates/stack-stat-core/tests/live_gh.rs index 359df79..ef8ad92 100644 --- a/crates/stack-stat-core/tests/live_gh.rs +++ b/crates/stack-stat-core/tests/live_gh.rs @@ -171,7 +171,10 @@ async fn discovers_a_three_pr_stack_and_loads_details() { let details = github.pr_details(&stack).await.unwrap(); assert_eq!(details.prs.len(), 3); assert!(details.prs.iter().all(|pr| pr.is_draft)); - assert!(details.remote_rebase_branches.is_empty()); + // s1-a is based on `main`, which moves, so it may legitimately be behind. + // s1-b and s1-c sit on fixture branches that only reset moves. + assert!(!details.remote_rebase_branches.contains("fixture/s1-b")); + assert!(!details.remote_rebase_branches.contains("fixture/s1-c")); } /// Assert a one-row single-mode view and return its row.