chore: set up storage reports #552
Open
Conversation
This file contains hidden or 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
nadir-akhtar
force-pushed
the
nadir/configure-storage-reports
branch
from
b783d29 to
83585e3
Compare
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.
Motivation:
Storage reports have not been generated for many contracts, and thus a storage report is absent on
dev. This PR sets up storage reports by running./bin/storage-report.shlocally and uploading the generated files.The output of this PR can be verified by pulling this branch and running
./bin/storage-report.shlocally, or by running the script ondevand comparing the output.Modifications:
+as storage report changes by PR and-as what's lost fromdevfor more intuitive parsingResult:
More clear storage analysis for CI