From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 65616 invoked by alias); 4 Sep 2018 19:43:54 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 65607 invoked by uid 89); 4 Sep 2018 19:43:54 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-6.9 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_2,KAM_LAZY_DOMAIN_SECURITY autolearn=ham version=3.3.2 spammy=secured, amounts, shapes, Hx-languages-length:1287 X-HELO: smtp.CeBiTec.Uni-Bielefeld.DE Received: from smtp.CeBiTec.Uni-Bielefeld.DE (HELO smtp.CeBiTec.Uni-Bielefeld.DE) (129.70.160.84) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 04 Sep 2018 19:43:52 +0000 Received: from localhost (localhost.CeBiTec.Uni-Bielefeld.DE [127.0.0.1]) by smtp.CeBiTec.Uni-Bielefeld.DE (Postfix) with ESMTP id 19FD76E; Tue, 4 Sep 2018 21:43:50 +0200 (CEST) Received: from smtp.CeBiTec.Uni-Bielefeld.DE ([127.0.0.1]) by localhost (malfoy.CeBiTec.Uni-Bielefeld.DE [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 3p41r1SCAiRH; Tue, 4 Sep 2018 21:43:48 +0200 (CEST) Received: from manam.CeBiTec.Uni-Bielefeld.DE (p4FDDBA32.dip0.t-ipconnect.de [79.221.186.50]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.CeBiTec.Uni-Bielefeld.DE (Postfix) with ESMTPSA id 52A306D; Tue, 4 Sep 2018 21:43:48 +0200 (CEST) From: Rainer Orth To: gdb@sourceware.org Cc: Sergio Durigan Junior Subject: Solaris 11 buildbots Date: Tue, 04 Sep 2018 19:43:00 -0000 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (usg-unix-v) MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes X-SW-Source: 2018-09/txt/msg00004.txt.bz2 Prompted by a couple of gdb build failures in the past and Tom's message https://sourceware.org/ml/gdb-patches/2018-09/msg00027.html I intend to set up gdb buildbots running on Solaris 11.4. The current plan is to have two buildslaves, one running on Solaris 11.4/SPARC, the other on Solaris 11.4/x86. I'll certainly run them to build sparcv9-sun-solaris2.11 and amd64-pc-solaris2.11 configurations testing 64-bit debugging; if it works out reasonably well, I mean to add 32-bit testing as well. I don't currently plan to test i386-pc-solaris2.11 or sparc-sun-solaris2.11 (i.e. a 32-bit gdb) or Solaris 10: the latter is close to it's end of life and I expect to remove gcc support for that target in about a year or two. Besides, I don't have hosts sufficiently secured to run buildbots there. As mentioned in the thread above, the target isn't in the best of shapes right now, with close to 2000 failures and 200+ racy tests, mostly in gdb.threads. The latter may have to be filtered out to avoid large amounts of useless noise. However, the buildbot will at least be able to detect build failures early on. Rainer -- ----------------------------------------------------------------------------- Rainer Orth, Center for Biotechnology, Bielefeld University