CI: freshness self-heal semantic tests compete with the suite for the fixed 250ms probe budget #463
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#463
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?
Native Windows run6651/job49500 on PR#462 failed freshness_self_heal::a_lag_beyond_the_listed_cap_rewalks_the_tree at its initial report assertion. The actual reply was state=unmeasured, compared=1, added=0, incomplete=true, empty lagging_paths; no recovery request had been measured. This is the production250ms comparison budget expiring under the parallel nextest suite, before the test's healing premise, not an observed failure to heal a measured lag.
Both freshness_self_heal tests depend indirectly on that fixed deadline while asserting a complete initial lag measurement. Existing ci-timing policy already isolates semantic tests with indirect shipped deadlines (large-XAML controls). Register/isolate these two as well, retain the exact250ms runtime budget and all initial-count, one-comparison, path-vs-tree and30s healing assertions. Verify both registry directions and the real tests serially; no test retry/skip or increased limit.