"Unfortunately, last time I tried to write tests for Unix sockets, I started triggering kernel panics in Windows." It seems like a Windows specific issue! A kernel panic should never occur, even when provided with invalid data.
Well... yes? I'm not sure what your point is.
I think it's best to ignore Windows <-> Unix communications tests for now as I don't think `winetest` allow running tests in both Windows and Unix space at the same time, that would require `winetest` supporting `wsl` when testing on Windows10+, and I think `wsl` support is out of scope of this PR.
I'm not requesting tests for host interop here, and while I don't think it's a bad idea (for some measure of stability) we don't have the infrastructure to do those kinds of tests.
-
Zebediah Figura (＠zfigura)