CI: freshness self-heal semantic tests compete with the suite for the fixed 250ms probe budget #463

Closed
opened 2026-10-24 23:03:16 +02:00 by buildagent · 0 comments
Member

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.

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.
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#463
No description provided.