-
Notifications
You must be signed in to change notification settings - Fork 707
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
Staking Fuzzer to test nomination pool commission & absent calls #424
Comments
@rossbulat I do think this is something that we should not omit for later, ideally we should have the code for this and the fuzzer ready, before this feature goes to Polkadot. |
Not sure if the staking fuzzers are already integrated into the CI, otherwise we have to do something similar to paritytech/substrate#13673 |
for Posting some notes to go by for implementing these changes:
For an operator specific random loop:
Although not an exhaustive set of scenarios (change rate, setting more restrictive commissions / max commissions) I think the above steps will bootstrap the fuzzer with basic commission testing and aid in future iterations where we can expand to cover all scenarios. |
The fuzzer fails on master: |
For me running
I assume this can only be tested in a VM / on a server if one is on Apple Silicon. |
Do you have |
Yes, we should add the existing fuzzer to the CI + make sure the commission feature is integrated into it. |
We can even do that async and allow it to fail in the CI now. |
I've got a PR ready to enable the nomination pool fuzzer. It still fails on master though, can we get that fixed? |
Motivation
Full coverage of fuzzer testing.
Request
@kianenigma: fuzzer code might need some extra change to add an "agent" that behaves like a pool operator with commission, who will change their commission a bunch of times, and we will compute on the side how much we will think they should earn in sum commission, and then we will check it.
Enhances testing for paritytech/substrate#13128 and paritytech/substrate#12608.
Solution
No response
Are you willing to help with this request?
Yes!
The text was updated successfully, but these errors were encountered: