Files atomic-write/reconcile test times out and a background write reports entry not found #942

Open
opened 2026-10-02 18:16:14 +00:00 by kayg · 0 comments
Owner

Observed on agenda-decks, HEAD dc68eb236c, on the shared build host. Files Clippy passed. The unchanged per-crate test run returned:

thread 'tests::internal_temp_paths_never_enter_index_during_atomic_write_reconcile_storm' panicked at crates/plugins/files/src/lib.rs:5236:14:
writes, reconcile scans, and watcher adoption complete within five minutes: Elapsed(())
thread 'tokio-rt-worker' panicked at crates/plugins/files/src/lib.rs:5210:45:
atomic write 779 failed: entry not found
test result: FAILED. 157 passed; 1 failed; 1 ignored; 0 measured; 0 filtered out; finished in 343.59s

The timeout is load-related evidence; the later entry-not-found panic may follow temporary-directory teardown after the timeout. That cause is an inference and is not confirmed. Do not treat the run as passing. No timeout, assertion, status code or fixture was changed to make the test pass.

Investigate task cancellation and Root lifetime after a bounded test timeout. Check whether the entry-not-found result can occur before timeout on a quiet locked host. The agenda-decks job reached its five-hour limit and did not change Files behavior to resolve this finding.

Observed on agenda-decks, HEAD dc68eb236c43ecf45b11f730bb78e77aaca103e1, on the shared build host. Files Clippy passed. The unchanged per-crate test run returned: ``` thread 'tests::internal_temp_paths_never_enter_index_during_atomic_write_reconcile_storm' panicked at crates/plugins/files/src/lib.rs:5236:14: writes, reconcile scans, and watcher adoption complete within five minutes: Elapsed(()) thread 'tokio-rt-worker' panicked at crates/plugins/files/src/lib.rs:5210:45: atomic write 779 failed: entry not found test result: FAILED. 157 passed; 1 failed; 1 ignored; 0 measured; 0 filtered out; finished in 343.59s ``` The timeout is load-related evidence; the later entry-not-found panic may follow temporary-directory teardown after the timeout. That cause is an inference and is not confirmed. Do not treat the run as passing. No timeout, assertion, status code or fixture was changed to make the test pass. Investigate task cancellation and Root lifetime after a bounded test timeout. Check whether the entry-not-found result can occur before timeout on a quiet locked host. The agenda-decks job reached its five-hour limit and did not change Files behavior to resolve this finding.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/calternal#942
No description provided.