With taskset -c 3, I run into: ... FAIL: gdb.tui/completion.exp: completion of layout names: quit command input (timeout) FAIL: gdb.tui/completion.exp: completion of focus command: tab completion (timeout) FAIL: gdb.tui/completion.exp: completion of focus command: quit command input (timeout) ... In more detail: ... (gdb) layout PASS: gdb.tui/completion.exp: completion of layout names: tab completion FAIL: gdb.tui/completion.exp: completion of layout names: quit command input (timeout) ^Cfocus^GQuit^M (gdb) ^G^M Display all 197 possibilities? (y or n)FAIL: gdb.tui/completion.exp: completion of focus command: tab completion (timeout) ^CFAIL: gdb.tui/completion.exp: completion of focus command: quit command input (timeout) ...
This was with trunk and a few patch, now also reproduced with pure trunk. Also reproduced with taskset -c 0. Frequency: about once in 10: ... $ for n in $(seq 1 10); do taskset -c 0 ./test.sh 2>&1 | grep "expected passes"; done # of expected passes 5 # of expected passes 5 # of expected passes 5 # of expected passes 5 # of expected passes 3 # of expected passes 5 # of expected passes 5 # of expected passes 5 # of expected passes 5 # of expected passes 5 ...
I think this is a duplicate of PR27813. It's in a TUI test-case, but in the CLI part, so changing component to CLI.
Marking as duplicate. I'm preparing a patch to fix PR 27813 also for readline 7, and if that one gets committed we shouldn't be seeing this FAIL anymore. *** This bug has been marked as a duplicate of bug 27813 ***