-
Notifications
You must be signed in to change notification settings - Fork 122
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
feat: check for panic in logs on start #1258
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
Will this slow down tests that spin up numerous containers? I just want to double check we won't wait 1 second for each ephemeral container we spin up. |
Test are only slowed down by the 1 second per container, and containers are spun up in parallel. So if you have 1 or 100 containers, the test time only slows down by 1 second
No, ephemeral containers use their own job.Run() method which is outside of the containerLifecycle.
containerLifecycle is only used for long running containers (nodes & sidecars). I had previously tested this with
Only time it hangs is post "Starting container" once. |
I also have a WIP speed up branch which will reduce test time by like 40%. Theoretical max is ~90 - 92% with state cache. Which would make this 1 second start wait the slowest part of ICT in the future |
closes #1238
Summary
This is a huge user experience improvement for ICT & local-ic upon a bad genesis param set (or some other failed startup option).
Before, the network would hang and just state it failed to query
:
failed to start chains: failed to start chain localosmosis-1: All attempts fail:
#1
: post failed: Post "http://0.0.0.0:26659\": dial tcp 0.0.0.0:26659: connect: connection refused...
#30
...Showcase
This chain uses a genesis modification of
{"key": "app_state.gov.params.voting_period", "value": "bad"},
. Both validators show this error in an easy to read format + the docker logs for the stacktrace.