From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 70002 invoked by alias); 21 Sep 2018 15:31:02 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 69895 invoked by uid 89); 21 Sep 2018 15:30:56 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,SPF_HELO_PASS autolearn=no version=3.3.2 spammy=237A, 7628, 31f4, D0EB X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 21 Sep 2018 15:30:54 +0000 Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.24]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id E30D9C07F9A2; Fri, 21 Sep 2018 15:30:36 +0000 (UTC) Received: from localhost (unused-10-15-17-196.yyz.redhat.com [10.15.17.196]) by smtp.corp.redhat.com (Postfix) with ESMTP id B1A7C308BDA4; Fri, 21 Sep 2018 15:30:36 +0000 (UTC) From: Sergio Durigan Junior To: Rainer Orth Cc: gdb-patches@sourceware.org Subject: Re: [PATCH] Provide Solaris 11 buildbots References: <874lelw9r3.fsf@redhat.com> <877ejguuo0.fsf@redhat.com> Date: Fri, 21 Sep 2018 15:31:00 -0000 In-Reply-To: (Rainer Orth's message of "Fri, 21 Sep 2018 10:50:53 +0200") Message-ID: <87pnx63m1v.fsf@redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes X-SW-Source: 2018-09/txt/msg00752.txt.bz2 On Friday, September 21 2018, Rainer Orth wrote: > Hi Sergio, > >>>> There are two "special" tags: "MAIL" and "TEST". When a builder is >>>> marked as "MAIL", the BuildBot master will send e-mail notifications >>>> about it to gdb-testers/gdb-patches. If it's marked as "TEST", then all >>>> e-mail notifications are supressed. I just mark a builder as "TEST" if >>>> it proves to unstable (i.e., when GDB fails to compile on it because of >>>> some problem with the builder itself). I think it makes sense to mark >>>> your builders as "MAIL", since they're relatively stable, from what you >>>> said. >>> >>> That's the intent: the hosts (global zones in Solaris lingo) are among >>> my main (or only in case of the sparc box) development machines, so I'll >>> keep them up and running for that reason alone ;-) >>> >>> The global zones are running current Solaris 11.5 Beta builds, and thus >>> will be upgraded/rebooted biweekly. The kernel zones which host the >>> build slaves are on Solaris 11.4, with the intent of upgrading to the >>> latest SRU (support repository upgrade; collection of patches tested >>> together) once a month. Apart from those planned downtimes (reboots in >>> the order of minutes), the systems have been rock solid. >> >> Cool. Reboots are fine, as long as (as you said below) the buildslaves >> reconnect automatically. > > just FYI: I've now turned both buildslaves into Solaris SMF services, > and they survived reboots. So I believe we're set on that front. Great! > One question, though: the reboots (both host and kernel zones, which are > VMs effectively) took longer than the current missing_timeout of 5 > minutes. Would it be possible to double that or make it per-buildslave? Sure, I doubled the time to 10 minutes now. Thanks, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/