From: Jan Vrany <jan.vrany@fit.cvut.cz>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: MI / Python tests failing on my machine (x86_64)
Date: Wed, 05 Jul 2017 06:42:00 -0000 [thread overview]
Message-ID: <1499236932.24598.1.camel@fit.cvut.cz> (raw)
Hi there,
I'm experimenting with Didier Nadeau's patches for python-defined
MI commands [1]
I tried to compile recent gdb (25c5412713ba) and then run MI and python
tests to ensure all is OK before I start hacking.
I run these tests using:
make check RUNTESTFLAGS='TRANSCRIPT=y gdb.mi/*.exp gdb.python/*.exp'Â
but 58 tests seems to fail:
# of expected passes 4810
# of unexpected failures 58
# of expected failures 9
# of known failures 13
# of untested testcases 3
# of unsupported tests 1
For GDB 8.0.0 (1f1c02597cc1) test results are the same on my machine.
I compiled gdb on Linux (Debian Jessie if that matters) using simple
./configure && make
Is that expected? Do I need to perform some additional setup to run
tests?
Thanks, Jan
[1]: https://sourceware.org/ml/gdb/2017-06/msg00010.html
next reply other threads:[~2017-07-05 6:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 6:42 Jan Vrany [this message]
2017-07-05 9:46 ` Phil Muldoon
2017-07-10 19:58 ` Jan Vrany
2017-07-11 15:19 ` Yao Qi
2017-07-12 14:21 ` Jan Vrany
2017-07-25 11:04 ` Yao Qi
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=1499236932.24598.1.camel@fit.cvut.cz \
--to=jan.vrany@fit.cvut.cz \
--cc=gdb@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