From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 107365 invoked by alias); 15 Dec 2017 17:29:20 -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 107302 invoked by uid 89); 15 Dec 2017 17:29:19 -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=urls X-HELO: mail-qk0-f175.google.com Received: from mail-qk0-f175.google.com (HELO mail-qk0-f175.google.com) (209.85.220.175) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 15 Dec 2017 17:29:17 +0000 Received: by mail-qk0-f175.google.com with SMTP id 63so11227515qke.0 for ; Fri, 15 Dec 2017 09:29:17 -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=4WFhZpotFgmUp0AuPS14qpcSF/OPiQ2Xt4SM0Kx6E7o=; b=h6+hivtYEh3gjulDPMUshNiT23uvEd4mbVgpdeaK5wuObsSeD/V0HMD9iz1jJ/ie05 DB7nAz0fEj3Ug3P4pnOR4/cnZKsP8x7vacdHxErQGP7U0Z7cnT9iWgaycp+QCgyw+9+W mou5Ry3G2+PUKjdOf7BGnzRJpcKVvVgYSCfP06WSUjGYhEkc9dg7qfBcaOEBOZ/9QlEu yfHWUqAlqZioxnWZ+EQJG7NNZa3Rs+Iv/8kywE4FG6mXVBQ4XOqvltx9Vl9qTdjmBi8B fBpsTJtwyYYxa0Lp5oq7aVEsQyoVzzgXCLalC4Y3VWc3EMb7bZmxZJ4/Gd8m9dVzaBtT cH2g== X-Gm-Message-State: AKGB3mKowEJ6kU0TcpgPHTvsh1HwlcDQaI/iN75wXVThS1J2kGl7G9Ec CMscjKAFtIfSpGZLQriPKERziPeZuD+6g/06Lsg= X-Google-Smtp-Source: ACJfBouFHe2wYJtWxW1ZHwgvH5h2Jw6DOr1TVZBNmW/NpljXHpuagSqv7jFjqVRCQhoTnQ6l3L8USIJ98T3yP3l9Vlo= X-Received: by 10.55.135.199 with SMTP id j190mr22120509qkd.188.1513358955976; Fri, 15 Dec 2017 09:29:15 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.196.134 with HTTP; Fri, 15 Dec 2017 09:29:15 -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 17:29: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/msg00386.txt.bz2 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. Thanks, David