[issue36597] Travis CI: doctest failure

2019-04-11 Thread Inada Naoki
Change by Inada Naoki : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___ P

[issue36597] Travis CI: doctest failure

2019-04-11 Thread Inada Naoki
Inada Naoki added the comment: New changeset ac31da8f3710f9f9b8dbb4c36b2108fb1e5b4a48 by Inada Naoki in branch '3.7': bpo-36597: fix random doctest failure (GH-12778) https://github.com/python/cpython/commit/ac31da8f3710f9f9b8dbb4c36b2108fb1e5b4a48 -- __

[issue36597] Travis CI: doctest failure

2019-04-11 Thread Inada Naoki
Inada Naoki added the comment: New changeset b3c92c6ae923ffb2b9ac5f80b28ecd689de48662 by Inada Naoki in branch 'master': bpo-36597: fix weakref example code (GH-12779) https://github.com/python/cpython/commit/b3c92c6ae923ffb2b9ac5f80b28ecd689de48662 -- _

[issue36597] Travis CI: doctest failure

2019-04-11 Thread Inada Naoki
Change by Inada Naoki : -- pull_requests: +12706 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue36597] Travis CI: doctest failure

2019-04-11 Thread Inada Naoki
Change by Inada Naoki : -- pull_requests: +12705 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue36597] Travis CI: doctest failure

2019-04-11 Thread Inada Naoki
Inada Naoki added the comment: New changeset 57b1a2862a99677f09614e9e456d36aae9ddd87c by Inada Naoki in branch 'master': bpo-36597: fix random doctest failure (GH-12776) https://github.com/python/cpython/commit/57b1a2862a99677f09614e9e456d36aae9ddd87c -- ___

[issue36597] Travis CI: doctest failure

2019-04-11 Thread Inada Naoki
Inada Naoki added the comment: I think PR-12776 fixed "obj dead or exiting" error. https://travis-ci.org/python/cpython/jobs/518656385 -- ___ Python tracker ___ __

[issue36597] Travis CI: doctest failure

2019-04-11 Thread Inada Naoki
Inada Naoki added the comment: On Thu, Apr 11, 2019 at 5:19 PM STINNER Victor wrote: > Really? When I click on https://travis-ci.org/python/cpython/jobs/518572326 > (the second link of my first message), I still see: > > """ > Warning, treated as error: > *

[issue36597] Travis CI: doctest failure

2019-04-11 Thread STINNER Victor
STINNER Victor added the comment: > You did not show travis build link which failed other than "obj dead or > exiting" error. Really? When I click on https://travis-ci.org/python/cpython/jobs/518572326 (the second link of my first message), I still see: """ Warning, treated as error: **

[issue36597] Travis CI: doctest failure

2019-04-11 Thread Inada Naoki
Change by Inada Naoki : -- pull_requests: +12703 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue36597] Travis CI: doctest failure

2019-04-11 Thread Inada Naoki
Inada Naoki added the comment: https://github.com/python/cpython/blob/master/Doc/library/weakref.rst#finalizer-objects >>> obj = Object() >>> weakref.finalize(obj, print, "obj dead or exiting") #doctest:+ELLIPSIS >>> exit() #docte

[issue36597] Travis CI: doctest failure

2019-04-11 Thread Inada Naoki
Inada Naoki added the comment: > See the beginning of my first message, the doctest prevents me to merge a PR. You did not show travis build link which failed other than "obj dead or exiting" error. Don't all other errors happened only on your environment? If no, please link to travis buil

[issue36597] Travis CI: doctest failure

2019-04-11 Thread Karthikeyan Singaravelan
Karthikeyan Singaravelan added the comment: "Object dead or exiting" is a less frequent random error with doctest. I am not sure from where it occurs but occurs for different tests at different times and is overlooked in Travis since the next runs are fine. Sample old builds : https://trav

[issue36597] Travis CI: doctest failure

2019-04-11 Thread STINNER Victor
STINNER Victor added the comment: > As far as reading your first report, this is happen only in your local environment. See the beginning of my first message, the doctest prevents me to merge a PR. But I tested on the master branch without my change, and I get the same issue locally, and the

[issue36597] Travis CI: doctest failure

2019-04-11 Thread STINNER Victor
STINNER Victor added the comment: I mark this issue as a release blocker to not forget it. I disabled the Travis CI doctest job to repair the CI, but we have to investigate why it started to fail yesterday. -- nosy: +lukasz.langa priority: normal -> release blocker _

[issue36597] Travis CI: doctest failure

2019-04-11 Thread STINNER Victor
STINNER Victor added the comment: New changeset adff01e81d291c698581eadd693caa43ae5c78ac by Victor Stinner in branch 'master': bpo-36597: Disable Travis CI doctest job (GH-12775) https://github.com/python/cpython/commit/adff01e81d291c698581eadd693caa43ae5c78ac -- __

[issue36597] Travis CI: doctest failure

2019-04-11 Thread STINNER Victor
STINNER Victor added the comment: 8 hours ago, the job still passed at the top of the the master branch (commit a9bd8925c7fa50dd3cfab125b824ec192133ef49): https://travis-ci.org/python/cpython/jobs/518281237 "Successfully installed Jinja2-2.10.1 MarkupSafe-1.1.1 Pygments-2.3.1 Sphinx-2.0.1 a

[issue36597] Travis CI: doctest failure

2019-04-11 Thread Inada Naoki
Inada Naoki added the comment: > > It seems it is caused by non English locale. > > Right, but why did it start to fail since yesterday? Is it an error start to fail since yesterday? As far as reading your first report, this is happen only in your local environment. > > You may run doctest wi

[issue36597] Travis CI: doctest failure

2019-04-11 Thread STINNER Victor
STINNER Victor added the comment: > It seems it is caused by non English locale. Right, but why did it start to fail since yesterday? > You may run doctest with existing Python, not Python 3.8. I used the command from the .travis.yml job: "... make -C Doc/ PYTHON=../python "...". It explic

[issue36597] Travis CI: doctest failure

2019-04-11 Thread Inada Naoki
Inada Naoki added the comment: On Thu, Apr 11, 2019 at 11:49 AM STINNER Victor wrote: > > File "library/unittest.mock-examples.rst", line ?, in default > Failed example: > m.one().two().three() > Expected: > > Got: > obj dead or exiting > I'm not sure where "obj is dead or e

[issue36597] Travis CI: doctest failure

2019-04-11 Thread STINNER Victor
Change by STINNER Victor : -- keywords: +patch pull_requests: +12702 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-

[issue36597] Travis CI: doctest failure

2019-04-11 Thread STINNER Victor
STINNER Victor added the comment: Well, same problem with Sphinx 1.8.5. No idea why the job started to fail. -- ___ Python tracker ___

[issue36597] Travis CI: doctest failure

2019-04-10 Thread Karthikeyan Singaravelan
Change by Karthikeyan Singaravelan : -- nosy: +mdk ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue36597] Travis CI: doctest failure

2019-04-10 Thread STINNER Victor
New submission from STINNER Victor : On my https://github.com/python/cpython/pull/12770 the doctest job of Travis CI failed with: https://travis-ci.org/python/cpython/jobs/518572326 mkdir -p build Building NEWS from Misc/NEWS.d with blurb PATH=./venv/bin:$PATH sphinx-build -b doctest -d build