docker run -d publishes ports to the Docker bridge network, but the
job container runs on a different Gitea Actions network. This causes
Connection refused when tests try http://localhost:6333.
Use --network container:$(hostname) so Qdrant shares the job container's
network stack, making localhost reachable.
The Gitea Actions runner v1.0.8 fails to start the Qdrant service container
with 'exec: ./entrypoint.sh: no such file or directory'. This is a runner bug
with how it handles service container entrypoints/CMD.
Bypass the service container mechanism by starting Qdrant manually with
docker run -d and a health check wait loop.
The Gitea Actions runner v1.0.8 fails to start the Qdrant service container
with 'exec: ./entrypoint.sh: no such file or directory'. This is a runner bug
with how it handles service container entrypoints/CMD.
Bypass the service container mechanism by starting Qdrant manually with
docker run -d and a health check wait loop.
- Integration tests for search_emails and read_email against live Qdrant
- Indexes 3 test emails, tests search by content/participant/date
- CI: new 'integration-test' job with qdrant service, runs before build
- Unit test job ignores integration test file
- Unit tests for normalize_email_address, payload_matches_participant,
format_search_result (9 test cases across 3 test classes)
- New 'test' job in CI workflow (runs before build)
- pytest.ini for pythonpath config
renovate
cloudix_mcp_server
opencodecabilloteu
Julien Cabillot
