From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from elastic.org (elastic.org [96.126.110.187]) by sourceware.org (Postfix) with ESMTPS id 49BA13858D32 for ; Mon, 22 Aug 2022 14:58:51 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 49BA13858D32 Received: from vpn-home.elastic.org ([10.0.0.2] helo=elastic.org) by elastic.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1oQ8t2-0005eA-Qx; Mon, 22 Aug 2022 14:58:44 +0000 Received: from very.elastic.org ([192.168.1.1]) by elastic.org with esmtp (Exim 4.94.2) (envelope-from ) id 1oQ8t2-0007W7-Aa; Mon, 22 Aug 2022 10:58:44 -0400 Received: from fche by very.elastic.org with local (Exim 4.95) (envelope-from ) id 1oQ8t2-008PPs-9t; Mon, 22 Aug 2022 10:58:44 -0400 Date: Mon, 22 Aug 2022 10:58:44 -0400 From: "Frank Ch. Eigler" To: Florian Weimer Cc: Mark Wielaard , Thomas Fitzsimmons , 'GNU C Library' , Wilco Dijkstra Subject: Re: [PATCH] Improve performance of IO locks Message-ID: References: <878rnoeja2.fsf@oldenburg.str.redhat.com> <87pmh0cxh8.fsf@oldenburg.str.redhat.com> <871qt81snr.fsf@oldenburg.str.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <871qt81snr.fsf@oldenburg.str.redhat.com> X-Sender-Verification: "" X-Spam-Status: No, score=-101.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_SHORT, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE, USER_IN_WELCOMELIST, USER_IN_WHITELIST autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) 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: Mon, 22 Aug 2022 14:58:53 -0000 Hi - > > Another is to look at all results for a particular builder (as above) > > or to look at all the glibc builds using the (sql) search form. e.g. > > https://builder.sourceware.org/testruns/?has_keyvalue_like_k=testrun.git_describe&has_keyvalue_like_v=%25glibc%25 > > Thank you for these links, they surely look useful. I assume the zebra > pattern in the table is not actually meaningful (it's too regular for > that), it's just to improve readability, right? Correct. > What confuses me still is that the run lists do not seem to have numbers > with failure counts. Yes, while one can view fail/etc. counts of all the test cases in one testrun [https://tinyurl.com/mry25ekt], there is no single view that contrasts such counts for multiple runs. It's coming. - FChE