Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign upbpo-36597: fix random doctest failure #12776
Conversation
methane
added
type-bugfix
skip news
needs backport to 3.7
labels
Apr 11, 2019
the-knights-who-say-ni
added
the
CLA signed
label
Apr 11, 2019
bedevere-bot
added
the
awaiting core review
label
Apr 11, 2019
This comment has been minimized.
This comment has been minimized.
|
Would you mind to close/reopen the PR to trigger a second Travis CI job, to confirm that it's not a random failure? |
vstinner
removed
the
needs backport to 3.7
label
Apr 11, 2019
This comment has been minimized.
This comment has been minimized.
The bot cannot cherry-pick directly the change, since I didn't disable doctest in the 3.7 branch. |
methane
closed this
Apr 11, 2019
methane
reopened this
Apr 11, 2019
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
When I test your PR locally, I still get random failures. Commands:
Example of failure:
My venv has these versions:
|
This comment has been minimized.
This comment has been minimized.
|
|
This comment has been minimized.
This comment has been minimized.
|
I'm very surprised that the job succeed on Travis CI but fail locally. Why Travis CI doesn't get the library/statistics.rst bug for example? Extract of library/statistics.rst where the fail occurred:
This file doesn't contain "import statistics". How is doctest support to know that fmean() comes from statistics? |
This comment has been minimized.
This comment has been minimized.
|
There is "testsetup" directive In
|
This comment has been minimized.
This comment has been minimized.
Ah sorry, I looked for "import statistics", but the file contains:
I didn't know this markup. The doc can be found at: Doc/conf.py also contains:
|
This comment has been minimized.
This comment has been minimized.
Aaaaaah, ok :-) Sorry, I completely misunderstood how sphinx-build picks its Python. I was confused by this line from .travis.yml:
The PYTHON=../python argument is misleading: it's useless, since sphinx-build uses its "own" Python from the virtual environment... Sorry for the noise. |
methane
merged commit 57b1a28
into
python:master
Apr 11, 2019
methane
deleted the
methane:fix-doctest
branch
Apr 11, 2019
bedevere-bot
removed
the
awaiting core review
label
Apr 11, 2019
This comment has been minimized.
This comment has been minimized.
|
Thanks @methane for the quick fix! |
methane commentedApr 11, 2019
•
edited by bedevere-bot
https://bugs.python.org/issue36597