public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj@redhat.com
To: gdb-testers@sourceware.org
Subject: Failures on Fedora-i686, branch gdb-7.9-branch
Date: Thu, 29 Jan 2015 02:38:00 -0000	[thread overview]
Message-ID: <E1YGe6B-0006Ur-NP@kwanyin.sergiodj.net> (raw)

Buildslave:
	fedora-x86-64-1

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

Commit(s) tested:
	dd25c4e757b07110efce8680ad530a4388f9d660

Author(s) (in the same order as the commits):
	GDB Administrator <gdbadmin@sourceware.org>

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

*** Regressions found ***
============================
new FAIL: gdb.ada/interface.exp: print s
new FAIL: gdb.ada/iwide.exp: print My_Drawable
new FAIL: gdb.ada/iwide.exp: print d_access.all
new FAIL: gdb.ada/iwide.exp: print dp_access.all
new FAIL: gdb.ada/iwide.exp: print s_access.all
new FAIL: gdb.ada/iwide.exp: print sp_access.all
new FAIL: gdb.ada/mi_interface.exp: Create ggg1 varobj
new FAIL: gdb.ada/mi_interface.exp: list ggg1's children
new FAIL: gdb.ada/ptype_tagged_param.exp: ptype s
new FAIL: gdb.ada/str_uninit.exp: print my_str
new FAIL: gdb.ada/tagged.exp: print obj
new FAIL: gdb.ada/tagged.exp: ptype obj
new FAIL: gdb.ada/tagged_access.exp: ptype c.all
new FAIL: gdb.ada/tagged_access.exp: ptype c.menu_name
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: begin testing fpu env
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: push st0
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: push st0 <<10>>
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: push st0 <<11>>
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: push st0 <<12>>
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: push st0 <<13>>
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: push st0 <<14>>
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: push st0 <<15>>
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: push st0 <<2>>
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: push st0 <<3>>
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: push st0 <<4>>
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: push st0 <<5>>
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: push st0 <<6>>
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: push st0 <<7>>
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: push st0 <<8>>
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: push st0 <<9>>
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: record to end of main
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: restore FPU env
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: rewind to beginning of main
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: save FPU env in memory
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: store status word in EAX
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: verify eax == 0x8040000
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: verify fstat == 0x1000
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: verify fstat == 0x1000 <<2>>
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: verify fstat == 0x1800
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: verify fstat == 0x1800 <<2>>
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: verify fstat == 0x2000
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: verify fstat == 0x2000 <<2>>
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: verify fstat == 0x2800
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: verify fstat == 0x2800 <<2>>
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: verify fstat == 0x3000
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: verify fstat == 0x3000 <<2>>
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: verify fstat == 0x3800
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: verify fstat == 0x3800 <<2>>
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: verify fstat == 0x800
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: verify ftag  == 0x3f
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: verify ftag  == 0x3f <<2>>
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: verify ftag  == 0x3ff
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: verify ftag  == 0x3ff <<2>>
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: verify ftag  == 0x3fff
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: verify ftag  == 0x3fff <<2>>
PASS -> FAIL: gdb.reverse/i387-env-reverse.exp: verify ftag  == 0x7
============================




             reply	other threads:[~2015-01-29  1:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29  2:38 sergiodj [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-05-30 11:03 [binutils-gdb/gdb-7.9-branch] Unbreak DJGPP build of GDB sergiodj+buildbot
2015-05-30 12:16 ` Failures on Fedora-i686, branch gdb-7.9-branch sergiodj+buildbot
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 20:41 ` Failures on Fedora-i686, branch gdb-7.9-branch sergiodj+buildbot
2015-05-13 17:56 [binutils-gdb/gdb-7.9-branch] Bump GDB version number to 7.9.1.DATE-cvs sergiodj+buildbot
2015-05-14  1:05 ` Failures on Fedora-i686, branch gdb-7.9-branch sergiodj+buildbot
2015-05-13 17:38 [binutils-gdb/gdb-7.9-branch] Set GDB version number to 7.9.1 sergiodj+buildbot
2015-05-13 23:18 ` Failures on Fedora-i686, branch gdb-7.9-branch sergiodj+buildbot
2015-05-12 16:20 [binutils-gdb/gdb-7.9-branch] PR python/18285 sergiodj+buildbot
2015-05-12 16:41 ` Failures on Fedora-i686, branch gdb-7.9-branch sergiodj+buildbot
2015-05-02 22:52 [binutils-gdb/gdb-7.9-branch] Subject: [PATCH] Fix pascal behavior for class fields with testcase sergiodj+buildbot
2015-05-02 23:01 ` Failures on Fedora-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  9:43 ` Failures on Fedora-i686, branch gdb-7.9-branch sergiodj+buildbot
2015-03-21 11:59 [binutils-gdb/gdb-7.9-branch] Fix undefined behavior in TUI's TAB expansion sergiodj+buildbot
2015-03-23  7:46 ` Failures on Fedora-i686, branch gdb-7.9-branch sergiodj+buildbot
2015-02-20 18:08 Test results for commit 1435f081d10098b0bff7e30273c1c2611c35c4f9 on " sergiodj
2015-02-20 18:18 ` Failures on Fedora-i686, " sergiodj
2015-02-20  4:06 Test results for commit 3b7a39661610038aad32563069b10fb2cfc55fab on " sergiodj
2015-02-20  8:07 ` Failures on Fedora-i686, " sergiodj
2015-02-19 14:13 Test results for commit 77ef543e9e7861214232c63c960eddf19674cf61 on " sergiodj
2015-02-19 15:07 ` Failures on Fedora-i686, " sergiodj
2015-02-17 13:49 Test results for commit d4a0a1ff2b7f3d50180229768a270750ef94bbdf on " sergiodj
2015-02-17 14:21 ` Failures on Fedora-i686, " sergiodj
2015-02-17 12:43 Test results for commit 140e2c62fd7a46b4500dbd442964543587c0337b on " sergiodj
2015-02-17 12:56 ` Failures on Fedora-i686, " sergiodj
2015-02-04 14:25 sergiodj
2015-02-02  1:53 sergiodj
2015-01-30  1:15 sergiodj
2015-01-29 19:49 sergiodj
2015-01-28  1:15 sergiodj
2015-01-27 15:59 sergiodj
2015-01-27  1:23 sergiodj
2015-01-26 16:36 sergiodj
2015-01-26  1:56 sergiodj
2015-01-25  9:17 sergiodj
2015-01-25  2:42 sergiodj
2015-01-24  2:22 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=E1YGe6B-0006Ur-NP@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).