Closed jamesbraza closed 1 month ago
As we see in this CI run, test_pdf_reader_match_doc_details has failed again. But it has a VCR, so why was it failing?
test_pdf_reader_match_doc_details
I traced it to going from pymupdf==1.24.10 to pymupdf==1.24.11 invalidating the VCR. So we can fix this now-failing test in one of two ways:
pymupdf==1.24.10
pymupdf==1.24.11
pymupdf
In this PR, I did the folowing:
pymupdf.__version__
match_on
conftest
As we see in this CI run,
test_pdf_reader_match_doc_details
has failed again. But it has a VCR, so why was it failing?I traced it to going from
pymupdf==1.24.10
topymupdf==1.24.11
invalidating the VCR. So we can fix this now-failing test in one of two ways:pymupdf
in dev dependenciespymupdf
to VCR key for this testIn this PR, I did the folowing:
test_pdf_reader_match_doc_details
's VCR name to includepymupdf.__version__
in the namematch_on
configuration from ourconftest
, and regenerated all VCR cassettes