android: test_concurrent_futures hangs on armv7

[xdegaye]

BPO	26938
Nosy	@brianquinlan, @xdegaye, @moreati

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2016-05-16.15:26:54.703>
created_at = <Date 2016-05-03.15:32:10.882>
labels = ['type-bug', 'library', 'build']
title = 'android: test_concurrent_futures hangs on armv7'
updated_at = <Date 2016-05-16.15:26:54.701>
user = 'https://github.com/xdegaye'

bugs.python.org fields:

activity = <Date 2016-05-16.15:26:54.701>
actor = 'xdegaye'
assignee = 'none'
closed = True
closed_date = <Date 2016-05-16.15:26:54.703>
closer = 'xdegaye'
components = ['Library (Lib)', 'Cross-Build']
creation = <Date 2016-05-03.15:32:10.882>
creator = 'xdegaye'
dependencies = []
files = []
hgrepos = []
issue_num = 26938
keywords = []
message_count = 4.0
messages = ['264740', '264757', '265012', '265698']
nosy_count = 3.0
nosy_names = ['bquinlan', 'xdegaye', 'Alex.Willmer']
pr_nums = []
priority = 'normal'
resolution = 'wont fix'
stage = None
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue26938'
versions = ['Python 3.6']

[xdegaye]

test_concurrent_futures hangs on an android emulator running an armv7 system image (but not on x86) at API level 21. The test suite hangs at:

test_pending_calls_race (test.test_concurrent_futures.ThreadPoolWaitTests) ...

A cause of this problem may be related to the fact that the android arm emulator runs very, very slowly.

[xdegaye]

Interestingly, all the tests (issues bpo-26938, bpo-26939, bpo-26940 and bpo-26941) that hang on arm use sys.setswitchinterval() aggressively.

[xdegaye]

The strace output, the process is blocked in a futex system call:

root@generic:/ # strace -p 1304
Process 1304 attached
futex(0xb6f24880, FUTEX_WAIT_PRIVATE, 2, NULL

[xdegaye]

test_concurrent_futures is not run on Android because "This platform lacks a functioning sem_open implementation", see issue bpo-26924.

Closing as won't fix.