-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
LogPoller ORM: add regression testing for pruning of multichain nodes #14454
Conversation
I see you updated files related to
|
45af65e
45af65e
to
0a0e6fc
Compare
e9f9cb1
to
ba95e1b
Compare
ba95e1b
to
4c2e18d
Compare
Quality Gate passedIssues Measures |
…develop * origin/develop: (233 commits) update Smoke Test TestAutomationBasic to load pre-deployed contracts if given (#14537) CCIP-2881 USDC Reader integration tests (#14516) [TT-1624] link PR to solidity review issue (#14521) Fix skipped notification in E2E test workflow (#14538) Add regression testing for pruning bug (#14454) Bump owner dep (#14531) Fix state view (#14532) Deployment tooling (#14533) CCIP 3388 - add offramp generation (#14526) CCIP-3416 paginate token admin registry get all tokens call (#14514) Change Polygon zkEVM to use FeeHistory estimator (#14161) [TT-1747] fix core changeset (#14524) TT-1459 Use CTF actions from .github repo (#14522) [TT-1693] try more universal Solidity scripts (#14436) Remove unused workflow for e2e tests (#14520) BCI-3668 Optimise HeadTracker's memory usage (#14130) BCFR-888 LP support chains that have not reached finality yet (#14366) support new heads polling over http rpc client (#14373) Bump CTF (#14518) TT-1550 Migrate remaining E2E workflows to the reusable workflow (#14403) ...
There was a 1-line bug fix for the LogPoller pruner that went into a larger commit on develop:
e514727
And a corresponding hotfix for the 2.16.0 release:
#14462
This PR was going to be that change, but since it already went into develop this just adds a regression test for it. Regression test is also a part of the hotfix.
See: BCFR-906
This updates the setup for the orm test for the pruner to include inserting logs for a second chain, and verifies that they don't get removed by the pruning query. Also adds a test for the paged version of the query, and enables parallelism.