Fix duplicate model_names for llama2-70b benchmarks #1356
Closed
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.
Description
There are several benchmarks named
llama2_70b_4096
. I tried to run this benchmark but was getting a different config then expected. A different llama2 benchmark with the same name was getting pulled instead of mine. This PR changes the other benchmark names to reduce duplicates.Tests
Checklist
Before submitting this PR, please make sure (put X in square brackets):