From: Mark Wielaard <mark@klomp.org>
To: buildbot@sourceware.org
Cc: Mark Wielaard <mark@klomp.org>
Subject: [COMMITTED] Set DockerLatentWorker build_wait_timeout back to zero
Date: Wed, 8 Jun 2022 21:54:02 +0200 [thread overview]
Message-ID: <20220608195402.676642-1-mark@klomp.org> (raw)
This was set to 5 minutes when we saw switching containers was leaking
ssh connections. But this issue is fixed. Shutting down and starting a
container is near instantaneous now. So just doing it always is fine.
---
builder/master.cfg | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/builder/master.cfg b/builder/master.cfg
index af4f65f..b4b42ae 100644
--- a/builder/master.cfg
+++ b/builder/master.cfg
@@ -142,7 +142,7 @@ bb1_worker = worker.DockerLatentWorker("bb1",
docker_host="ssh://builder@bb.wildebeest.org:2021",
dockerfile=util.Interpolate('%(prop:container-file)s'),
volumes=["/home/builder/shared:/home/builder/shared"],
- build_wait_timeout=60 * 5,
+ build_wait_timeout=0,
max_builds=1,
properties={'ncpus': 8});
c['workers'].append(bb1_worker)
@@ -153,7 +153,7 @@ bb2_worker = worker.DockerLatentWorker("bb2",
docker_host="ssh://builder@bb.wildebeest.org:2022",
dockerfile=util.Interpolate('%(prop:container-file)s'),
volumes=["/home/builder/shared:/home/builder/shared"],
- build_wait_timeout=60 * 5,
+ build_wait_timeout=0,
max_builds=1,
properties={'ncpus': 8});
c['workers'].append(bb2_worker)
@@ -164,7 +164,7 @@ bb3_worker = worker.DockerLatentWorker("bb3",
docker_host="ssh://builder@bb.wildebeest.org:2023",
dockerfile=util.Interpolate('%(prop:container-file)s'),
volumes=["/home/builder/shared:/home/builder/shared"],
- build_wait_timeout=60 * 5,
+ build_wait_timeout=0,
max_builds=1,
properties={'ncpus': 8});
c['workers'].append(bb3_worker)
--
2.30.2
reply other threads:[~2022-06-08 19:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220608195402.676642-1-mark@klomp.org \
--to=mark@klomp.org \
--cc=buildbot@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).