Message321902
| Author | vstinner |
|---|---|
| Recipients | ammar2, giampaolo.rodola, jkloth, paul.moore, steve.dower, tim.golden, vstinner, zach.ware |
| Date | 2018-07-18.17:10:07 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1531933807.52.0.56676864532.issue34060@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> I also haven't seen it suggested, but perhaps GetProcessTimes (https://docs.microsoft.com/en-us/windows/desktop/api/processthreadsapi/nf-processthreadsapi-getprocesstimes) (or GetThreadTimes) would provide enough information to detect the same information? My intent is to get an idea if the whole system is busy. Not if the current Python process is busy. Most buildbots run tests with multiple worker processes (at least 2). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-07-18 17:10:07 | vstinner | set | recipients: + vstinner, paul.moore, giampaolo.rodola, tim.golden, jkloth, zach.ware, steve.dower, ammar2 |
| 2018-07-18 17:10:07 | vstinner | set | messageid: <1531933807.52.0.56676864532.issue34060@psf.upfronthosting.co.za> |
| 2018-07-18 17:10:07 | vstinner | link | issue34060 messages |
| 2018-07-18 17:10:07 | vstinner | create | |