[issue36670] test suite broken due to cpu usage feature on win 10/ german

Change by STINNER Victor : -- nosy: +vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36670] test suite broken due to cpu usage feature on win 10/ german

Change by Steve Dower : -- keywords: +easy, newcomer friendly ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36670] test suite broken due to cpu usage feature on win 10/ german

Change by Steve Dower : -- stage: -> needs patch versions: +Python 3.8, Python 3.9 ___ Python tracker ___ ___ Python-bugs-list

[issue36670] test suite broken due to cpu usage feature on win 10/ german

Sebastian Koslowski added the comment: I ran into this issue on a Win10 German box running the tests for version 3.7.4 Your changes fixes the issue for me. -- nosy: +skoslowski versions: +Python 3.7 -Python 3.8 ___ Python tracker

[issue36670] test suite broken due to cpu usage feature on win 10/ german

Lorenz Mende added the comment: Did some minor changes with win_utils. Encoding changed to 'oem'. @heckad: does this bugfix work for u? @all: please verify working of the changes with different localizations. thx -- Added file: https://bugs.python.org/file48406/win_utils.py

[issue36670] test suite broken due to cpu usage feature on win 10/ german

Change by Lorenz Mende : Removed file: https://bugs.python.org/file48285/win_utils.py ___ Python tracker ___ ___ Python-bugs-list mailing

[issue36670] test suite broken due to cpu usage feature on win 10/ german

Change by Terry J. Reedy : -- nosy: -terry.reedy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36670] test suite broken due to cpu usage feature on win 10/ german

Андрей Казанцев added the comment: I have the same problem in Russian locale. Adding "oem" encoding in the decode method solve problem with decoding but got: File "C:\Users\User\Documents\Projects\cpython\lib\test\libregrtest\win_utils.py", line 98, in getloadavg load =

[issue36670] test suite broken due to cpu usage feature on win 10/ german

Eryk Sun added the comment: It's "oem", not "mbcs". -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36670] test suite broken due to cpu usage feature on win 10/ german

Lorenz Mende added the comment: Sorry, was off some days. I tried to decode the output with mbcs, solves the issue partly - the counter name is still wrong. Was able to pick the localization specific counter name from registry and use it for the typeperf. But the tests fail after several

[issue36670] test suite broken due to cpu usage feature on win 10/ german

Steve Dower added the comment: If the code page is set to UTF-8 then mbcs will still be the right encoding :) -- ___ Python tracker ___

[issue36670] test suite broken due to cpu usage feature on win 10/ german

Eryk Sun added the comment: > It'll probably be mbcs or oem encoding. Certainly not UTF-8 Unless the system locale's codepage is set to UTF-8 in Windows 10. I stepped through this in the debugger. When writing to a pipe, typeperf.exe calls WideCharToMultiByte(CP_OEMCP, ...), so it's "oem".

[issue36670] test suite broken due to cpu usage feature on win 10/ german

Steve Dower added the comment: It'll probably be mbcs or oem encoding. Certainly not UTF-8 -- ___ Python tracker ___ ___

[issue36670] test suite broken due to cpu usage feature on win 10/ german

Terry J. Reedy added the comment: 'crash' mean *nix coredump or Windows equivelent, rather than traceback. -- components: +Windows nosy: +paul.moore, steve.dower, terry.reedy, tim.golden, zach.ware type: crash -> behavior ___ Python tracker

[issue36670] test suite broken due to cpu usage feature on win 10/ german

Ammar Askar added the comment: Thank you, could you also share the output if you just give it the English name of the counter? -- ___ Python tracker ___

[issue36670] test suite broken due to cpu usage feature on win 10/ german

Lorenz Mende added the comment: Hi Ammar, you are correct. typeperf returns: P:\Repos\CPython\cpython>typeperf "\System\Prozessor-Warteschlangenlänge" -si 1 "(PDH-CSV 4.0)","\\ZERO\System\Prozessor-Warteschlangenlänge" "04/19/2019 19:09:14.510","0.00" "04/19/2019 19:09:15.514","0.00"

[issue36670] test suite broken due to cpu usage feature on win 10/ german

Ammar Askar added the comment: What does `typeperf "\System\Processor Queue Length" -si 1` actually return on your non-English system? Does it just return an error with the counter's name or is the umalet just in the first header line, i.e this one for me: "(PDH-CSV

[issue36670] test suite broken due to cpu usage feature on win 10/ german

Change by Lorenz Mende : -- nosy: -ammar2 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36670] test suite broken due to cpu usage feature on win 10/ german

Change by Lorenz Mende : -- nosy: +ammar2 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36670] test suite broken due to cpu usage feature on win 10/ german

New submission from Lorenz Mende : The test suite fails with the first tests (I assume 1st call of getloadavg of WindowsLoadTracker). Traceback (most recent call last): File "P:\Repos\CPython\cpython\lib\runpy.py", line 192, in _run_module_as_main return _run_code(code, main_globals,