You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the polling await strategy on a slower machine with container images lacking the ss command, the strategy falls back to using wait-for-it script, but doesn't specify a timeout. On slower machines autostarting multiple containers in parallel, the default timeout of 15 seconds isn't long enough.
Expected Behaviour
The polling await strategy should use the await parameters to specify a timeout to the wait-for-it script so that await times can be adjusted
Current Behaviour
Sometimes the containers start successfully, but on slower machines with multiple containers autostarting, container startups fail.
The text was updated successfully, but these errors were encountered:
Issue Overview
When using the polling await strategy on a slower machine with container images lacking the ss command, the strategy falls back to using wait-for-it script, but doesn't specify a timeout. On slower machines autostarting multiple containers in parallel, the default timeout of 15 seconds isn't long enough.
Expected Behaviour
The polling await strategy should use the await parameters to specify a timeout to the wait-for-it script so that await times can be adjusted
Current Behaviour
Sometimes the containers start successfully, but on slower machines with multiple containers autostarting, container startups fail.
The text was updated successfully, but these errors were encountered: