Freshness cap tests assume complete results from a bounded probe under Windows CI load #418
Labels
No labels
code-review
correctness
dos
performance
security
severity/high
severity/low
severity/medium
tech-debt
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
h-dv/code-index#418
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
PR #417 native Windows qualification at
0af18806ran 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.