This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Travis CI: Documentation tests fails with Sphinx 2.1
Type: Stage: resolved
Components: Build Versions: Python 3.8
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: barry, gvanrossum, maxking, mdk, ned.deily, njs, r.david.murray, vstinner
Priority: Keywords: patch

Created on 2019-06-03 01:09 by vstinner, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Pull Requests
URL Status Linked Edit
PR 13764 closed vstinner, 2019-06-03 01:12
Messages (6)
msg344352 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2019-06-03 01:09
Travis CI: "Documentation tests" failed with:

Successfully installed Jinja2-2.10.1 MarkupSafe-1.1.1 Pygments-2.4.2 Sphinx-2.1.0 alabaster-0.7.12 babel-2.7.0 blurb-1.0.7 certifi-2019.3.9 chardet-3.0.4 docutils-0.14 idna-2.8 imagesize-1.1.0 packaging-19.0 pyparsing-2.4.0 python-docs-theme-2018.7 pytz-2019.1 requests-2.22.0 six-1.12.0 snowballstemmer-1.2.1 sphinxcontrib-applehelp-1.0.1 sphinxcontrib-devhelp-1.0.1 sphinxcontrib-htmlhelp-1.0.2 sphinxcontrib-jsmath-1.0.1 sphinxcontrib-qthelp-1.0.2 sphinxcontrib-serializinghtml-1.1.3 urllib3-1.25.3
(...)
Warning, treated as error:
duplicate object description of email.message, other instance in library/email.message, use :noindex: for one of them

https://travis-ci.org/python/cpython/jobs/540532864

ref: https://github.com/python/cpython/pull/13762

--

Sphinx 2.1 was released yesterday:

https://www.sphinx-doc.org/en/master/changes.html#release-2-1-0-released-jun-02-2019
msg344361 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2019-06-03 01:39
I tried but I failed to reproduce the issue using:

git clean -fdx
./configure CFLAGS="-O0"
make

cd Doc
make venv PYTHON=../python

# Successfully installed Jinja2-2.10.1 MarkupSafe-1.1.1 Pygments-2.4.2 Sphinx-2.1.0 alabaster-0.7.12 babel-2.7.0 blurb-1.0.7 certifi-2019.3.9 chardet-3.0.4 docutils-0.14 idna-2.8 imagesize-1.1.0 packaging-19.0 pyparsing-2.4.0 python-docs-theme-2018.7 pytz-2019.1 requests-2.22.0 six-1.12.0 snowballstemmer-1.2.1 sphinxcontrib-applehelp-1.0.1 sphinxcontrib-devhelp-1.0.1 sphinxcontrib-htmlhelp-1.0.2 sphinxcontrib-jsmath-1.0.1 sphinxcontrib-qthelp-1.0.2 sphinxcontrib-serializinghtml-1.1.3 urllib3-1.25.3

# I added "LANG=" to ignore my French locale
# LANG= PATH=./venv/bin:$PATH sphinx-build -b doctest -d build/doctrees -D latex_elements.papersize= -q -W -j4 -W . build/doctest

LANG= make PYTHON=../python SPHINXOPTS="-q -W -j4" doctest
msg344362 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2019-06-03 01:42
Tests passed on my PR 13764, so I remove the release blocker status.

It might be something wrong specific to my PR 13762.
msg344363 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2019-06-03 01:51
Ok, it's very strange. The test passed when run again manually on Travis CI. I close the issue....
msg345444 - (view) Author: Nathaniel Smith (njs) * (Python committer) Date: 2019-06-13 01:09
One of Guido's mentees (I don't know her bpo account name) also ran into this:

https://python.zulipchat.com/#narrow/stream/116742-core.2Fhelp/topic/Weird.20sphinx.20error

Some analysis shows that we do have a bug in the docs – the sphinx '.. module::' directive is only supposed to be used once per module, because it means "this is the canonical documentation for this module, that should be linked to whenever anyone mentions this module".

But we have two documents that use '.. module:: email.message':
  Doc/library/email.message.rst
  Doc/library/email.compat32-message.rst

I don't know enough about the email module to know what the right fix is, so I'll CC the email-interest-area folks too... maybe email.compat32-message.rst should be using '.. currentmodule:: email.message' instead of '.. module::'?

It's not clear why this error is appearing and disappearing for different people. The sphinx 2.1 release did make some changes in this area:

  https://github.com/sphinx-doc/sphinx/commit/259be8716ad4b2332aa4d7693d73400eb06fa7d7

but that doesn't explain why it appears and disappears randomly.

Probably not worth tracking down though, given that we can just fix the underlying problem.
msg345455 - (view) Author: Ned Deily (ned.deily) * (Python committer) Date: 2019-06-13 04:07
The problem with the duplicate `.. module:: email.message` was fixed about 10 days ago with PR 13742 and backports; the fix adds a :noindex: to the duplicate entry.  I'm guessing that people seeing this problem had upgraded to Sphinx 2.1 but had not recently done a rebase of their feature branch to pick up that fix.
History
Date User Action Args
2022-04-11 14:59:16adminsetgithub: 81317
2019-06-13 04:07:11ned.deilysetstatus: open -> closed

nosy: + ned.deily
messages: + msg345455

resolution: fixed
stage: resolved
2019-06-13 01:09:48njssetstatus: closed -> open

nosy: + r.david.murray, maxking, barry, gvanrossum, njs
messages: + msg345444

resolution: not a bug -> (no value)
stage: resolved -> (no value)
2019-06-03 01:51:25vstinnersetstatus: open -> closed
resolution: not a bug
messages: + msg344363

stage: patch review -> resolved
2019-06-03 01:42:59vstinnersetpriority: release blocker ->
nosy: - lukasz.langa
messages: + msg344362

2019-06-03 01:39:03vstinnersetmessages: + msg344361
2019-06-03 01:12:40vstinnersetkeywords: + patch
stage: patch review
pull_requests: + pull_request13650
2019-06-03 01:09:22vstinnercreate