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 0773E3858D32 for ; Mon, 22 Aug 2022 10:25:51 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 0773E3858D32 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-58-vOBNLdDNO8OkAa7EE1RnNA-1; Mon, 22 Aug 2022 06:25:47 -0400 X-MC-Unique: vOBNLdDNO8OkAa7EE1RnNA-1 Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 1244C3C10221; Mon, 22 Aug 2022 10:25:47 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.39.192.199]) by smtp.corp.redhat.com (Postfix) with ESMTPS id CA02B492C3B; Mon, 22 Aug 2022 10:25:45 +0000 (UTC) From: Florian Weimer To: Mark Wielaard Cc: Thomas Fitzsimmons , 'GNU C Library' , Wilco Dijkstra , "Frank Ch. Eigler" Subject: Re: [PATCH] Improve performance of IO locks References: <878rnoeja2.fsf@oldenburg.str.redhat.com> <87pmh0cxh8.fsf@oldenburg.str.redhat.com> Date: Mon, 22 Aug 2022 12:25:44 +0200 In-Reply-To: (Mark Wielaard's message of "Wed, 17 Aug 2022 15:45:13 +0200") Message-ID: <871qt81snr.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.85 on 10.11.54.10 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-5.2 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE 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 10:25:52 -0000 * Mark Wielaard: > Hi Florian, > > On Tue, Aug 16, 2022 at 12:08:03PM +0200, Florian Weimer wrote: >> * Mark Wielaard: >> > Yeah, I am actually surprised just reverting the patch fixed things. >> > But looking at the bunsen data for glibc-debian-ppc64 does seem to >> > show that the only thing changed is this particular patch. Runs before >> > it pass, runs after show lots of fails. >> > >> > https://builder.sourceware.org/testruns/?has_keyvalue_like_k=testrun.git_describe&has_keyvalue_like_v=%25glibc-debian-ppc64%25 >> >> How do I read this table? > > Glad you ask! Although I think the mystery of the debian-ppc64 build > failure has now been solved, the intent of the bunsenweb tool is to > help figure out test result differences between builders. I have added > Frank to the CC who can explain better than me. We'll also have a BoF > at the GNU Tools Cauldron for suggestions on how the improve it and > the integration with other sourceware services [*]. > > So the table above is all the builds that bunsen knows about for > glibc-debian-ppc64. Note that currently we only have one ppc64[be] > worker that does glibc builds. > > You can select a couple of builds and compare them. Pick the failing > one, which was 498f51, and the last succeeding one. And compare the > results, configs, etc. > There are a couple of ways to explore the diffs. One is by looking at > the buildbot "upload to bunsen" step and select that URL (this really > should be improved to make this easier to find). This then gives you > different "clusters" of similar (but possible different) other builds > to compare to. e.g. look at > https://builder.sourceware.org/testrun/498f51f327afdd7030516455b709a31a0038b432 > > 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? What confuses me still is that the run lists do not seem to have numbers with failure counts. Thanks, Florian