Skip to content
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

Randomized Fuzzer: should not already be unbonded or unbonding, validator: #2290

Closed
ValarDragon opened this issue Sep 10, 2018 · 7 comments
Closed

Comments

@ValarDragon
Copy link
Contributor

ValarDragon commented Sep 10, 2018

Summary of Bug

Fuzzer panicked with

should not already be unbonded or unbonding, validator: {88E4C3BCC83F2A2EAE76AAC97E01371550303EED PubKeySecp256k1{02E7B647FEBC1A01C7957C35293572641E3E9356FAA7746795EAFE66673CC1189C} false 1 410000000000 410000000000 {ICfZpMBJbx tWSzirnbop WTodiGqFSy skAdRchwnB} 24 9 2 15059-02-26 19:36:45 +0000 UTC 0 0 0 0}

Steps to Reproduce

This is achieved by commenting out "// govsim.SimulateMsgDeposit(app.govKeeper, app.stakeKeeper),", and then running:

	go test ./cmd/gaia/app -run TestFullGaiaSimulation -SimulationSeed=3 -SimulationEnabled=true -SimulationNumBlocks=400 -SimulationBlockSize=400 -v -timeout 24h

error happens on block 24, so super quick.
You can also replicate this on other seeds, e.g. seed=2

@cwgoes
Copy link
Contributor

cwgoes commented Sep 12, 2018

After merging #2238 into develop I can't immediately replicate this again but we should keep trying.

@ValarDragon
Copy link
Contributor Author

I can't replicate this either. Perhaps we should close it and re-open if its found again?

@cwgoes
Copy link
Contributor

cwgoes commented Sep 12, 2018

I can't replicate this either. Perhaps we should close it and re-open if its found again?

Let's wait for the multi-seed PR - #2313. I don't immediately understand why #2238 would have fixed this.

@alexanderbez
Copy link
Contributor

Maybe something to do with bond height for validators entering the validator set by proxy/side effect?

@alexanderbez
Copy link
Contributor

Closing in favor of #2312.

@alexanderbez
Copy link
Contributor

Actually, re-opening this to keep track of the issue.

@alexanderbez alexanderbez reopened this Sep 25, 2018
@cwgoes
Copy link
Contributor

cwgoes commented Oct 9, 2018

This has likely been fixed by the staking refactor. Please reopen if it can be replicated.

@cwgoes cwgoes closed this as completed Oct 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants