This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
[1.8.x] 10 second sleep to address heavy usage wait-network bug in Anka #8183
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Description
Anka has a wait-network option which supposedly waits for networking to start before executing commands. Confirmed that's not the case and was able to manually replicate the failures happening in https://buildkite.com/EOSIO/eosio/builds/18583#947fc053-3cfa-406a-9bd2-e1828f517b1b
The only solutions are to expand the fleet with more hardware or increase the sleep time before commands execute. We'll have to increase the sleep time.
Consensus Changes
API Changes
Documentation Additions