From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTP id 243EF385481D for ; Thu, 15 Jul 2021 12:24:44 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 243EF385481D 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-48-n4R8JMxzMfmFrgK5EjKO4w-1; Thu, 15 Jul 2021 08:24:42 -0400 X-MC-Unique: n4R8JMxzMfmFrgK5EjKO4w-1 Received: by mail-qk1-f197.google.com with SMTP id h12-20020a05620a400cb02903b8e915ccceso285505qko.18 for ; Thu, 15 Jul 2021 05:24:42 -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:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=sT1drTAGvuywZ6bgneVfexuSQEnzko1Y8ntCwQgoqhM=; b=CdboT7yo4EmAamWJmKz3Q8BfiLc/d316e5ePX2FlBwYdtbLKeooUx1sGFui0Z/9eQ/ VrpVNtAEl0MvJcdzcvpF6Q32faVlYvzLBgFktAzNUb6rBE4AmPB76+Qa/UKiE8bBwYcF SuuZ2UuNnErnS3PbRG0YdMKwuxfgO63L7Pll7y9UjWh2kPF7f6yHFWMd04gadp0xIN11 Z57iI+pW3WVjZfE6c3VZi49Kpg0FOr9ObA8Oew3/s576vZW3TmLP+szPK2+feKigZhN5 lPXjQTyJZReQX9QCz/jEGFovhIdYKqf3OP3cQzpYEz/C7HhxAjTnfrSfm3Rs++InYSJa D2Bg== X-Gm-Message-State: AOAM533SWv4i5hyJbQalrX/vMPiKB3VbIAKz0cl6Odzkd84MXSkkEHNE EC2pRqhvFkjxEssFVZhMnJpbVU4z7OyXokXRSIDfd02YrPe+p12sM8R9z+pM9zKJ0fiVVYckUl6 q5wLe6thExCBALWNsNoA/kJ5rQ8Y2IJ+4xvSAwOj0yJZQCaro6yT6SZAOTUzInUj1gUbtUQ== X-Received: by 2002:a05:6214:e4a:: with SMTP id o10mr4136812qvc.39.1626351881572; Thu, 15 Jul 2021 05:24:41 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzbUIzGLug6s/aZKfGCSiWH52ZlsVgxiKnODdbn5rR9YPu8mleIiQa36PDK6DIlraCtQQ91eg== X-Received: by 2002:a05:6214:e4a:: with SMTP id o10mr4136796qvc.39.1626351881393; Thu, 15 Jul 2021 05:24:41 -0700 (PDT) Received: from [192.168.1.16] (198-84-214-74.cpe.teksavvy.com. [198.84.214.74]) by smtp.gmail.com with ESMTPSA id 12sm2393574qkr.10.2021.07.15.05.24.40 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 15 Jul 2021 05:24:40 -0700 (PDT) Subject: Re: Buildbot improvements To: DJ Delorie , Adhemerval Zanella Cc: libc-alpha@sourceware.org References: From: Carlos O'Donell Organization: Red Hat Message-ID: Date: Thu, 15 Jul 2021 08:24:39 -0400 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: 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-Spam-Status: No, score=-6.2 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, 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: 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: , X-List-Received-Date: Thu, 15 Jul 2021 12:24:45 -0000 On 7/15/21 12:11 AM, DJ Delorie wrote: > Adhemerval Zanella writes: >> I take this builbot setup is used along with Fedora to stress both systems, >> but maybe it would better to use a more stable baseline to make it easier >> to reproduce. Either Fedora current or a way to download the required >> packages/tools. > > I use the published registry.fedoraproject.org/fedora base container. > We chose to use the latest container for security reasons, to make sure > we had all the current security errata etc. It probably won't change > often enough to be an issue, but it means that I can't guarantee an > exact reproduction of a given trybot container. > > Even if the containers were published, the trybot's container includes a > full copy of the glibc git tree at that moment, and we're hoping that > there will eventually be many trybots - not just mine - so consider the > cost of moving all that data around vs just running your own trybot ;-) > > Note that I'm not defending my choice here, just explaining it. I'm > open to new ideas and tweaks. I think a set of instructions that gets you *close enough* to the container environment and provides host details will be sufficient. e.g. podman pull [something] git clone [something] git-pw series apply [something] I agree with Adhemerval that when this fails we'll want any 3rd party to be able to explain how they got to their setup. I think the host config is relevant but that just needs to be discussed with the partner. If we had a "record commands" function and the integrator used it to record the steps taken then we could just print those out for the container? -- Cheers, Carlos.