Re: [RFA 0/5] some cleanup removal for ui_out

[Simon Marchi <simon.marchi@polymtl.ca>]

On 2017-04-22 11:44, Tom Tromey wrote:
>>>>>> "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

What commit and platform are you able to reproduce it?  I can't 
reproduce, but I'd be interested in looking into it if I manage to do 
it.

Simon