-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
test: actually use masternode with basic bls pubkey in mnauth test #6481
Conversation
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.
makes sense, and change looks right.
utACK 3db20e3
@@ -21,8 +21,9 @@ def set_test_params(self): | |||
|
|||
def run_test(self): | |||
self.activate_v19(expected_activation_height=900) | |||
self.dynamically_add_masternode() |
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.
I believe we don't need 2 of them:
-self.set_dash_test_params(2, 1)
+self.set_dash_test_params(1, 0)
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.
utACK ec00c37
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.
utACK ec00c37
Issue being fixed or feature implemented
rpc_manuth
is failing in ~50% cases locally because we still use legacy pubkeys (not in 100% cases because sometimes they look like basic ones). In CI it fails too but we retry failed tests a few times so it's less noticeable. Example of "unlucky" tests: https://gitlab.com/dashpay/dash/-/jobs/8613271300#L1867.#6467 follow-up
What was done?
Add another masternode after v19 activaition to actually use basic bls pubkey
How Has This Been Tested?
run tests
Breaking Changes
n/a
Checklist: