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
Today I ensured that even if some of the runs fail in HIPERmark, HIPERpret will still be able to generate runtime data from the output file tree structure produced by HIPERmark.
But the exported JSONs that HIPERmark produce do not include those runs that have failed. It would be preferable if the exported JSONs included those runs that had failed. This is likely to have to be fixed in the "get_dconf_dicts" --> "belongs_to_dconf" function.
The text was updated successfully, but these errors were encountered:
Sword-Smith
changed the title
Invalid runs
Data from invalid runs is not being exported
Nov 8, 2015
Today I ensured that even if some of the runs fail in HIPERmark, HIPERpret will still be able to generate runtime data from the output file tree structure produced by HIPERmark.
But the exported JSONs that HIPERmark produce do not include those runs that have failed. It would be preferable if the exported JSONs included those runs that had failed. This is likely to have to be fixed in the "get_dconf_dicts" --> "belongs_to_dconf" function.
The text was updated successfully, but these errors were encountered: