Failing test on local environment
See original GitHub issueI’m seeing a number of tests failing locally and I can’t figure out why. Visually, the PDFs in rst2pdf/tests/output
and rst2pdf/tests/reference
look very similar.
- test_fancytitles.txt
- test_foreground.txt
- test_image_units_pdf.txt
- test_issue_263.txt
- test_issue_266_3.txt
- test_issue_266_4.txt
- test_issue_267.txt
- test_issue_294.txt
- test_issue_311.txt
- test_issue_383.txt
- test_vectorpdf.txt
The only common theme I see here is that the vectorpdf
extension is used in many, though not all (I don’t think fancytitles
uses it) of them. I’m using my tox environment for this, so things are isolated, and I see the exact same failures with a virtualenv. I’m also running Fedora 29, but I have the exact same issues with an Ubuntu 16.04 VM. Any suggestions on where/how I can start investigating the issue?
$ pip freeze
aafigure==0.6
alabaster==0.7.12
attrs==19.1.0
Babel==2.7.0
backports.functools-lru-cache==1.5
certifi==2019.6.16
chardet==3.0.4
coverage==4.5.4
cssselect2==0.2.1
cycler==0.10.0
docutils==0.15.2
html5lib==1.0.1
idna==2.8
imagesize==1.1.0
Jinja2==2.10.1
kiwisolver==1.1.0
lxml==4.4.1
MarkupSafe==1.1.1
matplotlib==2.2.4
nose==1.3.7
numpy==1.16.4
packaging==19.1
pdfrw==0.4
Pillow==6.1.0
Pygments==2.4.2
pyparsing==2.4.2
PyPDF2==1.26.0
python-dateutil==2.8.0
pytz==2019.2
reportlab==3.5.23
requests==2.22.0
-e git+https://github.com/rst2pdf/rst2pdf@5223553be12428955bad5ee6b1aa09b353a672a1#egg=rst2pdf
six==1.12.0
smartypants==2.0.1
snowballstemmer==1.9.0
Sphinx==1.8.5
sphinxcontrib-websupport==1.1.2
subprocess32==3.5.4
svglib==0.9.2
tinycss2==0.6.1
typing==3.7.4
urllib3==1.25.3
webencodings==0.5.1
xhtml2pdf==0.2.3
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Why would my code tests pass successfully in development ...
The best solution is to generally try to recreate your prod environment in a staging pool. Your staging pool should usually be as...
Read more >How to Fix Flaky Tests - Semaphore CI
Randomly failing tests are the hardest to debug. Here's a framework you can use to fix them and keep your test suite healthy....
Read more >Debugging Failing Tests and Test Pipelines - GitLab
Tips for running tests locally. Use the environment variable QA_LOG_LEVEL=debug to enable additional logging output that includes page actions and Git commands.
Read more >Troubleshooting Continuous Integration, or How to Debug ...
Troubleshooting Continuous Integration, or How to Debug Tests That Fail on CI, but Pass Locally · Don't Relaunch the CI Build · Rebase...
Read more >Why tests pass locally but fail in Jenkins | Object Partners
Why your tests may pass locally but fail in Jenkins · The first thing you want to do is determine the source(s) of...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
At least on my Fedora 31 host, most of these issues have been resolved by the move to content-based comparison in #854 and the remaining failures are addressed by #869. We can close this now 🙌
Okay, resolved a few of them by installing
svglib
(pip install svglib
) along with sometexlive
binary dependencies (sudo dnf install texlive-ucs texlive-anyfontsize texlive-amscls
). Alas, I still see three failing tests:I’m still investigating the first of these but the second looks like it would never pass. If I diff the reference and output I see:
(this is partial - there are more diffs but this is the first and most obvious one).
The third one is trickier. I see this:
I have no idea how to resolve this 😞