The application logs through structlog, which is not configured to propagate into the stdlib logging system during tests. Every test asserting on caplog (e.g. test_empty_chunks_list_returns_empty in tests/unit/test_batch_processor.py) fails even though the code under test does emit the expected log event. Configure structlog in tests/conftest.py (e.g. via structlog.stdlib processors or capture_logs) so caplog-based assertions work.
Steps to reproduce: pytest tests/unit/test_batch_processor.py::TestBatchEmbeddingProcessor::test_empty_chunks_list_returns_empty -q — observed: assertion on caplog fails while the warning is visibly printed to stderr.
The application logs through structlog, which is not configured to propagate into the stdlib logging system during tests. Every test asserting on
caplog(e.g.test_empty_chunks_list_returns_emptyintests/unit/test_batch_processor.py) fails even though the code under test does emit the expected log event. Configure structlog intests/conftest.py(e.g. viastructlog.stdlibprocessors orcapture_logs) so caplog-based assertions work.Steps to reproduce:
pytest tests/unit/test_batch_processor.py::TestBatchEmbeddingProcessor::test_empty_chunks_list_returns_empty -q— observed: assertion on caplog fails while the warning is visibly printed to stderr.