lsp_probe_bin_test daemon-reuse timing assertion flakes under high load average #648
Labels
No labels
P0
P1
P2
P3
bug
category/code-change
category/cross-repo
category/eval-run
category/investigation
category/no-test-target
category/owner-ruling
category/prose-artifact
category/recurring-chore
category/structure
category/umbrella
crc-refactor
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
rule-proposal
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#648
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?
lsp-probe daemon-reuse test uses a fixed timing bound that flakes under load
Problem
#645 merge verification on 2026-09-23 found timing flakes under load average ~28.
plugins/os-sdlc/tests/lsp_probe_bin_test.rb#test_the_daemon_is_warmed_once_then_reused_by_later_calls_until_stopasserts wall-clockelapsed < 2.0at line ~81. It failed with 8.0s elapsed on both main and the ticket-645 branch under load; it passed in isolation.Cases
Approach
Replace the fixed 2.0s bound with a relative bound against the measured cold-start time in the same test, keeping the assertion meaningful.
Required work:
cold_start_elapsed * 0.5), removing the fixed< 2.0bound — check:rake test plugins/os-sdlc/tests/lsp_probe_bin_test.rbAcceptance criteria
Non-goals
Land together with #651 (same file, related daemon lifecycle); do not solve #651's leak here.
Origin
Resolution
Done: The daemon-reuse timing assertion is gone with the class it tested; lsp_probe_bin_test now runs only under PROCMAN_REAL=1 and reuse is procman's lease semantics (ADR-0219, #712).
Evidence: Commit
cd265726on branch ticket-712: tests/lsp_probe/daemon_test.rb and four daemon unit tests retired per the ticket's Retired tests section; suite green 1423 runs.Follow-ups: none