Fix N150 llama3 demo CI tests to properly save perf information to superset #15220
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.
Final change to these CI tests after another back and forth:
Before we were running Llama3 on both N150 and N300 as intended. However the N150 functional pipeline does not upload the perf data to superset, nor does it run on the perf VMs.
This PR changes that.
Instead of running Llama on N150 pipeline, we run them twice on the N300 perf:
FAKE_DEVICE=N150
which forces a single-chip execution and saves the N150 perf to superset.To make sure this is the last change we are running the CI test and will make sure all the data is uploaded before committing this.