Skip to content
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

[3.7] closes bpo-34004: Skip lock interruption tests on musl. (GH-9224) #9226

Merged
merged 1 commit into from Sep 12, 2018

Conversation

miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Sep 12, 2018

Returning EINTR from pthread semaphore or lock acquisition is an optional POSIX
feature. musl does not provide this feature, so some threadsignal tests fail
when Python is built against it.

There's no good way to test for musl, so we skip if we're on Linux and not using
glibc pthreads.

Also, hedge in the threading documentation about when we can provide interrupts
from lock acquisition.
(cherry picked from commit 5b10d51)

Co-authored-by: Benjamin Peterson benjamin@python.org

https://bugs.python.org/issue34004

Returning EINTR from pthread semaphore or lock acquisition is an optional POSIX
feature. musl does not provide this feature, so some threadsignal tests fail
when Python is built against it.

There's no good way to test for musl, so we skip if we're on Linux and not using
glibc pthreads.

Also, hedge in the threading documentation about when we can provide interrupts
from lock acquisition.
(cherry picked from commit 5b10d51)

Co-authored-by: Benjamin Peterson <benjamin@python.org>
@miss-islington
Copy link
Contributor Author

@benjaminp: Status check is done, and it's a success ✅ .

@miss-islington miss-islington merged commit b608fcd into python:3.7 Sep 12, 2018
@miss-islington miss-islington deleted the backport-5b10d51-3.7 branch September 12, 2018 21:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip news tests Tests in the Lib/test dir
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants