Skip to content
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

Open
rndquu opened this issue Oct 3, 2024 · 9 comments · May be fixed by #974
Open

CI: fix check_storage_layout for new contracts #972

rndquu opened this issue Oct 3, 2024 · 9 comments · May be fixed by #974

Comments

@rndquu
Copy link
Member

rndquu commented Oct 3, 2024

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:

  1. core-contracts-storage-check is not failing for newly added contracts
  2. diamond-storage-check.yml is not failing for newly added libraries

P.S. Pls provide a QA in the related PR with these scenarios:

  1. No storage updates, CI passing
  2. Storage update, no collision, CI passing
  3. Storage update, collision, CI failing
  4. New contract added, CI passing
@zugdev
Copy link
Contributor

zugdev commented Oct 3, 2024

/start

Copy link

ubiquity-os bot commented Oct 3, 2024

Deadline Thu, Oct 3, 4:55 PM UTC
Beneficiary 0xbB689fDAbBfc0ae9102863E011D3f897b079c80F

Tip

  • Use /wallet 0x0000...0000 if you want to update your registered payment wallet address.
  • Be sure to open a draft pull request as soon as possible to communicate updates on your progress.
  • Be sure to provide timely updates to us when requested, or you will be automatically unassigned from the task.

@zugdev
Copy link
Contributor

zugdev commented Oct 3, 2024

Can use tj-actions/changed-files for this.

@rndquu
Copy link
Member Author

rndquu commented Oct 3, 2024

Can use tj-actions/changed-files for this.

uses: tj-actions/changed-files@v42

@rndquu
Copy link
Member Author

rndquu commented Oct 3, 2024

I suppose the simplest solution would be to add a new job step here and here to filter modifed contracts that exist both in the PR and default branches.

@zugdev
Copy link
Contributor

zugdev commented Oct 3, 2024

Yes already got it. I meant using tj-actions to see if contract existed last commit in whatever branch.

@zugdev
Copy link
Contributor

zugdev commented Oct 15, 2024

I should be reassigned here, waiting for review.

Copy link

ubiquity-os bot commented Oct 16, 2024

@zugdev the deadline is at Wed, Oct 16, 8:20 AM UTC

Copy link

ubiquity-os bot commented Nov 12, 2024

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
Projects
None yet
2 participants