diff options
author | Ammar Askar <ammar_askar@hotmail.com> | 2019-04-09 12:20:41 (GMT) |
---|---|---|
committer | Cheryl Sabella <cheryl.sabella@gmail.com> | 2019-04-09 12:20:41 (GMT) |
commit | e16467af0bfcc9f399df251495ff2d2ad20a1669 (patch) | |
tree | ee3c0cbd23c0e5a04fd8de12368a47bfcb184e09 /m4 | |
parent | c324c748871804f31f56b3bd02a8650b3bf1bae7 (diff) | |
download | cpython-e16467af0bfcc9f399df251495ff2d2ad20a1669.zip cpython-e16467af0bfcc9f399df251495ff2d2ad20a1669.tar.gz cpython-e16467af0bfcc9f399df251495ff2d2ad20a1669.tar.bz2 |
bpo-34060: Report system load when running test suite for Windows (GH-8357)
While Windows exposes the system processor queue length, the raw value
used for load calculations on Unix systems, it does not provide an API
to access the averaged value. Hence to calculate the load we must track
and average it ourselves. We can't use multiprocessing or a thread to
read it in the background while the tests run since using those would
conflict with test_multiprocessing and test_xxsubprocess.
Thus, we use Window's asynchronous IO API to run the tracker in the
background with it sampling at the correct rate. When we wish to access
the load we check to see if there's new data on the stream, if there is,
we update our load values.
Diffstat (limited to 'm4')
0 files changed, 0 insertions, 0 deletions