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

state_sync_massive.py fails with timeout #3130

Closed
SkidanovAlex opened this issue Aug 11, 2020 · 2 comments · Fixed by #3208
Closed

state_sync_massive.py fails with timeout #3130

SkidanovAlex opened this issue Aug 11, 2020 · 2 comments · Fixed by #3208
Assignees
Labels
A-chain Area: Chain, client & related A-python-test Area: issues related to python tests

Comments

@SkidanovAlex
Copy link
Collaborator

http://52.149.162.182:3000/#/test/7613

@MaksymZavershynskyi
Copy link
Contributor

MaksymZavershynskyi commented Sep 21, 2020

For the record, according to @mfornet the solution is to move it to MockNet.

@bowenwang1996 bowenwang1996 added the A-python-test Area: issues related to python tests label Sep 21, 2020
@bowenwang1996
Copy link
Collaborator

Discussed with @mfornet. He will try again to fix the test within nayduck and if it fails, he will move it to mocknet. Updated the estimate according to the new plan.

nearprotocol-bulldozer bot pushed a commit that referenced this issue Sep 25, 2020
Epoch length was too short (20) and observer when tried
to sync, used old epoch, but right now, trying to sync from
any epoch other than current epoch or previous epoch is considered
malicious behavior.

Fixes #3130

Test plan
======

state_sync_massive.py passes in nightly
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-chain Area: Chain, client & related A-python-test Area: issues related to python tests
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants