From: Mark Wielaard <mark@klomp.org>
To: buildbot@sourceware.org
Cc: Carl Love <cel@us.ibm.com>, Mark Wielaard <mark@klomp.org>
Subject: [COMMITTED] Remove power8 worker and builders
Date: Fri, 3 Feb 2023 17:29:13 +0100 [thread overview]
Message-ID: <20230203162912.63247-1-mark@klomp.org> (raw)
The power8 builder won't come back soon. Remove the worker and the
gdb and valgrind builders for real now.
---
builder/master.cfg | 24 ------------------------
1 file changed, 24 deletions(-)
diff --git a/builder/master.cfg b/builder/master.cfg
index 46e7cf9..127ba79 100644
--- a/builder/master.cfg
+++ b/builder/master.cfg
@@ -239,14 +239,6 @@ vm_workers = ['bb1-1', 'bb1-2', 'bb2-1', 'bb2-2', 'bb3',
'bbo1-1', 'bbo1-2']
big_vm_workers = ['bb3', 'bbo1-2']
-ibm_power8_worker = worker.Worker("ibm_power8",
- getpw("ibm_power8"),
- max_builds=2,
- properties={'ncpus': 8, 'maxcpus': 16},
- notify_on_missing=['will_schmidt@vnet.ibm.com',
- 'cel@us.ibm.com']);
-c['workers'].append(ibm_power8_worker)
-
ibm_power9_worker = worker.Worker("ibm_power9",
getpw("ibm_power9"),
max_builds=2,
@@ -618,7 +610,6 @@ valgrind_scheduler = schedulers.SingleBranchScheduler(
"valgrind-debian-testing-x86_64",
"valgrind-debian-armhf",
"valgrind-debian-i386",
-# "valgrind-ibm-power8",
"valgrind-ibm-power9",
"valgrind-ibm-power10",
"valgrind-fedora-ppc64le",
@@ -806,7 +797,6 @@ gdb_scheduler = schedulers.SingleBranchScheduler(
"gdb-armhf-ubuntu20_04",
"gdb-armhf-ubuntu22_04",
"gdb-debian-i386",
-# "gdb-ibm-power8",
"gdb-ibm-power9",
"gdb-ibm-power10",
"gdb-fedora-s390x",
@@ -2911,13 +2901,6 @@ gdb_try_debian_testing_x86_64_builder = util.BuilderConfig(
factory=gdb_factory)
c['builders'].append(gdb_try_debian_testing_x86_64_builder)
-# gdb_ibm_power8_builder = util.BuilderConfig(
-# name="gdb-ibm-power8",
-# workernames=["ibm_power8"],
-# tags=["gdb", "ibm", "power8"],
-# factory=gdb_factory)
-# c['builders'].append(gdb_ibm_power8_builder)
-
gdb_ibm_power9_builder = util.BuilderConfig(
name="gdb-ibm-power9",
workernames=["ibm_power9"],
@@ -3897,13 +3880,6 @@ valgrind_fedora_ppc64le_builder = util.BuilderConfig(
factory=valgrind_make_check_aux_factory)
c['builders'].append(valgrind_fedora_ppc64le_builder)
-# valgrind_ibm_power8_builder = util.BuilderConfig(
-# name="valgrind-ibm-power8",
-# workernames=["ibm_power8"],
-# tags=["valgrind", "ibm", "power8"],
-# factory=valgrind_make_check_aux_factory)
-# c['builders'].append(valgrind_ibm_power8_builder)
-
valgrind_ibm_power9_builder = util.BuilderConfig(
name="valgrind-ibm-power9",
workernames=["ibm_power9"],
--
2.31.1
next reply other threads:[~2023-02-03 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 16:29 Mark Wielaard [this message]
2023-02-03 18:09 ` Carl Love
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=20230203162912.63247-1-mark@klomp.org \
--to=mark@klomp.org \
--cc=buildbot@sourceware.org \
--cc=cel@us.ibm.com \
/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).