tree 876638d2822c22dd03ccbe304c8febd670397aff
parent 9ac2de922a0f783bd43b8e026e4fb70fd1888572
author Jeremy Kloth <jeremy.kloth@gmail.com> 1647907615 -0600
committer GitHub <noreply@github.com> 1647907615 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJiORMfCRBK7hj4Ov3rIwAAQhQIAHJadguuoYVigceHIJhFuh2I
 2gVrBTyfVK6lea/rBb6g0Rz4w25cSIKaHDFAzNdivNYB+Fpu5FSGGyE2WSEGnLhL
 57Hp321t6+P9k8LrP340Xuz7SfeQZGC5QWwRjWSo1qhgBDJuGF38z9dM/rjrXVu5
 Pusg5BEfNZE+TXqRwo30SAdatIe7EVY2oksiMQqCZuGVULalt8ZlpDZXxEpgX6tO
 csO8KxeNw+OwQBkHNp1QRXu/mZr8rz5Jr7dyDp8ajEW4q6dWpD56qjisyaEeSyNU
 fDDtSW+OhJr7wrB7c+Z1QXCU5MSn1yBnaXPUC08BmkNUBgSLdeS4NG6f3OCBqy4=
 =15++
 -----END PGP SIGNATURE-----
 

bpo-44336: Prevent tests hanging on child process handles on Windows (GH-26578)

Replace the child process `typeperf.exe` with a daemon thread that reads the performance counters directly.  This prevents the issues that arise from inherited handles in grandchild processes (see issue37531 for discussion).

We only use the load tracker when running tests in multiprocess mode. This prevents inadvertent interactions with tests expecting a single threaded environment.  Displaying load is really only helpful for buildbots running in multiprocess mode anyway.