Minimize redundancy in IOSimPOR logs #160
Labels
enhancement
New feature or request
IOSimPOR
Issues / PRs related to IOSimPOR
trace
Issues / PRs related to IOSim trace
Is your feature request related to a problem? Please describe.
Recently I had to debug a IOSimPOR test failure (See #154) and although IOSimPOR is complicated, analysing the logs adds an extra layer of difficulty because the logs are quite large and have a lot of redundant information. I'll explain:
Here's the excerpt of a log for an IOSimPOR run with
explorationDebugLevel = 2
:This is only 1 line worth of trace out of 355 total lines, AND I had to truncate this line of code to not exceed GitHub's limit of 65k words. It has A LOT of useless information.
Describe the solution you'd like
Here's the data types involved in the trace I mentioned above:
One can see how much information there's in each element of
activeRaces
orcompleteRaces
fields. I propose either a refactorisation of these datatypes to avoid redundant information being stored, e.g.:and have a
Map IOSimThreadId Step
somewhere in the state. And the same for other similar places in the code.OR
have a pretty printer with minimal verbosity that doesn't print all the information.
Are you willing to implement it?
The text was updated successfully, but these errors were encountered: