From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] Redesign mock environment for gdbarch selftests
Date: Wed, 04 Oct 2017 10:39:00 -0000 [thread overview]
Message-ID: <86y3or5ha8.fsf@gmail.com> (raw)
In-Reply-To: <ef791ec9-a3fd-097d-259d-a507c2eb2bf1@redhat.com> (Pedro Alves's message of "Tue, 3 Oct 2017 13:05:38 +0100")
Pedro Alves <palves@redhat.com> writes:
> OK. I propose we stick with something like I had, and still build
> an isolated inferior/aspace etc. To me, that feels like more robust
I like the way that we can build an isolated inferior/aspace for unit test.
> mocking/isolation. If I run the tests while debugging something
> with the updated patch (below), I get:
>
> (gdb) maint selftest
> Running selftest array_view.
> Running selftest copy_bitwise.
> Running selftest copy_integer_to_size.
> Running selftest current_regcache.
> Running selftest execute_cfa_program.
> Running selftest function_view.
> Running selftest gdb_environ.
> Running selftest gdb_realpath.
> Running selftest memory_error.
> Running selftest offset_type.
> Running selftest optional.
> Running selftest print_one_insn.
> Running selftest producer-parser.
> Running selftest register_to_value.
> Self test failed: arch i386: target already pushed
> Self test failed: arch i386:x86-64: target already pushed
> Self test failed: arch i386:x64-32: target already pushed
> Self test failed: arch i8086: target already pushed
> Self test failed: arch i386:intel: target already pushed
> Self test failed: arch i386:x86-64:intel: target already pushed
> Self test failed: arch i386:x64-32:intel: target already pushed
> Self test failed: arch i386:nacl: target already pushed
> Self test failed: arch i386:x86-64:nacl: target already pushed
> Self test failed: arch i386:x64-32:nacl: target already pushed
> Self test failed: self-test failed at
> /home/pedro/gdb/mygit/src/gdb/selftest-arch.c:86
> Running selftest rust-lex.
> Running selftest scoped_restore.
> Running selftest string_printf.
> Running selftest string_vprintf.
> Running selftest xml_escape_text.
> Ran 19 unit tests, 1 failed
>
> So it ends up being best effort, with most things passing and
> the gdbarch test failing.
>
> WDYT?
That is fine by me. Patch is good to me.
--
Yao (齐尧)
prev parent reply other threads:[~2017-10-04 10:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 15:15 [PATCH 0/3] Fix "Remote 'g' packet reply is too long" problems with multiple inferiors Pedro Alves
2017-10-02 15:15 ` [PATCH 3/3] " Pedro Alves
2017-10-03 11:36 ` Yao Qi
2017-10-03 11:40 ` Yao Qi
2017-10-03 12:21 ` Pedro Alves
2017-10-03 14:02 ` Pedro Alves
2017-10-04 10:21 ` Yao Qi
2017-10-04 17:38 ` Pedro Alves
2017-10-05 16:50 ` Ulrich Weigand
2017-10-05 17:08 ` Pedro Alves
2017-12-12 21:33 ` Maciej W. Rozycki
2017-12-13 0:45 ` Pedro Alves
2017-12-13 11:31 ` Maciej W. Rozycki
2017-10-02 15:15 ` [PATCH 2/3] Reimplement support for "maint print registers" with no running inferior yet Pedro Alves
2017-10-03 11:17 ` Yao Qi
2017-10-02 15:15 ` [PATCH 1/3] Redesign mock environment for gdbarch selftests Pedro Alves
2017-10-03 11:06 ` Yao Qi
2017-10-03 12:05 ` Pedro Alves
2017-10-04 10:39 ` Yao Qi [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=86y3or5ha8.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/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).