Re: New FAILs on gdb.tui/empty.exp

[Sergio Durigan Junior <sergiodj at redhat dot com>]

On Sunday, August 18 2019, I wrote:

> On Thursday, August 15 2019, Tom Tromey wrote:
>
>> The TUI currently has two different ways to resize a window: the
>> resize method, and the methods make_invisible_and_set_new_height and
>> make_visible_with_new_height.
>>
>> There's no deep reason to have two different ways to resize a window,
>> so this patch unifies them, leaving just the "resize" method.
>>
>> This also changes the locator to be handled more like an ordinary
>> window and less like an adjunct of the associated source window.
>
> Hi Tom,
>
> This commit has introduced new FAILs on gdb.tui/empty.exp:
>
>   PASS -> FAIL: gdb.tui/empty.exp: asm-regs: 80x24: box 1
>   new FAIL: gdb.tui/empty.exp: asm-regs: 90x40: box 1
>   new FAIL: gdb.tui/empty.exp: asm: 90x40: box 1
>   new FAIL: gdb.tui/empty.exp: split-regs: 90x40: box 1
>   PASS -> FAIL: gdb.tui/empty.exp: split: 80x24: box 1
>   new FAIL: gdb.tui/empty.exp: split: 90x40: box 1
>   PASS -> FAIL: gdb.tui/empty.exp: src-regs: 80x24: box 1
>   new FAIL: gdb.tui/empty.exp: src-regs: 90x40: box 1
>   new FAIL: gdb.tui/empty.exp: src: 90x40: box 1
>
> You can see the full Buildbot report here (with links to the logs, as
> usual):
>
>   https://sourceware.org/ml/gdb-testers/2019-q3/msg02696.html
>
> I caught these while release a new Fedora GDB.

I forgot to say, but these seem to be racy; they go from UNRESOLVED to
FAIL and back to UNRESOLVED, apparently.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/