From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 107876 invoked by alias); 5 Dec 2018 19:48:45 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 104449 invoked by uid 89); 5 Dec 2018 19:48:42 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,SPF_HELO_PASS autolearn=no version=3.3.2 spammy=busy, uncommon, socket, disabling X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 05 Dec 2018 19:48:40 +0000 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id D3775300158B; Wed, 5 Dec 2018 19:48:38 +0000 (UTC) Received: from localhost (unused-10-15-17-196.yyz.redhat.com [10.15.17.196]) by smtp.corp.redhat.com (Postfix) with ESMTP id 9A4121001640; Wed, 5 Dec 2018 19:48:38 +0000 (UTC) From: Sergio Durigan Junior To: Pedro Franco de Carvalho Cc: GDB Patches Subject: Re: [PATCH] Implement timestamp'ed output on "make check" References: <87va47ojas.fsf@linux.vnet.ibm.com> Date: Wed, 05 Dec 2018 19:48:00 -0000 In-Reply-To: <87va47ojas.fsf@linux.vnet.ibm.com> (Pedro Franco de Carvalho's message of "Wed, 05 Dec 2018 17:38:51 -0200") Message-ID: <87a7ljdaax.fsf@redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes X-SW-Source: 2018-12/txt/msg00062.txt.bz2 On Wednesday, December 05 2018, Pedro Franco de Carvalho wrote: > Sergio Durigan Junior writes: > >> It is unfortunately not uncommon to have tests hanging on some of the >> BuildBot workers. For example, the ppc64be/ppc64le+gdbserver builders >> are especially in a bad state when it comes to testing GDB/gdbserver, >> and we can have builds that take an absurd amount of time to >> finish (almost 1 week for one single build, for example). >> >> It may be hard to diagnose these failures, because sometimes we don't >> have access to the faulty systems, and other times we're just too busy >> to wait and check which test is actually hanging. During one of our >> conversations about the topic, someone proposed that it would be a >> good idea to have a timestamp put together with stdout output, so that >> we can come back later and examine which tests are taking too long to >> complete. > > Hello Sergio, Hey Pedro, > I've looked into the ppc64le native-gdbserver/native-extended-gdbserver > buildbot workers, it seems that they started getting slower with this > patch: > > f19c7ff839d7a32ebb48482ae7d318fb46ca823d > GDBSERVER: Listen on a unix domain (instead of TCP) socket if requested. >From my recollection, ISTR that the gdbserver builders were *very* slow even before this commit. I was even talking to Edjunior about disabling the gdbserver builders, because they were just contributing to making the queue larger for the native builder. > I believe this patch has been reverted, but the builders haven't reached > the reverted point yet. Would it make sense to make the workers resume > after the reverted patch? This would be at commit > 80e24d09860dbeba7d435b4a4f0990f85dbc084e. > > They did also get even slower after this patch: > > fe1a5cad302b5535030cdf62895e79512713d738 > [gdb/testsuite] Log wait status on process no longer exists error > > But I think it only happens in combination with the patch above (see > https://sourceware.org/ml/gdb-patches/2018-12/msg00060.html for a more > detailed explanation). Alright. I'll try to cancel the builds up until 80e24d09860dbeba7d435b4a4f0990f85dbc084e and see how things go. Thanks for taking the time to investigate this! -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/