[issue46788] regrtest fails to start on missing performance counter names

Change by Eryk Sun : Removed file: https://bugs.python.org/file50695/loadtracker.py ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue46788] regrtest fails to start on missing performance counter names

Change by Eryk Sun : -- Removed message: https://bugs.python.org/msg415781 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue46788] regrtest fails to start on missing performance counter names

Steve Dower added the comment: Backports have been merged -- resolution: -> fixed stage: backport needed -> resolved status: open -> closed ___ Python tracker ___ ___

[issue46788] regrtest fails to start on missing performance counter names

Eryk Sun added the comment: I implemented a ctypes prototype that replaces the registry-based implementation with the API calls PdhOpenQueryW(), PdhAddEnglishCounterW(), PdhCollectQueryData(), PdhGetRawCounterValue(), and PdhCloseQuery(). I'm attaching the script, but here's the class itself

[issue46788] regrtest fails to start on missing performance counter names

Jeremy Kloth added the comment: Backports state that they are ready... I'm just a little uneasy as I've never used cherry_picker before. 3.10 went smooth, but 3.9 required manual merging. -- ___ Python tracker

[issue46788] regrtest fails to start on missing performance counter names

Steve Dower added the comment: Jeremy - backports need to be done manually. Can I leave that with you and just ping me on here when you're ready for a merge? -- stage: -> backport needed ___ Python tracker ___

[issue46788] regrtest fails to start on missing performance counter names

Eryk Sun added the comment: I was just wondering whether it's worth implementing it using the API. To be clear, I wasn't implying to hold off on applying Jeremy's PR. The existing code is causing him problems, and he has a working solution. -- nosy: +eryksun

[issue46788] regrtest fails to start on missing performance counter names

Steve Dower added the comment: "So close" being some months ago ;) I need to retrigger address sanitiser so that it passes before merging, but after that, I'll merge (and hopefully the backport is clean). Copying Eryk Sun's comment here for posterity: This would be less fragile and more use

[issue46788] regrtest fails to start on missing performance counter names

Jeremy Kloth added the comment: With 3.8 so close to security only, I would doubt it is worth it anymore. I've just run the PR against HEAD and it still works as is, so should be good to go. -- versions: -Python 3.8 ___ Python tracker

[issue46788] regrtest fails to start on missing performance counter names

Steve Dower added the comment: You're closer to this stuff than I am, so if you say it works for your scenarios and it doesn't break the existing ones, I'll merge it. Do we need to backport to 3.8 at this point? -- ___ Python tracker

[issue46788] regrtest fails to start on missing performance counter names

Jeremy Kloth added the comment: OK, I know it has been a busy month for Python, but this issue is really hampering my bug fixing efforts. It makes the complete regrtest useless for me. I am required to run each affected test directly so it is possible to miss side-effects of changes made.

[issue46788] regrtest fails to start on missing performance counter names

Change by Jeremy Kloth : -- nosy: +vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue46788] regrtest fails to start on missing performance counter names

New submission from Jeremy Kloth : When attempting to run the test harness, I receive the following: Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "C:\Public\Devel\cpython\main\Lib\test\__main__.py", line 2, in main()