public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
Cc: Mark Wielaard <>
Subject: [PATCH] Upgrade to buildbot 3.6.1
Date: Sun,  9 Oct 2022 01:12:56 +0200	[thread overview]
Message-ID: <> (raw)

This includes our patch for:
- Fixed issue with DockerLatentWorker accumulating connections with
  the docker server (issue #6538).

It will hopefully also fix our git upgrade failure issue:
- Fixed “retry fetch” and “clobber on failure” git checkout options.

Include upgrade instructions in README.
 README                | 12 ++++++++++++
 buildbot.requirements | 12 ++++++------
 2 files changed, 18 insertions(+), 6 deletions(-)

diff --git a/README b/README
index 93ab54e..b909026 100644
--- a/README
+++ b/README
@@ -229,6 +229,18 @@ If this seems to not work check whether there are still git
 change-sources being checked and wait till they have done their
+= Upgrading buildbot
+Try this locally first.
+- python3 -m pip install --upgrade `cat buildbot.packages`
+- python3 -m pip freeze > buildbot.requirements
+Try the new setup first as under "Local hacking".
+After check in someone with buildbot shell access will have to
+actually stop, upgrade and restart the buildbot on sourceware.
 = Reconfig buildbot
 When making any changes to master.cfg. Please test everything first in
diff --git a/buildbot.requirements b/buildbot.requirements
index f62ee80..2e294e6 100644
--- a/buildbot.requirements
+++ b/buildbot.requirements
@@ -3,11 +3,11 @@ attrs==21.4.0
@@ -32,7 +32,7 @@ klein==21.8.0

             reply	other threads:[~2022-10-08 23:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-08 23:12 Mark Wielaard [this message]
2022-10-09 12:53 ` Mark Wielaard

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).