-
Notifications
You must be signed in to change notification settings - Fork 3
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
[PVM] Introduced e2e test for claiming validator rewards #66
Conversation
968f5b6
to
2bea571
Compare
|
21da935
to
3c47dc9
Compare
Checked logs. This error is expected and according to @evlekht should not be removed as it indicates problems if and only if it persists. In our case, it gets printed only cause of the first runs of a network with no previous transactions |
3c47dc9
to
85813a2
Compare
jest.config.js
Outdated
testSequencer: "<rootDir>/e2eSequencer.js", | ||
testTimeout: 300000 // 5 minutes | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pls. add a newline, after this we can go....
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
85813a2
to
48aa29a
Compare
Why this should be merged
To add test coverage to the scenario of a validator claiming rewards. These rewards get exported to from C->P after an adequate number of txs on cchain have accumulated enough gas fees.
The PR addresses the following 2 issues:
How this works
A dummy SC is deployed repeatedly on C Chain to accumulate gas fees. Then enough time (>feeRewardExportMinTimeInterval) is waited and a claim tx for a minimum amount is triggered for one of the validators. Finally, it's verified the claim tx gets committed and that the unlocked amounts of the validator are increased accordingly
How this was tested
Via newly introduced e2e test.