WIP: ci: Verify mapfile.csv metric entries #314
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 pull request expands automated
mapfile.csv
checks. Specifically focusing on content such as https://github.com/intel/perfmon/blob/main/GNR/metrics/graniterapids_retire_latency.json and https://github.com/intel/perfmon/blob/main/GNR/metrics/graniterapids_metrics.json . The goal is to prevent accidents when updatingmapfile.csv
. See #312 as an example where I previously dropped retire latency data.**/metrics/*.json
are mentioned inmapfile.csv
.GenuineIntel-6-BE
missingalderlake_metrics_goldencove_core.json
are ignored. ADL-N is an E-Core only product.sapphirerapidshbm_metrics.json
are ignored. Onlysapphirerapids_metrics.json
will be mentioned inmapfile.csv
.Follow-up commits add missing files to
mapfile.csv
as identified by this check.