Fix benchmark version and release date in tailoring files#120
Merged
Conversation
This fixes the issue of the tailoring files (and thus report) having the same description, version, and release_date regardless of which benchmark they are associated with. The benchmark version and release date are now parametrized in the tailoring file template and replaced at build time. Other changes: - tailoring file templates use string.Template placeholders - introduced 'release_date' to benchmark release metadata - introduced 'latest_benchmark_id' to channel data - switched to YAML BaseLoader and cast fields explicitly
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The benchmark version and release date are now parametrized in the tailoring file template and replaced at build time.
This fixes the issue of the tailoring files (and thus report) having the same description, version, and release_date regardless of which benchmark they are associated with.
Related bug report: https://bugs.launchpad.net/usg/+bug/2142286
Other changes: