Fix how virtual_packet properties are saved in hdf #1254
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes sure that vpacket logging status is determined at run-time, thus removes any need of saving to a config file.
Description
vpacket_logging.yml
config file creation code implemented in log additional properties in hdf witeout when --with-vpacket-logging is present #967runner.virt_logging
to check if vpacket logging is enabled or not within hdfMotivation and Context
Fixes #1246
How Has This Been Tested?
vpacket_hdf_properties
get saved.vpacket_hdf_properties
get saved.Screenshots (if appropriate):
Types of changes
Checklist: