[issue34022] Python 3.7: 6 tests failed on OpenSUSE and Debian

STINNER Victor added the comment: > Some patches seem old. Are they still needed? Where can I find these patches? > I'm interested by patches modifying site.py for example. I created PR 8057 to upstream distutils-reproducible-compile.patch. Matej Cepl: Would you mind to try to find the origi

[issue34022] Python 3.7: 6 tests failed on OpenSUSE and Debian

STINNER Victor added the comment: > Are you testing with patches? It may be interesting to try to get these > patches upstream: (...) I applied manually these patches on 3.7: the 6 tests still pass. -- ___ Python tracker

[issue34022] Python 3.7: 6 tests failed on OpenSUSE and Debian

Matej Cepl added the comment: > Are you testing with patches? It may be interesting to try to get these > patches upstream: Tested both and without patches, the same results. Everything in openSUSE is done in open (rather strikingly similar to RH openness, although things are even more simp

[issue34022] Python 3.7: 6 tests failed on OpenSUSE and Debian

STINNER Victor added the comment: > Yes, it must be something in the chroot, because when run in the plain > command line, all tests as well on openSUSE Tumbleweed (with the latest > updates). Are you testing with patches? It may be interesting to try to get these patches upstream: [ 59s

[issue34022] Python 3.7: 6 tests failed on OpenSUSE and Debian

Matej Cepl added the comment: Yes, it must be something in the chroot, because when run in the plain command line, all tests as well on openSUSE Tumbleweed (with the latest updates). 393 tests OK. 1 test failed: test_epoll 21 tests skipped: test_ctypes test_devpoll test_idle test_kq

[issue34022] Python 3.7: 6 tests failed on OpenSUSE and Debian

Matej Cepl added the comment: It's somehow complicated, in the build chroot I can make tests run only with LD_LIBRARY_PATH set to $(readlink -f Python-3.7.0) and PYTHONPATH to Lib directory. However, then the set of failed tests changes. For example test_runpy runs without problems, but othe

[issue34022] Python 3.7: 6 tests failed on OpenSUSE and Debian

Serhiy Storchaka added the comment: I built and ran these tests using commands from msg320892 on openSUSE Leap 42.3, and all tests are passed. -- nosy: +serhiy.storchaka ___ Python tracker _

[issue34022] Python 3.7: 6 tests failed on OpenSUSE and Debian

STINNER Victor added the comment: > Hmm, what about version of gcc? I suspect some troubles could be caused by > gcc version 8 (we have in openSUSE), or LTO option switched on? For my tests on Fedora, I used gcc 8.1.1. I used the OpenSUSE configure command which includes --with-lto. ---

[issue34022] Python 3.7: 6 tests failed on OpenSUSE and Debian

Matej Cepl added the comment: Hmm, what about version of gcc? I suspect some troubles could be caused by gcc version 8 (we have in openSUSE), or LTO option switched on? -- ___ Python tracker ___

[issue34022] Python 3.7: 6 tests failed on OpenSUSE and Debian

Change by STINNER Victor : -- title: Python 3.7: 6 tests failed on OpenSUSE -> Python 3.7: 6 tests failed on OpenSUSE and Debian ___ Python tracker ___ ___

[issue34022] Python 3.7: 6 tests failed on OpenSUSE

STINNER Victor added the comment: I also ran the Python test suite on Debian sid using the master branch of Python and all tests pass: --- $ ./configure --prefix=/usr --enable-ipv6 --enable-loadable-sqlite-extensions --with-dbmliborder=bdb:gdbm --with-computed-gotos --without-ensurepip --wit

[issue34022] Python 3.7: 6 tests failed on OpenSUSE

STINNER Victor added the comment: Thread on python-dev: "[Python-Dev] Failing tests [Was: Re: Python 3.7.0 is now available! (and so is 3.6.6)]" https://mail.python.org/pipermail/python-dev/2018-July/154208.html My reply: https://mail.python.org/pipermail/python-dev/2018-July/154224.html Ext

[issue34022] Python 3.7: 6 tests failed on OpenSUSE

Change by Ned Deily : -- nosy: +doko ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/

[issue34022] Python 3.7: 6 tests failed on OpenSUSE

STINNER Victor added the comment: I'm unable to reproduce the issue on Fedora using the same configure command: $ ./configure --host=x86_64-suse-linux-gnu --build=x86_64-suse-linux-gnu --program-prefix= --disable-dependency-tracking --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindi

[issue34022] Python 3.7: 6 tests failed on OpenSUSE

Matej Cepl added the comment: I would add that Debian doesn't seem to fare that much better ... https://buildd.debian.org/status/fetch.php?pkg=python3.7&arch=amd64&ver=3.7.0-1&stamp=1530136859&raw=0 -- nosy: +mcepl ___ Python tracker

[issue34022] Python 3.7: 6 tests failed on OpenSUSE

STINNER Victor added the comment: It seems like the same (or similar? I didn't check) tests fail on Debian: https://buildd.debian.org/status/fetch.php?pkg=python3.7&arch=amd64&ver=3.7.0-1&stamp=1530136859&raw=0 -- ___ Python tracker

[issue34022] Python 3.7: 6 tests failed on OpenSUSE

New submission from STINNER Victor : https://build.opensuse.org/package/show/home:mcepl:work/python3 6 tests failed: test_cmd_line_script test_compileall test_importlib test_multiprocessing_main_handling test_py_compile test_runpy ===