-
Notifications
You must be signed in to change notification settings - Fork 810
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
Allow 30m more to acquire consul lock #2922
Conversation
We seem to be having more frequent consul lock timeouts on CI. Best guess, this is a bandwidth issue of all PRs using the same e2e clusters and a higher number of PRs, plus probably some organic growth in e2e length. This PR is a stop-gap: * Bumps the consul lock timeout from 1h to 1.5h - basically "wait our turn" for longer. * Bumps the whole build timeout from 2h to 2.5h. I assume the whole build has a generous timeout to allow for the image build, etc, prior to e2es, so kept the increase here 1:1. * Bumps the queue TTL from (default) 1h to 6h. This is a generous bump to allow builds to hang out longer in the queue.
aa412e3
to
57125df
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gongmax, markmandel, zmerlynn The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Build Succeeded 👏 Build Id: 245386bc-e428-4c30-82a8-b4386f1ebe69 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
Build Succeeded 👏 Build Id: 34c4f7cb-32ed-4354-aa59-38657a1a4547 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
We seem to be having more frequent consul lock timeouts on CI. Best guess, this is a bandwidth issue of all PRs using the same e2e clusters and a higher number of PRs, plus probably some organic growth in e2e length. This PR is a stop-gap: * Bumps the consul lock timeout from 1h to 1.5h - basically "wait our turn" for longer. * Bumps the whole build timeout from 2h to 2.5h. I assume the whole build has a generous timeout to allow for the image build, etc, prior to e2es, so kept the increase here 1:1. * Bumps the queue TTL from (default) 1h to 6h. This is a generous bump to allow builds to hang out longer in the queue.
We seem to be having more frequent consul lock timeouts on CI. Best guess, this is a bandwidth issue of all PRs using the same e2e clusters and a higher number of PRs, plus probably some organic growth in e2e length. This PR is a stop-gap:
Bumps the consul lock timeout from 1h to 1.5h - basically "wait our turn" for longer.
Bumps the whole build timeout from 2h to 2.5h. I assume the whole build has a generous timeout to allow for the image build, etc, prior to e2es, so kept the increase here 1:1.