[rl3]

>In these cases, the WSL team covers test gaps by writing our own unit tests. At time of writing the team has written over 150,000 lines of unit test code for systems calls and virtual files (/proc, /sys).

I wonder why they went that route instead of contributing to LTP directly?

While there's probably some edge cases specific to WSL, surely much of their increased unit test coverage would be applicable beyond WSL.

[jackhammons]

We maintain a fork of LTP internally. Eventually we hope to contribute our changes back but unfortunately open sourcing isn't free and we have bigger fish to fry[1].

[1] https://wpdev.uservoice.com/forums/266908-command-prompt-con...

[rl3]

That's understandable. Thanks for the reply.

Out of curiosity, is progress on WSL bound by any blocking issues in particular, or could your team benefit from more resources being assigned to the project?

Maybe I'm naïve, but I tend to view WSL as a perfect way to win over a ton of developers who are becoming disillusioned with macOS, but are hesitant to run bare metal Linux due to the headaches involved (insofar that macOS and Windows "just work").