-
Notifications
You must be signed in to change notification settings - Fork 91
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
CI: fix check_storage_layout
for new contracts
#972
Comments
/start |
Tip
|
Can use tj-actions/changed-files for this. |
|
Yes already got it. I meant using tj-actions to see if contract existed last commit in whatever branch. |
This was referenced Oct 3, 2024
I should be reassigned here, waiting for review. |
@zugdev the deadline is at Wed, Oct 16, 8:20 AM UTC |
Passed the deadline and no activity is detected, removing assignees: @zugdev. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There's the core-contracts-storage-check workflow which checks that contracts' storage is not messed on contract upgrades.
Check these CI runs which fails with the
No workflow run found with an artifact named...
error:The issue is that when a new contract is added the core-contracts-storage-check starts to fail while the expected behavior for the CI workflow to pass because we don't need to check storage layout for newly added contracts (because storage of the newly added contract hasn't been updated hence storage collision could not occur).
So as a part of this issue we should make sure that:
P.S. Pls provide a QA in the related PR with these scenarios:
The text was updated successfully, but these errors were encountered: