From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA 0/5] some cleanup removal for ui_out
Date: Sat, 22 Apr 2017 15:44:00 -0000 [thread overview]
Message-ID: <87inlw4fbl.fsf@tromey.com> (raw)
In-Reply-To: <20170414022337.28368-1-tom@tromey.com> (Tom Tromey's message of "Thu, 13 Apr 2017 20:23:32 -0600")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> This series converts various (easy) spots to use ui_out_emit_list or
Tom> ui_out_emit_tuple. This removes a number of cleanups.
I am finally going to check this in.
I hadn't done so earlier because my buildbot runs were occasionally
showing some failures. However, a recent run with a completely
different patch shows the same failures, so I'm going forward on the
theory that these patches of mine aren't causing the problem.
The failures I'm seeing are from gdb.mi/user-selected-context-sync.exp,
though exactly which failures are seen varies by run.
PASS -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_frame: thread 1.2: reset selection to thread 1.2
PASS -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_select_frame: thread 1.2: reset selection to thread 1.2
PASS -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_up_down: reset selection to thread 1.2
PASS -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_mi_stack_select_frame: thread 1.2: reset selection to thread 1.2
PASS -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=direct: test_cli_in_mi_frame: thread 1.2: reset selection to thread 1.2
PASS -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=interpreter-exec: test_cli_in_mi_frame: thread 1.2: reset selection to thread 1.2
Tom
next prev parent reply other threads:[~2017-04-22 15:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 2:23 Tom Tromey
2017-04-14 2:23 ` [RFA 3/5] Use ui_out_emit_tuple in tracepoint.c Tom Tromey
2017-04-18 18:43 ` Pedro Alves
2017-04-14 2:23 ` [RFA 5/5] Use ui_out_emit_list Tom Tromey
2017-04-18 18:44 ` Pedro Alves
2017-04-14 2:23 ` [RFA 2/5] More uses of ui_out_emit_tuple Tom Tromey
2017-04-18 18:42 ` Pedro Alves
2017-04-19 2:42 ` Tom Tromey
2017-04-19 9:39 ` Pedro Alves
2017-04-14 2:24 ` [RFA 1/5] Use ui_out_emit_tuple Tom Tromey
2017-04-18 18:42 ` Pedro Alves
2017-04-14 2:42 ` [RFA 4/5] Use ui_out_emit_tuple in more places in MI Tom Tromey
2017-04-18 18:44 ` Pedro Alves
2017-04-22 15:44 ` Tom Tromey [this message]
2017-04-27 14:51 ` [RFA 0/5] some cleanup removal for ui_out Simon Marchi
2017-04-27 21:23 ` Tom Tromey
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=87inlw4fbl.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@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