From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2987 invoked by alias); 15 Dec 2017 18:55:46 -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 2977 invoked by uid 89); 15 Dec 2017 18:55:45 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy= X-HELO: mail-qk0-f179.google.com Received: from mail-qk0-f179.google.com (HELO mail-qk0-f179.google.com) (209.85.220.179) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 15 Dec 2017 18:55:43 +0000 Received: by mail-qk0-f179.google.com with SMTP id u184so11544154qkd.6 for ; Fri, 15 Dec 2017 10:55:43 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=okM5XB7JrNjsseBSgP7A3r8qSLGk91S0F3F6tgfEHng=; b=finODJ4ImvOacROweLjnJiHtsxC0K6go9uUYSxkSAvL2nT2vW6tnoiXKyWM3A0Q8vc WJFu6XUtRl5O1PYwobiYixHgkceXOzFF2hNTLXaquGWEAFwX4jlMSxY/zEawsFOOTwNp 5rgeu3Up3r/w6DQlc6tbCFKbw4rHzMTs/auxsPQArZSK14QNrnbE5SJ9Fb/UnX6YD3X0 x/bWr/nyE6XP9dQaEupEkgVvsCAqb9vn9jwlqPebG4RtsV1jutM/CRTWZh0B8J+nqecj 9YzjPKgs3q+CA4Rw4QrIR6wS75h0sXWZy8O9kpCdCQ7vzKATpu4BmRKWbgCYqjJh66/D YP6w== X-Gm-Message-State: AKGB3mL01eiNdZrsA5pjJTkUlxO2fYBgOX6UIeArg9l0OFBTv5P8lVXb YiPN277ffuTxtwjfnwLgTgTLbLoX/SI89U7sn30= X-Google-Smtp-Source: ACJfBotYIsTYyWLQa7gGOR4ArzWIFYwqt2RuzM5E28xVZy44mnCS73HtiXS9lSSG9/wvCWnJzvWBMr/gMmbg/o8TRGs= X-Received: by 10.55.43.89 with SMTP id r86mr3689965qkh.33.1513364142125; Fri, 15 Dec 2017 10:55:42 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.196.134 with HTTP; Fri, 15 Dec 2017 10:55:41 -0800 (PST) In-Reply-To: References: <87d13g6r5t.fsf@redhat.com> <878te46pk4.fsf@redhat.com> <3808c9ac-450e-3d53-d5c6-ddd7f4b8d1df@redhat.com> From: David Edelsohn Date: Fri, 15 Dec 2017 18:55:00 -0000 Message-ID: Subject: Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders To: Pedro Alves Cc: Sergio Durigan Junior , GDB Patches , Edjunior Machado Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2017-12/txt/msg00389.txt.bz2 On Fri, Dec 15, 2017 at 12:29 PM, David Edelsohn wrote: > On Fri, Dec 15, 2017 at 11:20 AM, Pedro Alves wrote: >> On 12/15/2017 03:53 PM, David Edelsohn wrote: >>> On Fri, Dec 15, 2017 at 10:42 AM, Pedro Alves wrote: >>>> On 12/15/2017 03:06 PM, David Edelsohn wrote: >>>> >>>>> Third, the testsuite summaries that no one from the GDB community >>>>> monitored show that the testsuite runtime jumped from a relatively >>>>> short amount of time to over 9 hours for each run, which points to a >>>>> newly introduced problem in GDB or in the testsuite (timeouts?). >>>> >>>> That may well be. Can you point at some representative builds, >>>> before/after the jump? >>> >>> The testsuite runs for 6 minutes on RHEL7 s390x buildslave and 9 hours >>> on Debian Jessie s390x buildslave. >> >> Those are separate machines. I'd like to see the jump on the same >> machine, so we can maybe pinpoint what caused it. >> >> I was really asking for URLs. Here looks like there's some: >> >> https://gdb-build.sergiodj.net/builders/Debian-s390x-native-gdbserver-m64 >> >> Here, for example: >> >> https://gdb-build.sergiodj.net/builders/Debian-s390x-native-gdbserver-m64/builds/4351 >> >> "test gdb tested GDB failed (9 hrs, 2 mins, 56 secs)" >> >> That's definitely too long. >> >> I downloaded the gdb.log file, and did: >> >> $ grep FAIL gdb.log | grep timeout | sed 's/.exp.*/.exp/g' | sort | uniq -c | sort -n >> 1 FAIL: gdb.base/watch-cond.exp >> 1 FAIL: gdb.multi/watchpoint-multi-exit.exp >> 1 FAIL: gdb.threads/interrupted-hand-call.exp >> 1 FAIL: gdb.threads/thread-unwindonsignal.exp >> 2 FAIL: gdb.base/value-double-free.exp >> 3 FAIL: gdb.mi/mi-async.exp >> 3 FAIL: gdb.threads/process-dies-while-detaching.exp >> 4 FAIL: gdb.base/pr11022.exp >> 10 FAIL: gdb.base/watch-bitfields.exp >> 15 FAIL: gdb.base/watchpoints.exp >> 20 FAIL: gdb.threads/interrupt-while-step-over.exp >> 32 FAIL: gdb.threads/watchpoint-fork.exp >> 45 FAIL: gdb.threads/step-over-trips-on-watchpoint.exp >> 46 FAIL: gdb.base/display.exp >> 51 FAIL: gdb.base/watchpoint.exp >> >> Not _that_ many. Could they explain the long time? I suspect not. >> >> We see this: >> >> $ grep "Test run by" gdb.log | head -n 3 >> Test run by dje on Tue Nov 21 03:23:01 2017 >> Test run by dje on Tue Nov 21 03:23:01 2017 >> Test run by dje on Tue Nov 21 03:23:01 2017 >> >> $ grep "Test run by" gdb.log | tail -n 3 >> Test run by dje on Tue Nov 21 03:29:54 2017 >> Test run by dje on Tue Nov 21 03:29:54 2017 >> Test run by dje on Tue Nov 21 03:29:54 2017 >> >> So most of the testsuite actually ran for 7 minutes. And then >> something hung for 9 hours? I have no idea how that >> could happen from the existing logs. The tail end of the log has: >> >> ~~~ >> FAIL: gdb.base/watchpoint.exp: delete all breakpoints in delete_breakpoints (timeout) >> ERROR: breakpoints not deleted >> ERROR: breakpoints not deleted >> >> command timed out: 1200 seconds without output running ['make', '-k', 'check', 'RUNTESTFLAGS=--target_board native-gdbserver', '-j8', 'FORCE_PARALLEL=1'], attempting to kill >> process killed by signal 9 >> program finished with exit code -1 >> elapsedTime=32576.210392 >> ~~~ >> >> I don't understand how 7 minutes plus 1200 seconds (~20min) >> resulted in "elapsedTime=32576.210392" (~9h). Maybe that number >> isn't to be trusted. >> >> Anyway, I'm sorry, but I really don't have the time to be >> looking at this. Someone with the motivation and access to >> the machine could try running the testsuite manually, >> for example, see how long that takes, and where the hang is. > > I will try reverting to an older version of DejaGNU framework. Older DejaGNU does not seem to have an effect. All of the processes are stuck in "gdb.threads/process-dies-while-handling-bp" Thanks, David