Hi all, thanks for this useful library! Sadly, with texlive 20250308 test_backend_pgf.py::test_rcupdate image comparison fails in matplotlib 3.10.1. I don't have the images, as the tests ran on an external system.
Code for reproduction
run`test_backend_pgf.py::test_rcupdate`
Actual outcome
I am sorry, as I said, I don't have the images and the log is boring otherwise:
Since this is an image comparison failure with texlive 2025, I suspect that the PDF rendering output may have slightly changed compared to the existing baseline images.
I will try to reproduce this locally with texlive 2025 and determine whether this requires updating the baseline images or adjusting the PGF backend.
I’ll report back with my findings before opening a PR.
Hi, I also came across this issue when running the tests and would like to look into it.
The test output images appear to show a small difference around the 'h' character in "math":
I ran the test using both texlive 2024 and texlive 2025, and the test only fails when using the latter.
For now, I will try to investigate what is causing the difference, and I'll report back with my findings.
As mentioned, the test passes with texlive 2024 but fails with texlive 2025. I checked whether the difference was coming from Matplotlib itself or from some part of the TeX/PDF rendering pipeline.
I captured the .pgf and .tex files that were generated by backend_pgf.py and compiled the same input manually using both texlive 2024 and 2025. What I found was that the different pdfTeX versions produced small differences in the PDF content. I also checked the Ghostscript rasterization, and that reproduced the same images as the ones generated from the test.
In conclusion, the rendering difference appears to be introduced by changes in pdfTeX between the two texlive versions rather than by the PGF output generated by Matplotlib.
@timhoffm I also tried using the texlive 2025 output as the new baseline image. This makes the test pass for texlive 2025 but then causes it to fail for texlive 2024 instead. As such, I was wondering whether the preferred solution is to update the baseline or leave it as is.
If updating the baseline to the texlive 2025 rendering is preferred, I'd be happy to prepare a PR with the updated image.
Activity
anupamdwivedi98 commented on Mar 3, 2026
Hi! I would like to investigate this issue.
Since this is an image comparison failure with texlive 2025, I suspect that the PDF rendering output may have slightly changed compared to the existing baseline images.
I will try to reproduce this locally with texlive 2025 and determine whether this requires updating the baseline images or adjusting the PGF backend.
I’ll report back with my findings before opening a PR.
axel-j-larsson commented on Sep 28, 2026
Hi, I also came across this issue when running the tests and would like to look into it.
The test output images appear to show a small difference around the 'h' character in "math":
I ran the test using both texlive 2024 and texlive 2025, and the test only fails when using the latter.
For now, I will try to investigate what is causing the difference, and I'll report back with my findings.
axel-j-larsson commented on Oct 8, 2026
I believe I have found the cause of the failure.
As mentioned, the test passes with texlive 2024 but fails with texlive 2025. I checked whether the difference was coming from Matplotlib itself or from some part of the TeX/PDF rendering pipeline.
I captured the .pgf and .tex files that were generated by backend_pgf.py and compiled the same input manually using both texlive 2024 and 2025. What I found was that the different pdfTeX versions produced small differences in the PDF content. I also checked the Ghostscript rasterization, and that reproduced the same images as the ones generated from the test.
In conclusion, the rendering difference appears to be introduced by changes in pdfTeX between the two texlive versions rather than by the PGF output generated by Matplotlib.
@timhoffm I also tried using the texlive 2025 output as the new baseline image. This makes the test pass for texlive 2025 but then causes it to fail for texlive 2024 instead. As such, I was wondering whether the preferred solution is to update the baseline or leave it as is.
If updating the baseline to the texlive 2025 rendering is preferred, I'd be happy to prepare a PR with the updated image.