Hi, As you can see in the vim build log[0]. There are a lot of 'RunVimInTerminal() failed'. When I run most of the failed tests due to 'RunVimInTerminal() failed' before 'make test', they can pass. I found that 'make test' (i.e. run all tests) could cause the tty "stuck". After finishing a 'make test'. Lets say I have used ttyp0 when I ssh and ttyp1 for a tmux window. I run 'make test' on the shell in ttyp1. Then when I open a new window in tmux using 'Ctrl+b c'. The ttyp2 is allocated, but I cannot see the prompt and I cannot type anything. I can see the cursor on the top left. Then when I create a new window in tmux, it's ttyp3 and ttyp3 can be used without any issue. I haven't found a reliable method to reproduce the circumstance (make test takes some time). I think in this case ttyp2 is frequently used for testing.
[0]: https://buildd.debian.org/status/fetch.php?pkg=vim&arch=hurd-i386&ver=2%3A9.1.0967-2&stamp=1736521254&raw=0 Best, Zhaoming
