From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-relay-internal-0.canonical.com (smtp-relay-internal-0.canonical.com [185.125.188.122]) by sourceware.org (Postfix) with ESMTPS id 9562D385842A for ; Thu, 9 Mar 2023 23:28:17 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 9562D385842A Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=canonical.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=canonical.com Received: from mail-pj1-f70.google.com (mail-pj1-f70.google.com [209.85.216.70]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-relay-internal-0.canonical.com (Postfix) with ESMTPS id A1FE53F17A for ; Thu, 9 Mar 2023 23:28:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1678404496; bh=mIIgzWWgEKnjgJqIN7NpuUPX4OWuTNrT29OrHdeCLAg=; h=MIME-Version:References:In-Reply-To:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=LDIkQ78DYEKRKBL8vqyYmahOZ1R1Xc7ErDYfFMrNlgf5dTEZ5m7sCU+z0hUJ+oYM9 02E8n7x2sYRo0K+gkYYj7gk/I1Dl9aUVdcb4Gm/eDvjDOWxzKkZn5ioJ1Dwn7X6SCn LXNe/ZCQ24TL6s3ndWpZc+UPrxANLjE6f2uNkJ8xsHiQ2JjLBDS38hgfyzoFj0OtQ7 I9IRypfG2skjrm1YjgkcZiY9wF6nU4xEj/eR8ZuIvTk0Pg+vBzrBBpFEBasFfaFTnk jAxUwJxvNYQI3yEb4Zn7Hwu9cLJDKzCeQbtyNfiEpQKRVlq7po1nJMc9LYnRmbmhVs 27VWQy17kpP4Q== Received: by mail-pj1-f70.google.com with SMTP id gm13-20020a17090b100d00b0023704a72ca5so1519383pjb.4 for ; Thu, 09 Mar 2023 15:28:16 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678404495; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=mIIgzWWgEKnjgJqIN7NpuUPX4OWuTNrT29OrHdeCLAg=; b=6YqfkD4XQYdf0ZnEhZaLCyAYj9YIfKuWVvy/d/EZn00ouxJ6IC3DeYNFn0Ji7tvMuw 09DkvQV1phqxe2iOpzRRmmIPH1SSFHaDHFJQUTe7NDaJLOp14N7FYwIdTRJMTO/Tr270 CbL3SaNqxLZwnxIdRz8ykHCxq+JGTeJk/KQ+t1mNhZEompDQwUSf8ppTZQDRleTYNLul J4bamT3eGWievl2a+otRQAnQdVDYXZnuv2HevukrKWIMdAet5fsvgvKbXYj9QATGCcoP q/fxW6B9tD3+Qxdf7aIJ5kQwdzc1uzr6LKztBgcsvSjc1fLaaqmFJt15uP2p36z8WG8d fcuw== X-Gm-Message-State: AO0yUKVEgNSMeQ5YX2sliUHRGO0azplvkPNDFGn/nokaK1UXboy5Zwy8 f8RrwKmTwiuOzqMYw5/LWidfyFnRcnoHp451cYDrMV2BVu2vus97ccyyhmGVimAO4j7R2spV1/u Zgv9WbRPFr7v5LLbJNcoWl6XMdKwLIv93VgBW86eiXueMbak6vJVx3w== X-Received: by 2002:a17:90b:2352:b0:230:9de7:1d14 with SMTP id ms18-20020a17090b235200b002309de71d14mr8631615pjb.5.1678404494965; Thu, 09 Mar 2023 15:28:14 -0800 (PST) X-Google-Smtp-Source: AK7set/vOqLnGT5kGc24Y21DR1P7Qm6Gr/U3rrLnyNxW1f2vvR6iG+8CSaf+zQr1AHQ20BmJMfNyQ0piqb+64LmNYhY= X-Received: by 2002:a17:90b:2352:b0:230:9de7:1d14 with SMTP id ms18-20020a17090b235200b002309de71d14mr8631607pjb.5.1678404494637; Thu, 09 Mar 2023 15:28:14 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Michael Hudson-Doyle Date: Fri, 10 Mar 2023 12:28:03 +1300 Message-ID: Subject: Re: release branch policy and distributions To: DJ Delorie Cc: carlos@redhat.com, libc-alpha@sourceware.org, sam@gentoo.org, simon.chopin@canonical.com Content-Type: multipart/alternative; boundary="000000000000b1551305f67fff3e" X-Spam-Status: No, score=-3.8 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,HTML_MESSAGE,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: --000000000000b1551305f67fff3e Content-Type: text/plain; charset="UTF-8" On Thu, 9 Mar 2023 at 18:27, DJ Delorie wrote: > Michael Hudson-Doyle via Libc-alpha writes: > > I think running the glibc testsuite on a wider range of hardware would be > > the most significant thing we could do here. We do have quite a range of > > hardware for testing but I wouldn't know where to start about using it > for > > glibc pre-commit CI, > > Fortunately, I do :-) > Ah here I was talking about getting access to the machines internally :-) Thanks for the instructions though... > The code is here: https://gitlab.com/djdelorie/glibc-cicd > > The URL for your runner to track is: https://delorie.com/cicd/curator.cgi > (unless you want to run your own curator, but there's no need) > > You'll need to create an API token in our patchwork instance if you want > to report results. > > In general, your runner will inspect the event and decide what > testing[*], if any, your organization wants to do. It will then queue a > task that your trybots will dequeue and run. You organize queues based > on hardware types or pools or whatever, so for example you could have > some expensive-to-use AVX512 machine only run tests when the patch > mentions AVX512, or a raspberry pi pool that tests patches that touch > sysdeps/arm, etc. > > > [*] it doesn't have to be testing, it could be anything - like spell > checking patches to documentation, or checking coding standards, etc. > Even grepping for interesting new sandwich recipes, although I hope you > don't find any in glibc. > > --000000000000b1551305f67fff3e--