[issue31705] test_sha256 from test_socket fails on ppc64le arch

Charalampos Stratakis added the comment: Thanks for the fix Victor! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue31705] test_sha256 from test_socket fails on ppc64le arch

STINNER Victor added the comment: "And this issue occurs not only ppc64le but also x86_64. (...) I think that this issue does not depend on arch." Thanks for the confirmation. This is what I understood from the Red Hat report, but also the kernel bugfix. test_sha256() is now skipped on all a

[issue31705] test_sha256 from test_socket fails on ppc64le arch

STINNER Victor added the comment: New changeset 92a2c07b71aefc01f84ba4b0eda8e2a45c1a6b65 by Victor Stinner (Miss Islington (bot)) in branch '3.6': Skip test_socket.test_sha256() on linux < 4.5 (GH-4643) (#4645) https://github.com/python/cpython/commit/92a2c07b71aefc01f84ba4b0eda8e2a45c1a6b65

[issue31705] test_sha256 from test_socket fails on ppc64le arch

Fomalhaut Weisszwerg added the comment: STINNER Victor Thank you for your info. And this issue occurs not only ppc64le but also x86_64. `uname -a` on my CentOS returns following: Linux localhost.localdomain 3.10.0-693.5.2.el7.x86_64 #1 SMP Fri Oct 20 20:32:50 UTC 2017 x86_64 x86_64 x86_64 GN

[issue31705] test_sha256 from test_socket fails on ppc64le arch

Change by Roundup Robot : -- pull_requests: +4560 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue31705] test_sha256 from test_socket fails on ppc64le arch

STINNER Victor added the comment: New changeset 86afc1f2a7fb3afe00779c6426bc141bc795d9a3 by Victor Stinner in branch 'master': Skip test_socket.test_sha256() on linux < 4.5 (#4643) https://github.com/python/cpython/commit/86afc1f2a7fb3afe00779c6426bc141bc795d9a3 -- _

[issue31705] test_sha256 from test_socket fails on ppc64le arch

STINNER Victor added the comment: > It would be nice to get the exact version in which sha256 was fixed on ppc64, > but it's not a requirements. Ah, I think that I found the bugfix (8 Jan 2016): https://github.com/torvalds/linux/commit/6de62f15b581 So it was fixed in the kernel 4.5. I found

[issue31705] test_sha256 from test_socket fails on ppc64le arch

STINNER Victor added the comment: Charalampos Stratakis, Ryan Decker, Fomalhaut Weisszwerg: * What is the value of os.uname().machine on ppc64le? 'ppc64le'? Is there a 'ppcbe' architecture? * Can you please try attached PR 4643 on a kernel 3.10 and confirms that the test is skipped, and maybe

[issue31705] test_sha256 from test_socket fails on ppc64le arch

Change by STINNER Victor : -- keywords: +patch pull_requests: +4557 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-li

[issue31705] test_sha256 from test_socket fails on ppc64le arch

STINNER Victor added the comment: Charalampos Stratakis told me that the test pass on kernel 4.11. The bug comes from the kernel, there is nothing that Python can do to workarond this kernel bug. So I suggest to skip the test on kernel < 4.11, or at least skip it on ppc64 with kernel < 4.11.

[issue31705] test_sha256 from test_socket fails on ppc64le arch

Fomalhaut Weisszwerg added the comment: I've got the same error on CentOS 7.4 on x86_64. --- $ cat /etc/redhat-release CentOS Linux release 7.4.1708 (Core) $ uname -a Linux localhost.localdomain 3.10.0-693.5.2.el7.x86_64 #1 SMP Fri Oct 20 20:32:50 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ st

[issue31705] test_sha256 from test_socket fails on ppc64le arch

Ryan C. Decker added the comment: I seem to be having this issue on CentOS 7.4 but running on x86_64 instead of ppc64le. I have attached an strace using version 4.17 (the lastest version from scl) created as follows: strace -s 128 -e trace=%network -o trace ./python -m test -v test_socket -m

[issue31705] test_sha256 from test_socket fails on ppc64le arch

Charalampos Stratakis added the comment: Attaching the output of: strace -s 128 -e trace=%network -o trace ./python3 -m test -v test_socket -m test_sha256 using the latest version of strace (4.19). -- Added file: https://bugs.python.org/file47204/trace2 _

[issue31705] test_sha256 from test_socket fails on ppc64le arch

Charalampos Stratakis added the comment: Indeed the version of strace is 'strace-4.12-4.el7'. I will try to provide output from the latest one. -- ___ Python tracker ___ _

[issue31705] test_sha256 from test_socket fails on ppc64le arch

STINNER Victor added the comment: > strace is maybe outdated and fails to display the full bind() address, I vote for this option since I see addrlen=88 in both examples. -- ___ Python tracker __

[issue31705] test_sha256 from test_socket fails on ppc64le arch

STINNER Victor added the comment: Charalampos Stratakis: "Attaching the strace output." Oh thanks! I guess tha the interesting syscalls are: socket(AF_ALG, SOCK_SEQPACKET|SOCK_CLOEXEC, 0) = 3 bind(3, {sa_family=AF_ALG, sa_data="hash\0\0\0\0\0\0\0\0\0\0"}, 88) = 0 accept4(3, NULL, NULL, SOCK_CL

[issue31705] test_sha256 from test_socket fails on ppc64le arch

Charalampos Stratakis added the comment: Attaching the strace output. -- Added file: https://bugs.python.org/file47202/trace ___ Python tracker ___

[issue31705] test_sha256 from test_socket fails on ppc64le arch

Charalampos Stratakis added the comment: Forgot the mention the kernel version which is 3.10.0-693.2.1.el7.ppc64le -- ___ Python tracker ___ ___

[issue31705] test_sha256 from test_socket fails on ppc64le arch

STINNER Victor added the comment: > The issue is reproducible on a CentOS 7.4 on ppc64le architecture. What is the kernel version? It would be nice to have the strace output. Example: strace -o trace ./python -m test -v test_socket -m test_sha256 # then get the trace file I'm surprised becau

[issue31705] test_sha256 from test_socket fails on ppc64le arch

Change by Charalampos Stratakis : -- nosy: +christian.heimes ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue31705] test_sha256 from test_socket fails on ppc64le arch

New submission from Charalampos Stratakis : The issue is reproducible on a CentOS 7.4 on ppc64le architecture. It passes successfully on other arch's (however the other power pc arch's might also be affected). How to reproduce: Compile python 3.6 from source. Run ./python3 -m test --verbose