From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk1-x743.google.com (mail-qk1-x743.google.com [IPv6:2607:f8b0:4864:20::743]) by sourceware.org (Postfix) with ESMTPS id D7EEA3851C09 for ; Thu, 27 Aug 2020 19:31:44 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org D7EEA3851C09 Received: by mail-qk1-x743.google.com with SMTP id d139so7107735qke.11 for ; Thu, 27 Aug 2020 12:31:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=9GZlSAD7eKld5yyzJBifnNyRf9EfsakE4jwQgY88E4E=; b=L2paELqvjZm0Q+yUHku/Lfl0uSkaSguvwST73yUG/W+F5iQ4I8zdHJaH/K2D2u8SBm 4WagXcLVV7lIKRsvsL8fBBiTiPDF8J0hwkdJZr1DLpc99dFFmUSFv7zlqFqCFs6vlhWe fiqYSgOKQbZttn42KRkEX8PpnGWS1FcWV5OCqGlRmKd34eUeXi/pH42zjCclmqtxKSbY UhTs4rIeGP/TRcr6h9N0mr0eerGPIVgAPINrvmNE+Q2LbteZc+s2RxxngxpJSg31vH1u x1ezj4wC6LBd9tyJhr7v37032UluwoH3CucKNtqvKfnkr159/RBaEjC3OXm12UirDnyD zGzg== X-Gm-Message-State: AOAM532hDiDxZzZhTDAjV43Iy2IFp9uUm2DMhf93VChnmr39ryxJXqB0 ZsKA4EkE5vkswgXezhl2A37YQlFmIh8ElA== X-Google-Smtp-Source: ABdhPJxD2qQI6ia5Jsl9UByQZH9Lrs4fUPyudTuDMSq2vgnmBsSQo9cy+/S4Y24+h1CkyYCnQp5nqA== X-Received: by 2002:a37:e54:: with SMTP id 81mr2778241qko.433.1598556704265; Thu, 27 Aug 2020 12:31:44 -0700 (PDT) Received: from ?IPv6:2804:7f0:8283:a3ee:1908:8b5e:50f8:c881? ([2804:7f0:8283:a3ee:1908:8b5e:50f8:c881]) by smtp.gmail.com with ESMTPSA id l13sm2471410qth.77.2020.08.27.12.31.42 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 27 Aug 2020 12:31:43 -0700 (PDT) Subject: Re: Request for help with the Buildbot [was: Re: Status of GDB buildbots] To: Sergio Durigan Junior , Rainer Orth Cc: gdb@sourceware.org References: <87y2m2rdcz.fsf_-_@paluero> From: Luis Machado Message-ID: <83ebccde-b99b-408b-2bb3-23ab3a7613cc@linaro.org> Date: Thu, 27 Aug 2020 16:31:38 -0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <87y2m2rdcz.fsf_-_@paluero> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2020 19:31:46 -0000 Hi, On 8/25/20 11:47 AM, Sergio Durigan Junior via Gdb wrote: > On Tuesday, August 25 2020, Rainer Orth wrote: > >> Rainer Orth writes: >> >>> It seems regular scheduled runs of the GDB buildbots stopped about a >>> month ago. AFAICS all runs since (which are only a few) are for the >>> racy and try_ssh schedulers only, nothing for master. >>> >>> I've initially observed this on the Solaris buildbots, but the others >>> seem to be equally affected. For the Solaris bots, there are regular >>> keepalive messages in twistd.log, but nothing else. >> >> I've never received a reply on this one and now found that Sergio has >> left RedHat. Given that the buildbots have been mostly idle for a month >> or two: is there anyone to look into this? > > Hi Rainer, > > Sorry about the disappearance; indeed I'm not at RH anymore, and > although I'm trying to follow gdb-patches, I'm not subscribed to gdb@ > anymore, which means I completely missed your message :-/. Is this something RH will pick up or is it a best-effort personal contribution of yours? > > Anyway, I was not aware of this problem with our buildbot. I thought > I'd be able to maintain it while doing my other job, but as it turns out > it's just too much. So I'm hijacking this thread and turning it into a > request for help with our Buildbot. > > I don't know how much value the Buildbot still brings to the community. > I know a few people were relying heavily on it because of the try build > feature, but I'm not sure if they still use it. That's something for > the community to discuss, I think. I can state it brings pretty good value to arm-linux/aarch64-linux testing. I've been noticing an influx of regressions from pushed patches that have not been properly exercised on aarch64-linux, which is unfortunate. Ideally we'd have a CI loop integrated with some patch reviewing system (gerrit was great in this regard), but the buildbot is already a great improvement over not having anything.