- Notifications
You must be signed in to change notification settings - Fork673
chore(ci): increase timeout for docker container to come online#2089
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
f135c82 tod886f1fCompareThanks@JohnVillalovos! What I've also been thinking is that sometimes the GitLab container completely fails to start up properly in underpowered CI VMs (I have a similar test setup on GitLab CI using If that still happens with 5 minutes, we might need to investigate further slimming down the services started in the Omnibus config. GitLab is quite a beast now with all the batteries-included stuff 🤔 |
Uh oh!
There was an error while loading.Please reload this page.
7a8bba8 to4d74e30CompareHave been seeing timeout issues more and more. Increase timeout from200 seconds to 300 seconds (5 minutes).
4d74e30 tobda020bComparecodecov-commenter commentedJun 24, 2022
Codecov Report
@@ Coverage Diff @@## main #2089 +/- ##======================================= Coverage 94.69% 94.69% ======================================= Files 78 78 Lines 5050 5056 +6 =======================================+ Hits 4782 4788 +6 Misses 268 268
Flags with carried forward coverage won't be shown.Click here to find out more.
|
Uh oh!
There was an error while loading.Please reload this page.
Have been seeing timeout issues more and more. Increase timeout from
200 seconds to 300 seconds (5 minutes).