From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 63720 invoked by alias); 19 Sep 2018 19:46:54 -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 63635 invoked by uid 89); 19 Sep 2018 19:46:43 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=patch!, proves 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; Wed, 19 Sep 2018 19:46:41 +0000 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 9C844A8F2; Wed, 19 Sep 2018 19:46:40 +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 71197176DC; Wed, 19 Sep 2018 19:46:40 +0000 (UTC) From: Sergio Durigan Junior To: Rainer Orth Cc: gdb-patches@sourceware.org Subject: Re: [PATCH] Provide Solaris 11 buildbots References: Date: Wed, 19 Sep 2018 19:46:00 -0000 In-Reply-To: (Rainer Orth's message of "Wed, 19 Sep 2018 13:23:05 +0200") Message-ID: <874lelw9r3.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/msg00711.txt.bz2 On Wednesday, September 19 2018, Rainer Orth wrote: > If the proposed Solaris 11 buildbots > > https://sourceware.org/ml/gdb/2018-09/msg00004.html Thanks for the offer, and for the patch! IMO, "the more the merrier". So yeah, Solaris 11 buildslaves are absolutely welcome. > are considered worthwhile, here's a patch to introduce them. It's > completely untested of course (I cannot even check syntactic validity), > and there are a couple of caveats: > > * While a regular gdb build succeeds, a -g -D_GLIBCXX_DEBUG build as > used by the buildbot fails as reported in PR build/23676. This can be > avoided either by performing a -g -O build or with > --disable-unit-tests from Sergio's proposed patch. Oh, cool, I saw your comment regarding my patch on the bug. I'm happy it helps to solve other problems. > * The buildslaves are configured to be compile-only at the moment: at > -j4, a build takes ca. 15 minutes, while make check takes 1h 15 due to > many timeouts (mostly in gdb.threads). Until those are resolved, it's > probably useless to run the tests. Right. Until I implement a way to enable only a subset of tests from our testsuite, I agree that it's not a good idea to have builds taking that long to finish. > * I couldn't find proper documentation for at least two fields: > > ** arch in config.json (slaves), seems to be unused AFAICT > > ** tags in config.json (builders) Sorry about that. The "arch" field is indeed unused. The initial plan was to use it to offer some filtering capabilities in the web interface, but that's been replaced by "tags". The "tags" filter is just a collection of tags that are used to categorize the builders. If you go to , at the top of the page you'll see a "Tags:" header, with a bunch of tags. You can use them to selectively display just the builders associated with a certain tag. For example, if you want to list the x86_64 builders, you'd go to . 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. I'll have to contact you in private in order to give the password necessary for connection to the BuildBot master. I'll also apply your patch now and enable the builders, so all it's left for you is to start them on your side. Thank you very much again for your contribution! -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/