michal/mcpctl
1
0
Fork 0
Code Issues Pull Requests 7 Actions Packages Projects Releases Wiki Activity

test(smoke): give the smoke-aws-docs fixture a readiness probe #107

Merged
michal merged 1 commits from fix/readiness-probes into main 2026-08-10 16:00:09 +00:00
Conversation 0 Commits 1 Files Changed 1 +13

1 Commits

Author SHA1 Message Date
Michal
b8cedd6262 test(smoke): give the smoke-aws-docs fixture a readiness probe
Some checks failed
CI/CD / lint (pull_request) Successful in 1m13s
Details
CI/CD / typecheck (pull_request) Successful in 1m18s
Details
CI/CD / test (pull_request) Successful in 1m26s
Details
CI/CD / build (pull_request) Successful in 2m15s
Details
CI/CD / smoke (pull_request) Failing after 3m23s
Details
CI/CD / publish (pull_request) Has been skipped
Details 
health-readiness.smoke.test.ts asserts no RUNNING server lacks a
healthCheck.tool. The smoke suite's own shared fixture had none, so the suite
reported its own scaffolding as a fleet regression — and because the fixture is
in the PROTECTED set of clean-smoke-resources.ts, it is long-lived and failed
that assertion on every run.

Mirrors the production aws-docs probe (same package): search_documentation with
a phrase, 300s interval since the call leaves the cluster.

Verified live: with this applied, "every RUNNING server has a readiness probe
configured" passes.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019wUmrfkVQR6CKcYKxENq7k
 2026-08-10 16:59:41 +01:00