Freshness cap tests assume complete results from a bounded probe under Windows CI load #418

Closed
opened 2026-10-23 04:14:02 +02:00 by buildagent · 0 comments
Member

PR #417 native Windows qualification at 0af18806 ran 4,821 normal tests: 4,820 passed and freshness_lagging_paths::the_list_is_capped_and_says_so failed. All 27 serial timing tests and 31 installer tests passed.

The fixture creates 60 added Markdown files and assumes index_freshness must report the exact total and truncate its path list at 50. The real API limits the probe to 250 ms. This run legitimately returned added=1, incomplete=true, one named added path and lagging_paths_truncated=false. No incorrect freshness result was demonstrated; the assertion ignored the explicit incompleteness disclosure.

Keep production time/file/probe limits intact. Exercise complete-walk naming and list capping with a private explicit budget in deterministic algorithm tests; separately prove an exhausted budget reports an incomplete, uncapped sample. Integration assertions should verify exact totals only for complete probes and otherwise check coherent observed counters, names and list truncation. Do not retry the failed run or treat its verdict as green.

PR #417 native Windows qualification at 0af18806 ran 4,821 normal tests: 4,820 passed and freshness_lagging_paths::the_list_is_capped_and_says_so failed. All 27 serial timing tests and 31 installer tests passed. The fixture creates 60 added Markdown files and assumes index_freshness must report the exact total and truncate its path list at 50. The real API limits the probe to 250 ms. This run legitimately returned added=1, incomplete=true, one named added path and lagging_paths_truncated=false. No incorrect freshness result was demonstrated; the assertion ignored the explicit incompleteness disclosure. Keep production time/file/probe limits intact. Exercise complete-walk naming and list capping with a private explicit budget in deterministic algorithm tests; separately prove an exhausted budget reports an incomplete, uncapped sample. Integration assertions should verify exact totals only for complete probes and otherwise check coherent observed counters, names and list truncation. Do not retry the failed run or treat its verdict as green.
Sign in to join this conversation.
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
h-dv/code-index#418
No description provided.