[PATCH] SETUP: buildbot-stop.sh should not use --clean

[PATCH] SETUP: buildbot-stop.sh should not use --clean

[Mark Wielaard]

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