On Fri, 8 Nov 2024 at 11:49, Brendan Jackman wrote:
> Does anyone know what the 'stty sane' invocation in kunit.py is about?
> At
> the time I believed that it was there to clean up after the firmware
> that QEMU runs potentially messed up the terminal.
Came back to this thread to look this info
On Sat, 9 Nov 2024 at 08:18, David Gow wrote:
> On Fri, 8 Nov 2024 at 18:49, Brendan Jackman 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
On Fri, 8 Nov 2024 at 18:49, Brendan Jackman wrote:
>
> Hi all,
>
> Does anyone know what the 'stty sane' invocation in kunit.py is about?
>
> The other day I ran into an issue when running it via watchexec[1]. At
> the time I believed that it was there to clean up after the firmware
> that QEMU r
(resend, gmail decided to switch to html email :\)
David would know best.
As you probably saw, this was added in 021ed9f551da ("kunit: Run all
KUnit tests through allyesconfig").
This was specifically for running on UML, _not_ QEMU.
I vaguely remember it being along the lines of #1, but not what
Hi all,
Does anyone know what the 'stty sane' invocation in kunit.py is about?
The other day I ran into an issue when running it via watchexec[1]. At
the time I believed that it was there to clean up after the firmware
that QEMU runs potentially messed up the terminal.
However, I just realised I
