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-x86_64-m32
Date: Sat, 24 Jan 2015 00:08:00 -0000 [thread overview]
Message-ID: <E1YEj4q-0006ai-OQ@kwanyin.sergiodj.net> (raw)
Buildslave:
fedora-x86-64-2
Commit(s) tested:
f7e5394d614db4456fc0d9598bbfa936cc7941af
Author(s) (in the same order as the commits):
Simon Marchi <simon.marchi@ericsson.com>
Log URL(s):
<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?id=2d55cdf2f74a8eb06cafbc5a00ee75237638a36d>
*** Regressions found ***
============================
PASS -> FAIL: gdb.base/interrupt.exp: echo data
============================
Failures that are being ignored:
FAIL: gdb.ada/interface.exp: print s
FAIL: gdb.ada/iwide.exp: print My_Drawable
FAIL: gdb.ada/iwide.exp: print d_access.all
FAIL: gdb.ada/iwide.exp: print dp_access.all
FAIL: gdb.ada/iwide.exp: print s_access.all
FAIL: gdb.ada/iwide.exp: print sp_access.all
FAIL: gdb.ada/mi_interface.exp: Create ggg1 varobj
FAIL: gdb.ada/mi_interface.exp: list ggg1's children
FAIL: gdb.ada/ptype_tagged_param.exp: ptype s
FAIL: gdb.ada/str_uninit.exp: print my_str
FAIL: gdb.ada/tagged.exp: print obj
FAIL: gdb.ada/tagged.exp: ptype obj
FAIL: gdb.ada/tagged_access.exp: ptype c.all
FAIL: gdb.ada/tagged_access.exp: ptype c.menu_name
FAIL: gdb.base/interrupt.exp: continue
next reply other threads:[~2015-01-23 18:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-24 0:08 sergiodj [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-01-23 16:53 sergiodj
2015-01-23 11:25 sergiodj
2015-01-23 7:40 sergiodj
2015-01-22 23:33 sergiodj
2015-01-20 10:32 sergiodj
2015-01-19 17:33 sergiodj
2015-01-16 16:50 buildbot
2015-01-16 0:47 buildbot
2015-01-16 17:03 ` Sergio Durigan Junior
2015-01-15 21:11 buildbot
2015-01-15 19:50 buildbot
2015-01-15 17:12 buildbot
2015-01-15 13:58 buildbot
2015-01-15 12:03 buildbot
2015-01-15 11:07 buildbot
2015-01-15 9:48 buildbot
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=E1YEj4q-0006ai-OQ@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).