You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running machinestate without likwid, the attribute PerfEnergyBias has value similiar like this:
...
"PerfEnergyBias": "ERROR - [./src/access_client.c:189] No such file or directory\nExiting due to timeout: The socket file at '/tmp/likwid-9098' could not be\nopened within 10 seconds. Consult the error message above\nthis to find out why. If the error is 'no such file or directoy',\nit usually means that likwid-accessD just failed to start."
...
Furthermore, whenever I do another run it (obviously) prints a different four-digit-number as part of the socket file, therefore, when comparing two machine states with -j option, I get an error due to a mismatch in this string:
$ machinestate -j old_state.json
ERROR: Equality check failed for key 'PerfEnergyBias' for class TurboInfo
The current state differs at least in one setting with input file
The text was updated successfully, but these errors were encountered:
"Without likwid" cannot be true as the string is an error coming from LIKWID. The mismatch is probable the ID of the UNIX socket The socket file at '/tmp/likwid-9098' as you pointed out.
It seems the regex for matching is not specific enough.
Thanks for reporting.
Hi @TomTheBear,
this issue occurs on my WSL 2 (with Ubuntu 20.04) so this is probably why in that case likwid cannot be installed correctly. 9d5b885 didn't help but the issue might be neglected since I don't have any use case for running machinestate on WSL.
When running machinestate without likwid, the attribute
PerfEnergyBias
has value similiar like this:Furthermore, whenever I do another run it (obviously) prints a different four-digit-number as part of the socket file, therefore, when comparing two machine states with
-j
option, I get an error due to a mismatch in this string:The text was updated successfully, but these errors were encountered: