Fix test_jumpstart_network
by waiting longer to jumpstart network
#1316
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.
Was able to reproduce error locally, with extra logging I ruled out some theories
Found through logging chain data that with all the infastructure running one chain node would just fall behind, catch up too late and not work, this is mitigated by waiting longer to run jumpstart so every node can catch up
you can see this in logs of a failed run 2 nodes fire a tss OCW message, one does but only after the others have timed out waiting.
for testing ran locally and in CI multiple times