This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [glibc-buildbot] Add 'glibc-s390x-linux': 'marist-fedora-s390x' to builder_map.


On Mon, 2016-10-03 at 16:31 -0700, Roland McGrath wrote:
> Merged and restarted.  It looks like the slave is connected.
> So the next commit to libc should trigger a build there.

It did trigger, but then immediately died:
http://130.211.48.148:8080/builders/glibc-s390x-linux/builds/0/steps/annotate/logs/stdio
ERROR - unset/invalid builder name
builder name: glibc-s390x-linux

I believe that is because I forgot to add the new builder to the
BOT_ASSIGNMENT. The attached patch (also on mjw/s390x branch) does that.

Cheers,

Mark
From e9fadb8090adbab2976f0ef3732155665f176f2e Mon Sep 17 00:00:00 2001
From: Mark Wielaard <mjw@redhat.com>
Date: Tue, 4 Oct 2016 16:11:44 +0200
Subject: [PATCH] scripts/slave/buildbot_selector.py (BOT_ASSIGNMENT): Add
 glibc-s390x-linux.

---
 scripts/slave/buildbot_selector.py | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/scripts/slave/buildbot_selector.py b/scripts/slave/buildbot_selector.py
index 1bb72d0..12bfbb3 100755
--- a/scripts/slave/buildbot_selector.py
+++ b/scripts/slave/buildbot_selector.py
@@ -20,7 +20,8 @@ BOT_ASSIGNMENT = {
     'glibc-power8-linux': bash('glibc-native.sh', [
         '--with-cpu=power8',
         '--enable-lock-elision',
-    ])
+    ]),
+    'glibc-s390x-linux': bash('glibc-native.sh'),
 }
 
 BOT_ADDITIONAL_ENV = {
-- 
1.8.3.1


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]