➜
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.
Created on 2019-04-09 16:51 by vstinner, last changed 2022-04-11 14:59 by admin. This issue is now closed.
| Messages (7) | |||
|---|---|---|---|
| msg339778 - (view) | Author: STINNER Victor (vstinner) *  |
Date: 2019-04-09 16:51 | |
https://buildbot.python.org/all/#/builders/10/builds/2389 0:45:36 [412/420/1] test_venv crashed (Exit code 1) Timeout (0:15:00)! Thread 0x00000001 (most recent call first): File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/subprocess.py", line 987 in communicate File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/subprocess.py", line 476 in run File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/subprocess.py", line 396 in check_output File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/venv/__init__.py", line 271 in _setup_pip File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/venv/__init__.py", line 68 in create File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/venv/__init__.py", line 373 in create File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/test_venv.py", line 68 in run_with_capture File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/test_venv.py", line 400 in do_test_with_pip File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/test_venv.py", line 460 in test_with_pip ... Re-running test 'test_venv' in verbose mode test_defaults (test.test_venv.BasicTest) ... ok ... test_devnull (test.test_venv.EnsurePipTest) ... ok test_explicit_no_pip (test.test_venv.EnsurePipTest) ... ok test_no_pip_by_default (test.test_venv.EnsurePipTest) ... ok Timeout (0:15:00)! Thread 0x00000001 (most recent call first): File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/selectors.py", line 415 in select File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/subprocess.py", line 1807 in _communicate File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/subprocess.py", line 1000 in communicate File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/test_venv.py", line 39 in check_output File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/test_venv.py", line 428 in do_test_with_pip File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/test_venv.py", line 460 in test_with_pip File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/unittest/case.py", line 680 in run File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/unittest/case.py", line 740 in __call__ ... test_with_pip (test.test_venv.EnsurePipTest) ... Makefile:1139: recipe for target 'buildbottest' failed make: *** [buildbottest] Error 1 program finished with exit code 2 |
|||
| msg339873 - (view) | Author: Michael Felt (Michael.Felt) * | Date: 2019-04-10 15:56 | |
On 09/04/2019 18:51, STINNER Victor wrote: > New submission from STINNER Victor <vstinner@redhat.com>: > > https://buildbot.python.org/all/#/builders/10/builds/2389 > > 0:45:36 [412/420/1] test_venv crashed (Exit code 1) > Timeout (0:15:00)! > Thread 0x00000001 (most recent call first): > File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/subprocess.py", line 987 in communicate > File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/subprocess.py", line 476 in run > File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/subprocess.py", line 396 in check_output > File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/venv/__init__.py", line 271 in _setup_pip > File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/venv/__init__.py", line 68 in create > File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/venv/__init__.py", line 373 in create > File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/test_venv.py", line 68 in run_with_capture > File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/test_venv.py", line 400 in do_test_with_pip > File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/test_venv.py", line 460 in test_with_pip > ... > Re-running test 'test_venv' in verbose mode > test_defaults (test.test_venv.BasicTest) ... ok > ... > test_devnull (test.test_venv.EnsurePipTest) ... ok > test_explicit_no_pip (test.test_venv.EnsurePipTest) ... ok > test_no_pip_by_default (test.test_venv.EnsurePipTest) ... ok > Timeout (0:15:00)! > Thread 0x00000001 (most recent call first): > File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/selectors.py", line 415 in select > File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/subprocess.py", line 1807 in _communicate > File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/subprocess.py", line 1000 in communicate > File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/test_venv.py", line 39 in check_output > File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/test_venv.py", line 428 in do_test_with_pip > File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/test_venv.py", line 460 in test_with_pip > File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/unittest/case.py", line 680 in run > File "/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/unittest/case.py", line 740 in __call__ > ... > test_with_pip (test.test_venv.EnsurePipTest) ... Makefile:1139: recipe for target 'buildbottest' failed > make: *** [buildbottest] Error 1 > program finished with exit code 2 > > ---------- > components: Tests > messages: 339778 > nosy: David.Edelsohn, Michael.Felt, vstinner > priority: normal > severity: normal > status: open > title: test_venv: test_with_pip() hangs on PPC64 AIX 3.x > versions: Python 3.8 > > _______________________________________ > Python tracker <report@bugs.python.org> > <https://bugs.python.org/issue36579> > _______________________________________ > I am looking into this - but as it seems to have gone away again - is there a simple way to get that code back, and/or see what the diff is, before/badrun/after? Michael |
|||
| msg339875 - (view) | Author: STINNER Victor (vstinner) * |
Date: 2019-04-10 16:49 | |
"I am looking into this - but as it seems to have gone away again - is there a simple way to get that code back, and/or see what the diff is, before/badrun/after?" Maybe it's just a flacky test. It's hard to guess. You can get the Git revision of a build by looking at details: https://buildbot.python.org/all/#/builders/10/builds/2389 => Properties: "got_revision: 8702b67dad62a9084f6c1823dce10653743667c8" See also "Changes" tab. Sometimes when a bug disappears, I just close it as "outdated" after a few weeks. |
|||
| msg340016 - (view) | Author: Michael Felt (Michael.Felt) * | Date: 2019-04-12 08:28 | |
On 10/04/2019 18:49, STINNER Victor wrote: > STINNER Victor <vstinner@redhat.com> added the comment: > > "I am looking into this - but as it seems to have gone away again - is > there a simple way to get that code back, and/or see what the diff is, > before/badrun/after?" > > Maybe it's just a flacky test. It's hard to guess. > > You can get the Git revision of a build by looking at details: > > https://buildbot.python.org/all/#/builders/10/builds/2389 > => Properties: "got_revision: 8702b67dad62a9084f6c1823dce10653743667c8" > > See also "Changes" tab. > > Sometimes when a bug disappears, I just close it as "outdated" after a few weeks. > > ---------- > > _______________________________________ > Python tracker <report@bugs.python.org> > <https://bugs.python.org/issue36579> > _______________________________________ > I'll try a manual build on the gccfarm. Not exactly the same environment, but as close as I can get. |
|||
| msg340024 - (view) | Author: Michael Felt (Michael.Felt) * | Date: 2019-04-12 10:49 | |
On 12/04/2019 10:28, Michael Felt wrote: > Michael Felt <aixtools@felt.demon.nl> added the comment: > > On 10/04/2019 18:49, STINNER Victor wrote: >> STINNER Victor <vstinner@redhat.com> added the comment: >> >> "I am looking into this - but as it seems to have gone away again - is >> there a simple way to get that code back, and/or see what the diff is, >> before/badrun/after?" >> >> Maybe it's just a flacky test. It's hard to guess. >> >> You can get the Git revision of a build by looking at details: >> >> https://buildbot.python.org/all/#/builders/10/builds/2389 >> => Properties: "got_revision: 8702b67dad62a9084f6c1823dce10653743667c8" >> >> See also "Changes" tab. >> >> Sometimes when a bug disappears, I just close it as "outdated" after a few weeks. >> >> ---------- >> >> _______________________________________ >> Python tracker <report@bugs.python.org> >> <https://bugs.python.org/issue36579> >> _______________________________________ >> > I'll try a manual build on the gccfarm. Not exactly the same > environment, but as close as I can get. > > ---------- The single test passes: $ ./python -m test -v test_venv == CPython 3.8.0a3+ (v3.8.0a3-109-g8702b67:8702b67, Apr 12 2019, 04:35:08) [GCC 7.2.0] == AIX-2-00FA74164C00-powerpc-32bit big-endian == cwd: /home/aixtools/python/test_venv/build/test_python_27132304 == CPU count: 64 == encodings: locale=ISO8859-1, FS=iso8859-1 Run tests sequentially 0:00:00 [1/1] test_venv test_defaults (test.test_venv.BasicTest) ... ok test_executable (test.test_venv.BasicTest) ... ok test_executable_symlinks (test.test_venv.BasicTest) ... ok test_isolation (test.test_venv.BasicTest) ... ok test_multiprocessing (test.test_venv.BasicTest) ... ok test_overwrite_existing (test.test_venv.BasicTest) ... ok test_prefixes (test.test_venv.BasicTest) ... ok test_prompt (test.test_venv.BasicTest) ... ok test_symlinking (test.test_venv.BasicTest) ... ok test_unicode_in_batch_file (test.test_venv.BasicTest) ... skipped 'only relevant on Windows' test_unoverwritable_fails (test.test_venv.BasicTest) ... ok test_upgrade (test.test_venv.BasicTest) ... ok test_devnull (test.test_venv.EnsurePipTest) ... ok test_explicit_no_pip (test.test_venv.EnsurePipTest) ... ok test_no_pip_by_default (test.test_venv.EnsurePipTest) ... ok test_with_pip (test.test_venv.EnsurePipTest) ... ok ---------------------------------------------------------------------- Ran 16 tests in 172.244s OK (skipped=1) test_venv passed in 2 min 52 sec == Tests result: SUCCESS == With "make test" - they also all pass (make buildbottest did not run as expected, only one thread, make test runs with CPU: 64) ... 0:05:50 [420/420/1] test_venv passed (5 min 43 sec) == Tests result: SUCCESS == 401 tests OK. 1 test altered the execution environment: test_concurrent_futures 18 tests skipped: test_curses test_devpoll test_epoll test_gdb test_kqueue test_msilib test_ossaudiodev test_spwd test_startfile test_tix test_tk test_ttk_guionly test_unicode_file test_unicode_file_functions test_winconsoleio test_winreg test_winsound test_zipfile64 Total duration: 5 min 50 sec Tests result: SUCCESS So, I guess "flacky". Cannot reproduce in any case. > > _______________________________________ > Python tracker <report@bugs.python.org> > <https://bugs.python.org/issue36579> > _______________________________________ > |
|||
| msg340029 - (view) | Author: STINNER Victor (vstinner) * |
Date: 2019-04-12 12:15 | |
Since build 2389 which failed, 21 builds succeeded. The failure looks random, so I success to close the issue. I leave it open since it seems like Michael Felt is interested to investigate ;-) |
|||
| msg340031 - (view) | Author: STINNER Victor (vstinner) * |
Date: 2019-04-12 12:19 | |
Oh, I missed your second message: "So, I guess "flacky". Cannot reproduce in any case." So well, I close the issue. It's ok, sometimes things break randomly :-) The important thing is that the current status is that tests pass ;-) |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:59:13 | admin | set | github: 80760 |
| 2019-04-12 12:19:50 | vstinner | set | status: open -> closed resolution: out of date messages: + msg340031 stage: resolved |
| 2019-04-12 12:15:24 | vstinner | set | messages: + msg340029 |
| 2019-04-12 10:49:47 | Michael.Felt | set | messages: + msg340024 |
| 2019-04-12 08:28:32 | Michael.Felt | set | messages: + msg340016 |
| 2019-04-10 16:49:03 | vstinner | set | messages: + msg339875 |
| 2019-04-10 15:56:31 | Michael.Felt | set | messages: + msg339873 |
| 2019-04-09 16:51:40 | vstinner | create | |