public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: buildbot@sourceware.org
Cc: Mark Wielaard <mark@klomp.org>
Subject: [PATCH] SETUP: buildbot-stop.sh should not use --clean
Date: Sat,  4 Jun 2022 01:19:15 +0200	[thread overview]
Message-ID: <20220603231915.631645-1-mark@klomp.org> (raw)

Using --clean means the buildbot will not stop till all workers
are done. Which can take hours. Just stop, which interrupts the
builds. They will be retried when the master starts.
---
 SETUP | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/SETUP b/SETUP
index ed82db3..c9f7005 100644
--- a/SETUP
+++ b/SETUP
@@ -62,7 +62,7 @@ buildbot start --start_timeout=120 /sourceware/builder/buildbot/builder
 - buildbot-stop.sh
 #!/bin/bash
 source /sourceware/builder/buildbot-env/bin/activate
-buildbot stop --clean /sourceware/builder/buildbot/builder
+buildbot stop /sourceware/builder/buildbot/builder
 - buildbot-reload.sh
 #!/bin/bash
 source /sourceware/builder/buildbot-env/bin/activate
@@ -145,4 +145,4 @@ key pair under /sourceware/builder/.ssh (ssh-keygen) with the public
 part going into the docker_host builder user .ssh/authorized_keys. So
 the DockerLatentWorker can run docker system dial-stdio on the
 docker_host. Since the buildbot will use the ~/.ssh config make sure
-that the hosts are in .known_hosts (by logging in by hand once).
\ No newline at end of file
+that the hosts are in .known_hosts (by logging in by hand once).
-- 
2.30.2


                 reply	other threads:[~2022-06-03 23:19 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=20220603231915.631645-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).