From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pj1-x1029.google.com (mail-pj1-x1029.google.com [IPv6:2607:f8b0:4864:20::1029]) by sourceware.org (Postfix) with ESMTPS id A030E385AC19 for ; Tue, 20 Jul 2021 15:21:22 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A030E385AC19 Received: by mail-pj1-x1029.google.com with SMTP id o3-20020a17090a6783b0290173ce472b8aso2122452pjj.2 for ; Tue, 20 Jul 2021 08:21:22 -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:from:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=JSKKKCPBbDIlJKY6GUXN6bbzhI6ktu4Kx2bZxOaM3SI=; b=GMKB6bFs/rVw1RamRjTienPjj05wy4ChC85pr/qlRPo+GFwPsszEtL9iKJtCGdp9K4 YoMS7n+kD50LucurAOLQDet9UkOVjuIt8tKI3Hri4IOcmHbBvEiETA/I6ckxCTwAmIW+ IH7S+ihWIt/TbGkvjO6K/stg1i7JaESDib5Gfmv45NdGyeS2X7P4+zcQpXKJA4e1nrO/ ANeGfVTF9qS+2+NUhSwM9dW5p4yTziZHGuqAT8f6MrIqHvyHQiWNmoPjZCU3hwmwZPm2 0FNN24BNldPZA5Glu/9Ghtn50TW0SufYDuReDavyV4WUaA+GL6rGWW8Mw8gedz+bpJbh +MaA== X-Gm-Message-State: AOAM5318wfq4CEOwIpCC1b4JhkhlLtgAiRI8rCdUqLFqQXy6owcKVX8m +2JUn6fqmXH6wXdMLlVu4As7Hg== X-Google-Smtp-Source: ABdhPJxdJNgmZr8VftwPzf9F7CC0Qzp2yTs5heyAPPRXyeuE3EagZkEzGQuwl0XLdMXkXcOmU1lELw== X-Received: by 2002:a17:90a:6686:: with SMTP id m6mr29941405pjj.109.1626794481737; Tue, 20 Jul 2021 08:21:21 -0700 (PDT) Received: from ?IPv6:2804:7f0:4841:2b39:357f:5f9a:1dce:6fcc? ([2804:7f0:4841:2b39:357f:5f9a:1dce:6fcc]) by smtp.gmail.com with ESMTPSA id a20sm23370907pfv.101.2021.07.20.08.21.19 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 20 Jul 2021 08:21:20 -0700 (PDT) Subject: Re: [RFC] Proposal for hosting GDB CI builds From: Luis Machado To: "gdb@sourceware.org" References: <7bfae273-3887-30c8-dc65-94d5b177db56@linaro.org> Message-ID: <519a40f4-5999-f338-227e-464ed7ce23be@linaro.org> Date: Tue, 20 Jul 2021 12:21:17 -0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: <7bfae273-3887-30c8-dc65-94d5b177db56@linaro.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.7 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.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) 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: Tue, 20 Jul 2021 15:21:24 -0000 Any other feedback on this? On 6/30/21 1:46 PM, Luis Machado wrote: > Hi, > > This proposal comes as an attempt to revive the GDB CI builds, given the > previous one (buildbot) is no longer being maintained by Sergio (thanks > a lot for keeping it working for all these years by the way). > > CI GDB builds are a great help for spotting regressions without having > to do the tedious and time-consuming work of running the GDB testsuite > for each git revision, for each architecture and reading through > hundreds of lines of summaries. If a regression is spotted, then one > needs to bisect to find the culprit. This isn't great, specially for > architectures without great availability of desktop hardware. > > Ideally, for each commit, we'd run full builds to validate the state of > the tree, but we're not quite there yet. So meanwhile, having some level > of automation to get the builds done without manual intervention sounds > like a reasonable step forward. > > From previous IRC conversations, it seems to be a consensus that > availability of processing power is not a problem. It is reasonably easy > to find hardware to do some builds. The most difficult resource to find > is manpower to setup the CI infrastructure and keep it running. > > With the above said, I've discussed this internally at Linaro and we can > spare some manpower to setup and maintain an isolated Linaro-hosted > Jenkins instance for GDB CI builds. > > Linaro can take care of providing builders and build jobs for ARM. Other > architectures would be handled by their respective contributors. Those > contributors can write jobs and plug builders as needed. > > Setting up new jobs doesn't require the use of the web interface. It can > be done with yaml files in a git repo. It is reasonably simple. > > You can see an example of the Linaro CI here: https://ci.linaro.org/ > > Also, a GDB job for aarch64: https://ci.linaro.org/job/tcwg-gdb/ > > And also the summaries for GDB testsuite runs: > https://ci.linaro.org/job/tcwg-compare-results/13968/artifact/artifacts/logs/0-report.html > > > Of course, this effort only makes sense if the community is OK with > using Jenkins as the CI mechanism and if it actually sees value in > having a system like this in place. > > Thoughts? Questions?