From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-4.3 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,MAILING_LIST_MULTI,NICE_REPLY_A, RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server2.sourceware.org [IPv6:2620:52:3:1:0:246e:9693:128c]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id DDA321F4B4 for ; Thu, 14 Jan 2021 12:59:45 +0000 (UTC) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id CCA143947427; Thu, 14 Jan 2021 12:59:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CCA143947427 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1610629184; bh=FIPv2k1TAx5s20oUoHQwCcI/nABaU5ijTtwfGKR4u88=; h=Subject:To:References:Date:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=n49Bq6rTkttyERRb7LLE8VYPRFbATUOOKapqMzM5EghtG9jI0llSMWOErQhOBbNeZ PWxp314xnXoNzHaI9urfDwWICpwTMQrUN1yuFWR+nqyM9rJdoRHasgqn6tXKCEOhuj zhiioFLKDAci6epdws99QgpMOXEfU5igeF0modsw= Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by sourceware.org (Postfix) with ESMTP id 77F1E3870891 for ; Thu, 14 Jan 2021 12:59:42 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 77F1E3870891 Received: from mail-qk1-f197.google.com (mail-qk1-f197.google.com [209.85.222.197]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-495-OecytO8yPbCq8FcONgR4lw-1; Thu, 14 Jan 2021 07:59:40 -0500 X-MC-Unique: OecytO8yPbCq8FcONgR4lw-1 Received: by mail-qk1-f197.google.com with SMTP id n13so4565370qkn.2 for ; Thu, 14 Jan 2021 04:59:39 -0800 (PST) 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:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=FIPv2k1TAx5s20oUoHQwCcI/nABaU5ijTtwfGKR4u88=; b=i7FDHDOsc1E7FeXtIhJqoY29s5WNqDKUOG+bC8WNlh882EJnYj6wAJGeamnwNip43I vty9f+zGWN/8bF2zxedau2br/SIhOk85tWnjBJo2S3jfVumMSXEKstUAUiDcAPKpYX8R V4zkjwWum/+5+XKao4hyLE7/6Me1Xk+OjQcikM03CLFaNjvBXkt8bVcqzOUhce9jrBb0 QF8rbVbr7GbaBuFxRi/CCD0ACIOtVIih5sBEPVyUNDQMWHFcECSeZwCMTMAxQ+3CEXxn MWT09F8QSjKS6ICs56CeGsF/9wi3Hp0FK4LkgCZRcQjZGETc9gE782iPmYcMF76G35vr hOIw== X-Gm-Message-State: AOAM533z/o0zqJFOw7V8ta79yPAnswDetCP4FLZ+drYnSF4kbGhgsVN8 RGmWycUIQpkT+cx17z1K8kBoSCL19TfH9QwHFf4q4n6lpDb/zyu5HuY0JVAt6nomo/wzvB27HkU 2K+/0LpcyVPiMGorypyRFtG7z/JoDVG1W6RDb62zBBh/DjH5N1s7Hdu3TKYNwVjWyhDqiJA== X-Received: by 2002:ac8:7288:: with SMTP id v8mr6950177qto.358.1610629179160; Thu, 14 Jan 2021 04:59:39 -0800 (PST) X-Google-Smtp-Source: ABdhPJwiNplQHwBqpWa6k0YMnqgjlVmK+N7+DHaDU4pSFj/g67uZ6pGRvRU1ciMwanSdDgNR2QiZcQ== X-Received: by 2002:ac8:7288:: with SMTP id v8mr6950167qto.358.1610629178906; Thu, 14 Jan 2021 04:59:38 -0800 (PST) Received: from [192.168.1.16] (198-84-214-74.cpe.teksavvy.com. [198.84.214.74]) by smtp.gmail.com with ESMTPSA id 17sm2970678qtu.23.2021.01.14.04.59.37 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 14 Jan 2021 04:59:38 -0800 (PST) Subject: Re: New math test failures on Fedora/33 To: Tulio Magno Quites Machado Filho , Adhemerval Zanella , Paul Zimmermann References: <4b0af99b-8353-7201-ec79-aae1b8eada70@linaro.org> <44e1b250-8946-4d8a-614e-f2e20c3f1f33@linaro.org> <6eead3d5-56c7-1332-a978-8663bd296522@linaro.org> <87eeiq0xz9.fsf@linux.ibm.com> Organization: Red Hat Message-ID: <8338bca0-9b10-6ad7-3b3a-aa44c0c14970@redhat.com> Date: Thu, 14 Jan 2021 07:59:37 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: <87eeiq0xz9.fsf@linux.ibm.com> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Carlos O'Donell via Libc-alpha Reply-To: Carlos O'Donell Cc: libc-alpha@sourceware.org Errors-To: libc-alpha-bounces@sourceware.org Sender: "Libc-alpha" On 1/12/21 2:14 PM, Tulio Magno Quites Machado Filho via Libc-alpha wrote: > Adhemerval Zanella via Libc-alpha writes: > >> Currently we only have aarch64/armhf that provide any meaningful information. >> Maybe Tulio can give us a better idea of the current status of the powerpc >> ones. > > I lost access to the 3 servers I had a while ago. > It's been difficult to find 32-bit powerpc servers after that. > > During the pandemic, I also lost access to the ansible playbooks I used to > create the controller and the ppc workers. > I've just recovered them, but I'm able to add just ppc64le and ppc64 servers. > Not optimal, but better than what we have now. > > During the last 2 Cauldrons, we've also discussed improvements that are > necessary to make this BuildBot useful. > They're all still pending. > > In case there is anyone willing to help, the repository is available at: > https://sourceware.org/git/?p=glibc-buildbot.git;a=summary DJ and I have been discussing this as a project for 2021. More importantly I think we need to shift this to CI/CD and integrate it into patchwork. I want to see fails reported per-patch. Then glue the CI/CD into that using new infrastructure (runners + builbot try bot). I continue to feel that we need confidence to integrate new patches and that confidence doesn't come from build bots, but comes from CI/CD during review for reviewers assistance. I still want to get to 100 patches reviewed in a day and I need automated help to get there. I want to see a process where we get email back immediately into a patch thread (consider each patch thread like a PR) and it includes a try bot result. Then (and this idea I attribute to Konrad Kleine from the Red Hat Platform Tools team) I want the reviewer to interact with the try bot by email with special commands e.g. @build build-many-glibcs, to kick off a single bmg run with the patch in the thread that is tied to the patchwork object. This way the reviewer is in charge of exactly which background additional task is required to be carried out by CI/CD and report back the results in the thread for public review. -- Cheers, Carlos.