From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 54063 invoked by alias); 5 Dec 2018 19:39:00 -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 54036 invoked by uid 89); 5 Dec 2018 19:39:00 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=busy, uncommon, During, socket X-HELO: mx0a-001b2d01.pphosted.com Received: from mx0a-001b2d01.pphosted.com (HELO mx0a-001b2d01.pphosted.com) (148.163.156.1) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 05 Dec 2018 19:38:58 +0000 Received: from pps.filterd (m0098399.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id wB5JYUZd075065 for ; Wed, 5 Dec 2018 14:38:57 -0500 Received: from e31.co.us.ibm.com (e31.co.us.ibm.com [32.97.110.149]) by mx0a-001b2d01.pphosted.com with ESMTP id 2p6j69g7dk-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Wed, 05 Dec 2018 14:38:57 -0500 Received: from localhost by e31.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 5 Dec 2018 19:38:56 -0000 Received: from b03cxnp07028.gho.boulder.ibm.com (9.17.130.15) by e31.co.us.ibm.com (192.168.1.131) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Wed, 5 Dec 2018 19:38:54 -0000 Received: from b03ledav006.gho.boulder.ibm.com (b03ledav006.gho.boulder.ibm.com [9.17.130.237]) by b03cxnp07028.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id wB5Jcrvb17629380 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 5 Dec 2018 19:38:53 GMT Received: from b03ledav006.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id C2B67C605B; Wed, 5 Dec 2018 19:38:53 +0000 (GMT) Received: from b03ledav006.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 8DB81C6057; Wed, 5 Dec 2018 19:38:53 +0000 (GMT) Received: from pedro.localdomain (unknown [9.18.235.147]) by b03ledav006.gho.boulder.ibm.com (Postfix) with ESMTP; Wed, 5 Dec 2018 19:38:53 +0000 (GMT) Received: by pedro.localdomain (Postfix, from userid 1000) id 1A7553C0426; Wed, 5 Dec 2018 17:38:51 -0200 (-02) From: Pedro Franco de Carvalho To: Sergio Durigan Junior , GDB Patches Cc: Sergio Durigan Junior Subject: Re: [PATCH] Implement timestamp'ed output on "make check" In-Reply-To: <20181122221240.15354-1-sergiodj@redhat.com> Date: Wed, 05 Dec 2018 19:39:00 -0000 MIME-Version: 1.0 Content-Type: text/plain x-cbid: 18120519-8235-0000-0000-00000E33804C X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00010177; HX=3.00000242; KW=3.00000007; PH=3.00000004; SC=3.00000270; SDB=6.01127462; UDB=6.00585622; IPR=6.00907596; MB=3.00024464; MTD=3.00000008; XFM=3.00000015; UTC=2018-12-05 19:38:55 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18120519-8236-0000-0000-00004399DA17 Message-Id: <87va47ojas.fsf@linux.vnet.ibm.com> X-IsSubscribed: yes X-SW-Source: 2018-12/txt/msg00061.txt.bz2 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, 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. 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). Thanks!! -- Pedro Franco de Carvalho