public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj@redhat.com
To: gdb-testers@sourceware.org
Subject: Failures on Debian-i686, branch gdb-7.9-branch
Date: Tue, 03 Feb 2015 10:56:00 -0000	[thread overview]
Message-ID: <E1YIXbZ-0005to-P8@kwanyin.sergiodj.net> (raw)

Buildslave:
	wildebeest-debian-wheezy-i686

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Debian-i686/builds/40>

Commit(s) tested:
	b9f28929592990231bdce7b44369afc184a55f5d

Author(s) (in the same order as the commits):
	Joel Brobecker <brobecker@adacore.com>

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Debian-i686/.git/tree/?h=gdb-7.9-branch&id=a24eb3a9ad553c0dc801d76f58c5a1c50f4d4b8c>

*** Regressions found ***
============================
PASS -> FAIL: gdb.base/longjmp.exp: next over patt3
============================




             reply	other threads:[~2015-02-03  7:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03 10:56 sergiodj [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-05-29 17:52 [binutils-gdb/gdb-7.9-branch] PR gdb/18464: Do not crash on unrecognized GNU .note.ABI-tag values sergiodj+buildbot
2015-05-29 18:34 ` Failures on Debian-i686, branch gdb-7.9-branch sergiodj+buildbot
2015-04-29  6:16 [binutils-gdb/gdb-7.9-branch] PR python/18299 sergiodj+buildbot
2015-04-29  7:32 ` Failures on Debian-i686, branch gdb-7.9-branch sergiodj+buildbot
2015-02-26 12:11 [binutils-gdb/gdb-7.9-branch] Remove // comment in gdb/iq2000-tdep.c sergiodj+buildbot
2015-02-26 18:39 ` Failures on Debian-i686, branch gdb-7.9-branch sergiodj+buildbot
2015-02-20 19:31 Test results for commit c9ae55c9597064a8fe9a20899a17a394ac4ee3f8 on " sergiodj
2015-02-20 19:52 ` Failures on Debian-i686, " sergiodj
2015-02-20  4:06 Test results for commit 3b7a39661610038aad32563069b10fb2cfc55fab on " sergiodj
2015-02-20  8:02 ` Failures on Debian-i686, " sergiodj
2015-02-19 15:26 Test results for commit 3b41352824ddc32dabca2d3281a03b4a0b8c7a27 on " sergiodj
2015-02-19 20:39 ` Failures on Debian-i686, " sergiodj
2015-02-17 15:08 Test results for commit 5991bec1d4dbd23b476dc90bc6d1ba70e044898e on " sergiodj
2015-02-17 19:11 ` Failures on Debian-i686, " sergiodj
2015-02-11 15:19 Test results for commit 46d020960241fcafd7d0ab483746a206829620ea on " sergiodj
2015-02-13  5:49 ` Failures on Debian-i686, " sergiodj
2015-02-11 14:04 Test results for commit 25a0672ba8b7f4badc682eaf08a1e342b496b483 on " sergiodj
2015-02-12 17:15 ` Failures on Debian-i686, " sergiodj
2015-02-04 17:37 sergiodj
2015-02-03  7:35 sergiodj
2015-02-02  0:49 sergiodj
2015-01-31  5:23 sergiodj

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=E1YIXbZ-0005to-P8@kwanyin.sergiodj.net \
    --to=sergiodj@redhat.com \
    --cc=gdb-testers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).