Skip to content

Conversation

@shohamc1
Copy link
Member

Making changes to MDBX tables does not result in failing RPC tests.

@shohamc1 shohamc1 requested review from canepat and mriccobene August 15, 2025 14:41
@shohamc1 shohamc1 enabled auto-merge (squash) August 15, 2025 14:41
@shohamc1 shohamc1 merged commit 7772141 into main Aug 16, 2025
17 of 20 checks passed
@shohamc1 shohamc1 deleted the shohamc1/qa-run-migrations branch August 16, 2025 02:52
shohamc1 pushed a commit that referenced this pull request Aug 20, 2025
Starting from #16678, we've tried using `integration run_migrations`
within RPC Integration Tests CI workflows to handle creation of new
tables automatically: it worked immediately for Ethereum, but failed for
both Gnosis and Polygon.

Some changes to `integration run_migrations` are necessary to make it
work for them:

- Gnosis: migrations must work also for `consensus` database, which is
used there because pre-Merge consensus was AuRa. `ConsensusTables` used
within `consensus` database already contained all `ChaindataTables`, so
just running the migrations on the `consensus` database is sufficient.
- Polygon: migrations must work also for both `heimdall` and
`polygon-bridge` databases, which are used by internal Polygon
components. In order to use exactly the same run migration procedure, we
need to create all `ChaindataTables` also there. Of course, this is not
ideal but IMO should be addressed as a separate issue (namely,
refactoring and improvement of run migration procedure not to require
the same tables in all databases).
canepat pushed a commit that referenced this pull request Sep 1, 2025
Making changes to MDBX tables does not result in failing RPC tests.
canepat pushed a commit that referenced this pull request Sep 1, 2025
Making changes to MDBX tables does not result in failing RPC tests.
AskAlexSharov pushed a commit that referenced this pull request Sep 2, 2025
…16935)

Cherry-pick #16678
Cherry-pick #16711
Cherry-pick #16762

---------

Co-authored-by: Shoham Chakraborty <[email protected]>
yperbasis pushed a commit that referenced this pull request Sep 12, 2025
…16936)

Cherry-pick #16678
Cherry-pick #16711
Cherry-pick #16762

---------

Co-authored-by: Shoham Chakraborty <[email protected]>
NazariiDenha pushed a commit that referenced this pull request Oct 24, 2025
Making changes to MDBX tables does not result in failing RPC tests.
NazariiDenha pushed a commit that referenced this pull request Oct 24, 2025
Starting from #16678, we've tried using `integration run_migrations`
within RPC Integration Tests CI workflows to handle creation of new
tables automatically: it worked immediately for Ethereum, but failed for
both Gnosis and Polygon.

Some changes to `integration run_migrations` are necessary to make it
work for them:

- Gnosis: migrations must work also for `consensus` database, which is
used there because pre-Merge consensus was AuRa. `ConsensusTables` used
within `consensus` database already contained all `ChaindataTables`, so
just running the migrations on the `consensus` database is sufficient.
- Polygon: migrations must work also for both `heimdall` and
`polygon-bridge` databases, which are used by internal Polygon
components. In order to use exactly the same run migration procedure, we
need to create all `ChaindataTables` also there. Of course, this is not
ideal but IMO should be addressed as a separate issue (namely,
refactoring and improvement of run migration procedure not to require
the same tables in all databases).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants