From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x42c.google.com (mail-wr1-x42c.google.com [IPv6:2a00:1450:4864:20::42c]) by sourceware.org (Postfix) with ESMTPS id 04DDA385702D for ; Fri, 6 Aug 2021 15:55:25 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 04DDA385702D Received: by mail-wr1-x42c.google.com with SMTP id n12so1626333wrr.2 for ; Fri, 06 Aug 2021 08:55:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=XXDZnZLgbtZs0MAtfX/y/XrDC/Lie8xkOyzNtpVnx9o=; b=FwSOu+fOC0/PZKXFcNN7KmSmVVLOjL6RoaJKsHdFLDvzBDl0p8lUeTTyDpslWPRhns THVGGXhwvDKQBidp0irQle6MrQtUTOELpxgfSIGZ9dHbBwks472ngNkYQjpVEKZrYPQd uqv4skSnAStMdEgvjU89FgilQtzKCVi7TKCZVK7qK4rREn6/e2B+9fKIPSRzy1lPq01h fmKYH8RVcWXRlny48VMzgQXF5Y5jp4wr6qpASMBPeHl3Snpxoe7BsAaR8BTQAAyVh6Eg 9449/Ut5jY9q4UCriqipZ70edRr78MmBbMUlfU/trDpcV6/jDf2bxHylJ4OMlqd41/bp RXMQ== X-Gm-Message-State: AOAM530qmwUG/oze6XsUW53MoHNptkZ7sKY3mjMDPOj4orj7frVJ/Y+1 nGiIuM6LswrkFlkpBFia/Q== X-Google-Smtp-Source: ABdhPJy9h9REiOypTOcBhg7DRbcDdT20EkVJXh+gr6VMmMMHxDVdUzChS4olH3B9s/JtZ54FyJPv5g== X-Received: by 2002:adf:d091:: with SMTP id y17mr11723530wrh.311.1628265324061; Fri, 06 Aug 2021 08:55:24 -0700 (PDT) Received: from localhost (static-176-191-252-212.ftth.abo.bbox.fr. [176.191.252.212]) by smtp.gmail.com with ESMTPSA id z3sm12583863wmf.6.2021.08.06.08.55.23 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 06 Aug 2021 08:55:23 -0700 (PDT) Date: Fri, 6 Aug 2021 17:55:09 +0200 From: "cohenarthur.dev" To: Philip Herron Cc: Mark Wielaard , buildbot@builder.wildebeest.org, gcc-rust@gcc.gnu.org Subject: Re: Buildbot failure in Wildebeest Builder on whole buildset Message-ID: <20210806155509.f4advlfv4zvdrr6k@oneshade> References: <20210804151500.BECFC81A9C8@builder.wildebeest.org> <8b46b6ad-750d-96bf-6814-b0226aa4eaf6@embecosm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8b46b6ad-750d-96bf-6814-b0226aa4eaf6@embecosm.com> X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, 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: gcc-rust@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: gcc-rust mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Aug 2021 15:55:26 -0000 On 21/08/06 03:31PM, Philip Herron wrote: > On 04/08/2021 21:25, Mark Wielaard wrote: > > Hi, > > > > On Wed, Aug 04, 2021 at 03:15:00PM +0000, buildbot@builder.wildebeest.org wrote: > >> The Buildbot has detected a new failure on builder gccrust-debian-arm64 while building gccrust. > >> Full details are available at: > >> https://builder.wildebeest.org/buildbot/#builders/58/builds/270 > >> > >> Buildbot URL: https://builder.wildebeest.org/buildbot/ > >> > >> Worker for this Build: debian-arm64 > >> > >> Build Reason: > >> Blamelist: CohenArthur > >> > >> BUILD FAILED: failed compile (failure) > > This commit (and the following 3) were really bad. They didn't build. > > Apparently bors doesn't check commit individually, but the buildbot > > does build every commit separately. Really sorry about this. > > The tree is buildable again, but I think it would be good to not have > > any commits that break the build. > > > > Periodically broken trees make it also hard to bisect issues. > > > > Is it possible to make bors check all commits in a series? Or can we > > somehow connect the buildbot workers to the bors checks? I think bors is mostly focused on having the latest commit on the main branch always build, but I might be wrong on this. I think it should be possible to integrate buildbot to the CI on github directly, side to side with bors. > > > > Thanks, > > > > Mark > > > Hi Mark, > > I think the build-bot checks for every commit is a really nice feature > here. I think you should keep the build-bots as are. I really like to > make sure each of my commits are build-able and pass tests. It keeps me > honest to avoid regressions as best I can. > > What do you think? > > Thanks > > --Phil > I'm really sorry about not having all the commits build. I tried to keep them as atomic as possible and clearly didn't check all of them separately. This could have been a single commit and would have avoided this, but since each change was big I decided to split them up. I was not aware that buildbot checks every commit separately. I think this is a good feature, and I'll keep it in mind. Won't happen again! Sorry again, -- Arthur