Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: gdb-patches@sourceware.org
To: gdb-patches@sourceware.org, Tom de Vries <tdevries@suse.de>
Subject: Breakage on builder Fedora-x86_64-native-gdbserver-m64, revision 060b3ab4edadfc0d55e606598769c1e5315fd74c
Date: Thu, 03 Oct 2019 22:34:00 -0000	[thread overview]
Message-ID: <E1iG9gJ-00010D-SG@gdb-buildbot.osci.io> (raw)
In-Reply-To: <060b3ab4edadfc0d55e606598769c1e5315fd74c-master-breakage@gdb-build>

Unfortunately it seems that there is a breakage on GDB.

Commit title: '[gdb/testsuite] Fix incomplete regexps in step-precsave.exp'
Revision: 060b3ab4edadfc0d55e606598769c1e5315fd74c

You can find more details below:

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


+++ The full log is too big to be posted here.
+++ These are the last 100 lines of it.

  CXX    c-typeprint.o
  CXX    c-valprint.o
  CXX    c-varobj.o
  CXX    charset.o
  CXX    cli-out.o
  CXX    cli/cli-cmds.o
  CXX    cli/cli-decode.o
  CXX    cli/cli-dump.o
  CXX    cli/cli-interp.o
  CXX    cli/cli-logging.o
  CXX    cli/cli-option.o
  CXX    cli/cli-script.o
  CXX    cli/cli-setshow.o
  CXX    cli/cli-style.o
  CXX    cli/cli-utils.o
  CXX    coff-pe-read.o
  CXX    coffread.o
  CXX    compile/compile-c-support.o
  CXX    compile/compile-c-symbols.o
  CXX    compile/compile-c-types.o
  CXX    compile/compile-cplus-symbols.o
  CXX    compile/compile-cplus-types.o
  CXX    compile/compile-loc2c.o
  CXX    compile/compile-object-run.o
  CXX    compile/compile-object-load.o
  CXX    compile/compile.o
  CXX    complaints.o
  CXX    completer.o
  CXX    continuations.o
  CXX    copying.o
  CXX    corefile.o
  CXX    corelow.o
  CXX    cp-abi.o
  CXX    cp-name-parser.o
  CXX    cp-namespace.o
  CXX    cp-support.o
  CXX    cp-valprint.o
  CXX    cris-linux-tdep.o
  CXX    cris-tdep.o
  CXX    csky-linux-tdep.o
  CXX    csky-tdep.o
  CXX    ctf.o
  CXX    d-exp.o
  CXX    d-lang.o
  CXX    d-namespace.o
  CXX    d-valprint.o
  CXX    dbxread.o
  CXX    dcache.o
  CXX    debug.o
  CXX    demangle.o
  CXX    dicos-tdep.o
  CXX    dictionary.o
  CXX    disasm-selftests.o
  CXX    disasm.o
  CXX    dtrace-probe.o
  CXX    dummy-frame.o
  CXX    dwarf-index-cache.o
  CXX    dwarf-index-common.o
  CXX    dwarf-index-write.o
  CXX    dwarf2-frame-tailcall.o
  CXX    dwarf2-frame.o
  CXX    dwarf2expr.o
  CXX    dwarf2loc.o
  CXX    dwarf2read.o
  CXX    elfread.o
  CXX    eval.o
  CXX    event-loop.o
  CXX    event-top.o
  CXX    exceptions.o
  CXX    exec.o
  CXX    expprint.o
  CXX    extension.o
  CXX    f-exp.o
  CXX    f-lang.o
  CXX    f-typeprint.o
  CXX    f-valprint.o
  CXX    fbsd-tdep.o
  CXX    filename-seen-cache.o
  CXX    filesystem.o
  CXX    findcmd.o
  CXX    findvar.o
  CXX    fork-child.o
  CXX    frame-base.o
  CXX    frame-unwind.o
  CXX    frame.o
  CXX    frv-linux-tdep.o
  CXX    frv-tdep.o
  CXX    ft32-tdep.o
  CXX    gdb_bfd.o
  CXX    gcore.o
  CXX    gdb_obstack.o
  CXX    gdb_regex.o
  CXX    gdbarch-selftests.o
  CXX    gdbarch.o

command timed out: 1200 seconds without output running [b'make', b'-j2', b'all'], attempting to kill
process killed by signal 9
program finished with exit code -1
elapsedTime=1532.955936


  parent reply	other threads:[~2019-10-03 22:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-03 22:03 Oh dear. I regret to inform you that commit 060b3ab4edadfc0d55e606598769c1e5315fd74c might be unfortunate gdb-buildbot
2019-10-03 22:03 ` Breakage on builder Fedora-x86_64-native-gdbserver-m32, revision 060b3ab4edadfc0d55e606598769c1e5315fd74c gdb-buildbot
2019-10-03 22:08 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2019-10-03 22:34 ` gdb-buildbot [this message]
2019-10-03 22:43 ` Oh dear. I regret to inform you that commit 060b3ab4edadfc0d55e606598769c1e5315fd74c might be unfortunate Sergio Durigan Junior

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1iG9gJ-00010D-SG@gdb-buildbot.osci.io \
    --to=gdb-buildbot@sergiodj.net \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox