tox -e doc is network sensitive

Issue #537 invalid
Loic Dachary
created an issue

From time to time tox -e doc fails with something that looks like

doc develop-inst-noop: /home/loic/software/coveragepy/issue-433/coverage.py
doc installed: alabaster==0.7.9,Babel==2.3.4,chardet==2.3.0,-e hg+ssh://hg@bitbucket.org/dachary/coverage.py@c02d9e294169532dfe902f6dafed040aceb501e4#egg=coverage,doc8==0.7.1.dev1,docutils==0.13.1,imagesize==0.7.1,Jinja2==2.8,MarkupSafe==0.23,pbr==1.10.0,pyenchant==1.6.8,Pygments==2.1.3,pytz==2016.10,restructuredtext-lint==0.17.2,six==1.10.0,snowballstemmer==1.2.1,Sphinx==1.4.9,sphinx-rtd-theme==0.1.9,sphinxcontrib-spelling==2.2.0,stevedore==1.19.1
doc runtests: PYTHONHASHSEED='692856632'
doc runtests: commands[0] | doc8 -q --ignore-path doc/_build doc CHANGES.rst README.rst
doc runtests: commands[1] | sphinx-build -b html -b linkcheck -aEnq doc doc/_build/html
/home/loic/software/coveragepy/issue-433/coverage.py/doc/faq.rst:120: WARNING: broken link: http://bitbucket.org/ned/coveragepy/src/tip/AUTHORS.txt
/home/loic/software/coveragepy/issue-433/coverage.py/doc/install.rst:50: WARNING: broken link: http://packages.python.org/distribute/
ERROR: InvocationError: '/home/loic/software/coveragepy/issue-433/coverage.py/.tox/doc/bin/sphinx-build -b html -b linkcheck -aEnq doc doc/_build/html'
____________________________________________________________________ summary ____________________________________________________________________
....
ERROR:   doc: commands failed

Or another URL being unavailable, not always http://packages.python.org/distribute/.

Comments (4)

  1. Ned Batchelder repo owner

    In this case, I moved AUTHORS to CONTRIBUTORS, and I just removed the section of the docs that linked to Distribute. So those two failures should be gone.

    It does occasionally fail if a site is down, but how else can we check for dead links?

  2. Loic Dachary reporter

    Oh, I did not notice the AUTHORS.txt broken link ;-) I meant to note that this happens:

    WARNING: broken link: http://packages.python.org/distribute/
    

    And re-running immediately afterwards works. Maybe transient network errors should be retried more ? I did not actually look into this but it happened to me at least once a day in the past week and figured it is worth a bug report.

  3. Log in to comment