| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
Depending on the thread scheduler, a busy-wait loop can hog the CPU and
make the tests very slow. So convert such loops to loops that have an
explicit sleep, allowing the worker threads to do their job.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Qstr code accesses global state and needs to be made thread safe.
|
|
Tests concurrent mutating access to: list, dict, set, bytearray.
|
|
|
|
|
|
Use a lock and a counter instead, and busy wait for all threads to
complete. This makes test run faster and they no longer rely on the time
module.
|
|
|
|
Includes functionality and stress tests.
|
