The native emitter will not release/bounce the GIL when running code, so if it runs tight loops then no other threads get a chance to run (if the GIL is enabled). So for the thread tests, explicitly include a call to `time.sleep(0)` (or equivalent) to bounce the GIL and give other threads a chance to run. For some tests (eg `thread_coop.py`) the whole point of the test is to test that the GIL is correctly bounced. So for those cases force the use of the bytecode emitter for the busy functions. Signed-off-by: Damien George <damien@micropython.org>
36 lines
736 B
Python
36 lines
736 B
Python
# test capability for threads to access a shared mutable data structure
|
|
# (without contention because they access different parts of the structure)
|
|
#
|
|
# MIT license; Copyright (c) 2016 Damien P. George on behalf of Pycom Ltd
|
|
|
|
import time
|
|
import _thread
|
|
|
|
|
|
def foo(lst, i):
|
|
lst[i] += 1
|
|
|
|
|
|
def thread_entry(n, lst, idx):
|
|
for i in range(n):
|
|
foo(lst, idx)
|
|
with lock:
|
|
global n_finished
|
|
n_finished += 1
|
|
|
|
|
|
lock = _thread.allocate_lock()
|
|
n_thread = 2
|
|
n_finished = 0
|
|
|
|
# the shared data structure
|
|
lst = [0, 0]
|
|
|
|
# spawn threads
|
|
for i in range(n_thread):
|
|
_thread.start_new_thread(thread_entry, ((i + 1) * 10, lst, i))
|
|
|
|
# busy wait for threads to finish
|
|
while n_finished < n_thread:
|
|
time.sleep(0)
|
|
print(lst)
|