feat: testing function for partitioned and cached traces #486
Conversation
This file contains 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
OsamaAlkhodairy
force-pushed
the
feat/test-cached-traces
branch
from
151d9b2 to
902a530
Compare
jonathanpwang
approved these changes
Oct 1, 2024
There was a problem hiding this comment.
Great! Maybe this can save @nyunyunyunyu some work - we were discussing further automating some parts of the keygen to remove matrix pointers.
Will let @nyunyunyunyu merge in case there's any conflicts with what he's currently doing.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added test functions to StarkEngine that automatically do keygen, proving, and verifying when partitions of the trace are cached, utilizing #481. Edited the tests for
IndexedOutputPageAirto showcase usage. Much cleaner now!Relevant to INT-2203