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 ESMTPS id EF3163858D33 for ; Thu, 9 Mar 2023 05:27:06 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org EF3163858D33 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1678339626; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to; bh=ENZo/zeRSeoEAdYN3l3kJUq1Yq//LvdVUNj6DU3Ixs8=; b=GHi/vN8XKfCK7gTFhfbS2UuwzG1RnAf74FacnqS73Cvk8SsFq8D1Rl3K3x7cxLqYdi3R0g ofnwMVc7hJ0gsIdhwHGV55kH6FHzUg55Vl2/FTxATvx3ENdEOns2Hu8ix1rhWMLFIe6DjR 2SQdMJi0xAv++mRkTid55wNEwWZimMk= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-380-EuX2_LwmP_uUSLPE9PPGGQ-1; Thu, 09 Mar 2023 00:27:03 -0500 X-MC-Unique: EuX2_LwmP_uUSLPE9PPGGQ-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 264C01C05AA4; Thu, 9 Mar 2023 05:27:03 +0000 (UTC) Received: from greed.delorie.com (unknown [10.22.9.14]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 098F1C15BA0; Thu, 9 Mar 2023 05:27:02 +0000 (UTC) Received: from greed.delorie.com.redhat.com (localhost [127.0.0.1]) by greed.delorie.com (8.15.2/8.15.2) with ESMTP id 3295R1oe3224514; Thu, 9 Mar 2023 00:27:02 -0500 From: DJ Delorie To: Michael Hudson-Doyle Cc: carlos@redhat.com, libc-alpha@sourceware.org, sam@gentoo.org, simon.chopin@canonical.com Subject: Re: release branch policy and distributions In-Reply-To: Date: Thu, 09 Mar 2023 00:27:01 -0500 Message-ID: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.8 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-4.8 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,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: 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 :-) 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.