perso/mcp-maildir
4
0 Fork 0
Code Issues 1 Pull Requests 2 Actions 2 Packages Projects Releases Wiki Activity

ci: harden the qdrant integration job (5s client timeout + cold storage) #60

Merged
jcabillot merged 1 commits from ci/harden-qdrant-integration into main 2026-10-17 17:43:30 -04:00
Conversation 0 Commits 1 Files Changed 5
+73 -16
1 Commits
Author SHA1 Message Date
Sagent 01d15c486e ci: harden the qdrant integration job
PR Checks / hadolint (pull_request) Successful in 23s
Details
Docker Build and Push / test (pull_request) Successful in 5m19s
Details
PR Checks / build-test (pull_request) Successful in 47s
Details
Docker Build and Push / integration-test (pull_request) Successful in 5m30s
Details
PR Checks / pytest (pull_request) Successful in 3m7s
Details
Docker Build and Push / build (pull_request) Successful in 3m14s
Details 
The integration test job has been failing intermittently on main and on
open pull requests with `httpx.ReadTimeout: timed out` on the first write
to Qdrant, while `GET /collections` and `/healthz` kept answering.

Cause: the qdrant-client default request timeout is 5 seconds, and the job
only waits for `/healthz`, which is served before the storage engine
accepts writes. On a shared runner doing several builds at once, the first
collection creation or indexing exceeds 5s and the whole fixture errors
out.

- pin qdrant/qdrant to v1.19 (the digest `latest` and the cluster already
  run) and let Renovate track the pin in the workflows as well
- wait for a real write round-trip (create + delete a probe collection)
  instead of `/healthz` alone, and dump the container logs if it never
  becomes writable
- make the Qdrant client timeout configurable via QDRANT_TIMEOUT and set
  it to 60s in CI, where there is no latency SLA
 2026-10-17 21:24:18 +00:00