daemon_suite indexing_lifecycle_test::mounted_incremental_lifecycle_preserves_only_complete_compatible_generations fails on origin/master 17274b3 on Linux.
Command (clean detached checkout of 17274b3, own target dir, host load ~65 on 96 cores):
cargo build --locked -p tracedecay-cli --features tracedecay-cli/test-transport --bin tracedecay
cargo test --locked --no-fail-fast -p tracedecay --features test-helpers,test-transport --test daemon_suite -- mounted_incremental_lifecycle_preserves_only_complete_compatible_generations
Result: 0 passed; 1 failed (53.8 s), panicking at tests/daemon_suite/code_index_journey.rs:513:
assertion `left == right` failed: index never became ready: {"active_branch":"feature/lifecycle","code_index_freshness":{"status":"warming","worktree":{"clone_index":{"reason":"the sealed lexical artifact is still building","state":"unavailable"}, ... "coverage":"partial_refresh_in_progress", ... "progress":{"completed_files":772,"total_files":772,"completed_lexical_units":17798985,"committed_payload_bytes":250982831,"phase":"index_build","estimated_remaining_seconds":0, ...},"rebuild_in_flight":true,"staleness_state":"indexing"}}
All 772 files have been indexed, but the sealed lexical artifact for the cancellation_probe_* corpus (about 17.8M lexical units, 251 MB payload) is still building when the tracedecay_status wait_for readiness budget expires. The same test passed once on 15a43ba (before #2185), which used a CLI build without test-transport. The same failure reproduced three times out of three on the #2040 branch rebased onto 17274b3.
Per AGENTS.md this is a limit symptom. It needs measurement of the lexical seal cost for this corpus (for example, whether #2185's import path re-reads the payload), not a larger budget.
daemon_suiteindexing_lifecycle_test::mounted_incremental_lifecycle_preserves_only_complete_compatible_generationsfails onorigin/master17274b3 on Linux.Command (clean detached checkout of 17274b3, own target dir, host load ~65 on 96 cores):
Result:
0 passed; 1 failed(53.8 s), panicking attests/daemon_suite/code_index_journey.rs:513:All 772 files have been indexed, but the sealed lexical artifact for the
cancellation_probe_*corpus (about 17.8M lexical units, 251 MB payload) is still building when thetracedecay_statuswait_forreadiness budget expires. The same test passed once on 15a43ba (before #2185), which used a CLI build withouttest-transport. The same failure reproduced three times out of three on the #2040 branch rebased onto 17274b3.Per AGENTS.md this is a limit symptom. It needs measurement of the lexical seal cost for this corpus (for example, whether #2185's import path re-reads the payload), not a larger budget.