Skip to content

bpo-31705: Skip test_socket.test_sha256() on ppc64 #4643

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 30, 2017
Merged

bpo-31705: Skip test_socket.test_sha256() on ppc64 #4643

merged 1 commit into from
Nov 30, 2017

Conversation

vstinner
Copy link
Member

@vstinner vstinner commented Nov 30, 2017

Skip test_socket.test_sha256() on ppc64 for kernel version older than
4.11.

https://bugs.python.org/issue31705

@vstinner
Copy link
Member Author

My first patch only skipped the test_sha256() on kernel < 4.11 on ppc64. My second patch skipped test_sha256() on kernel < 4.5 for any architecture. My third patch added a NEWS enty. Ok, now we should be good :-)

Copy link
Member

@tiran tiran left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

The test isn't that important. I'm totally fine with skipping it on older Linux Kernels. It's not our business to verify the Kernel API. :)

@vstinner vstinner merged commit 86afc1f into python:master Nov 30, 2017
@miss-islington
Copy link
Contributor

Thanks @vstinner for the PR 🌮🎉.. I'm working now to backport this PR to: 3.6.
🐍🍒⛏🤖 I'm not a witch! I'm not a witch!

@vstinner vstinner deleted the sha256_ppc64 branch November 30, 2017 12:58
@bedevere-bot
Copy link

GH-4645 is a backport of this pull request to the 3.6 branch.

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Nov 30, 2017
vstinner pushed a commit that referenced this pull request Nov 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants