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 Tromey <tom@tromey.com>
Subject: Breakage on builder Fedora-x86_64-native-extended-gdbserver-m32, revision 7f6aba03b929d3d893378760eeeca431005fc5cd
Date: Sat, 05 Oct 2019 04:29:00 -0000	[thread overview]
Message-ID: <E1iGbhR-0006cy-4F@gdb-buildbot.osci.io> (raw)
In-Reply-To: <7f6aba03b929d3d893378760eeeca431005fc5cd-master-breakage@gdb-build>

Unfortunately it seems that there is a breakage on GDB.

Commit title: 'Introduce metadata style'
Revision: 7f6aba03b929d3d893378760eeeca431005fc5cd

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    guile/scm-pretty-print.o
  CXX    guile/scm-progspace.o
  CXX    guile/scm-safe-call.o
  CXX    guile/scm-string.o
  CXX    guile/scm-symbol.o
  CXX    guile/scm-symtab.o
  CXX    guile/scm-type.o
  CXX    guile/scm-utils.o
  CXX    guile/scm-value.o
  CXX    h8300-tdep.o
  CXX    hppa-bsd-tdep.o
  CXX    hppa-linux-tdep.o
  CXX    hppa-nbsd-tdep.o
  CXX    hppa-obsd-tdep.o
  CXX    hppa-tdep.o
  CXX    i386-bsd-tdep.o
  CXX    i386-cygwin-tdep.o
  CXX    i386-darwin-tdep.o
  CXX    i386-dicos-tdep.o
  CXX    i386-fbsd-tdep.o
  CXX    i386-gnu-tdep.o
  CXX    i386-go32-tdep.o
  CXX    i386-linux-tdep.o
  CXX    i386-nbsd-tdep.o
  CXX    i386-nto-tdep.o
  CXX    i386-obsd-tdep.o
  CXX    i386-sol2-tdep.o
  CXX    i386-tdep.o
  CXX    i387-tdep.o
  CXX    ia64-linux-tdep.o
  CXX    ia64-tdep.o
  CXX    ia64-vms-tdep.o
  CXX    inf-child.o
  CXX    inf-loop.o
  CXX    inf-ptrace.o
  CXX    infcall.o
  CXX    infcmd.o
  CXX    inferior.o
  CXX    inflow.o
  CXX    infrun.o
  CXX    inline-frame.o
  CXX    interps.o
  CXX    iq2000-tdep.o
  CXX    jit.o
  CXX    language.o
  CXX    linespec.o
  CXX    linux-fork.o
  CXX    linux-nat.o
  CXX    linux-record.o
  CXX    linux-tdep.o
  CXX    linux-thread-db.o
  CXX    lm32-tdep.o
  CXX    location.o
  CXX    m2-exp.o
  CXX    m2-lang.o
  CXX    m2-typeprint.o
  CXX    m2-valprint.o
  CXX    m32c-tdep.o
  CXX    m32r-linux-tdep.o
  CXX    m32r-tdep.o
  CXX    m68hc11-tdep.o
  CXX    m68k-bsd-tdep.o
  CXX    m68k-linux-tdep.o
  CXX    m68k-tdep.o
  CXX    machoread.o
  CXX    macrocmd.o
  CXX    macroexp.o
  CXX    macroscope.o
  CXX    macrotab.o
  CXX    main.o
  CXX    maint-test-options.o
  CXX    maint-test-settings.o
  CXX    maint.o
  CXX    mdebugread.o
  CXX    mem-break.o
  CXX    memattr.o
  CXX    memory-map.o
  CXX    memrange.o
  CXX    mep-tdep.o
  CXX    mi/mi-cmd-break.o
  CXX    mi/mi-cmd-catch.o
  CXX    mi/mi-cmd-disas.o
  CXX    mi/mi-cmd-env.o
  CXX    mi/mi-cmd-file.o
  CXX    mi/mi-cmd-info.o
  CXX    mi/mi-cmd-stack.o
  CXX    mi/mi-cmd-target.o
  CXX    mi/mi-cmd-var.o
  CXX    mi/mi-cmds.o
  CXX    mi/mi-common.o
  CXX    mi/mi-console.o
  CXX    mi/mi-getopt.o
  CXX    mi/mi-interp.o
  CXX    mi/mi-main.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=2653.098696


      parent reply	other threads:[~2019-10-05  4:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-05  3:44 Oh dear. I regret to inform you that commit 7f6aba03b929d3d893378760eeeca431005fc5cd might be unfortunate gdb-buildbot
2019-10-05  3:44 ` Breakage on builder Fedora-i686, revision 7f6aba03b929d3d893378760eeeca431005fc5cd gdb-buildbot
2019-10-05  4:29 ` gdb-buildbot [this message]

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=E1iGbhR-0006cy-4F@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