Files
codebase-memory-mcp/tests
Martin Vogel 1aa0d74e83 test(cli): the activation-maintenance fixture and the drained probe end on definite events
Follow-up to #2590: three more waits that a timeout decided.

cli_activation_quiesce_does_not_wait_on_bootstrap_startup:
- Its participant child joined the version cohort with a 45 s deadline. It
  now uses UINT64_MAX, which waits for locks and answers a conflicting
  holder at once.
- The child watched for the installer's maintenance request for at most
  120 s. It now watches until a definite event: the request, an UNSAFE/IO
  answer, or the parent closing a new install-done pipe once its install
  has returned. A failed install therefore ends the watch at once instead
  of hanging, and a slow install is waited for instead of failing.

cli_install_into_host_namespace_still_drains_host_cohort:
- The "drained host stopped serving" probe was one status request with a
  2 s budget, so a slow host that still served could pass as drained (a
  false green). It now asks through the same mute-retry rule as the
  positive probe: a drained host is unreachable or reports stopping at
  once, and a slow host that still serves is asked again until it answers.
  cli_scope_host_serving_within and CLI_SCOPE_HOST_DRAINED_PROBE_MS are
  gone.

Checked by hand: with the install made to fail before it requests
maintenance (an unknown option), the test ends in 3 s through the
install-done pipe. Without the pipe and the old deadline it would hang;
with the deadline it took 120 s.

Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>
2026-10-11 15:54:35 +02:00
..
…