[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

[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

[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: [

[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

[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

[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 ___