Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when running machinestate/comparing JSONs without likwid #2

Open
JanLJL opened this issue Jun 16, 2020 · 3 comments
Open

Error when running machinestate/comparing JSONs without likwid #2

JanLJL opened this issue Jun 16, 2020 · 3 comments

Comments

@JanLJL
Copy link
Contributor

JanLJL commented Jun 16, 2020

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
@TomTheBear
Copy link
Member

"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.

@TomTheBear
Copy link
Member

Can you please test the latest version because I'm not able to reproduce your problem on any of my machines.

@JanLJL
Copy link
Contributor Author

JanLJL commented Jun 17, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants