Skip to content

Error when running machinestate/comparing JSONs without likwid #2

@JanLJL

Description

@JanLJL

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions