-
Notifications
You must be signed in to change notification settings - Fork 0
Add m4 and a18 chipsets #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
80bd0c6 to
0362435
Compare
4678f69 to
26242fb
Compare
54d73ad to
187daed
Compare
| - name: Update benchmarks | ||
| run: npm run update-benchmarks | ||
|
|
||
| - name: Validate *local* benchmark JSON shape |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is where we run the new test to verify that the json generated from the https://gfxbench.com/result.jsp matches the shape we expect
| const tokenizedRenderer = tokenizeForLevenshteinDistance(renderer); | ||
| // eslint-disable-next-line prefer-const | ||
| let [gpu, , , , fpsesByPixelCount] = | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is where their old code was going wrong where it was incorrectly retrieving the placement of where the fpsesByPixelCount should be - so for now to support both data shapes we just assume its the last entry in the array which seems to be accurate between how it used to look and now - if this ever changes again though our test should pick it up
No description provided.