On Sat, 9 Nov 2024 at 08:18, David Gow <davidgow@xxxxxxxxxx> wrote: > On Fri, 8 Nov 2024 at 18:49, Brendan Jackman <jackmanb@xxxxxxxxxx> wrote: > If I remember correctly, this was due to UML sometimes messing up the > terminal (not QEMU, though QEMU definitely does the same thing > sometimes), possibly just when it terminated uncleanly. It may also > have been, as Daniel notes, something to do with the --alltests > option, which used allyesconfig, so could enable some strange > settings. Oh yes I totally forgot about the UML support! UML could definitely be doing terminal ioctls. In a funny coincidence, a totally separate codebase that I'm working on on weekends recently started doing freaky terminal stuff, and now that hangs when run as the child of something like watchexec. So, I guess I'll get back to this kunit.py question once I've debugged that other thing, I bet I'll learn something useful. I guess it's also not worth trying to fix this if we can't be sure the replacement still fixes the problem that `stty sane` was intended to fix, unless the hang turns out to be a problem for CI tooling.
