WSL and WSL2 test runs

[adamsitnik]

#40727 has shown that it's possible to have WSL-specific bugs and that they are important to our customers and us

We have provided a fix (#40851) but it would be great if we could prevent similar issues to reoccur in the future.

@danmosemsft are there any plans to add WSL test runs to our CI?

Tagging subscribers to this area: @ViktorHofer
See info in area-owners.md if you want to be subscribed.

[EgorBo]

there can be also WSL-specific performance issues, e.g. #24839

[danmoseley]

It would be nice to matrix it into the rolling runs somehow. What distro would be most interesting? I assume we need both WSL1 and WSL2 represented?

@jaredpar owns this matrix.

[ViktorHofer]

I wouldn't invest in WSL1. There are multiple test failures with it, because of the kernel not being complete.

[danmoseley]

I wonder whether we would be confident enough to drop tests on distro X (presumably in docker) in favor of X in WSL2.

[ViktorHofer]

AFAIK WSL2 remains to be a development only environment. I think we should always prefer execution environments over development only environments in our testing. Just my 5c.

[danmoseley]

To be a useful development environment the tests need to reliably pass.

[adamsitnik]

WSL2 remains to be a development only environment

this is true, but there are some tools like PowerShell Core that need to work properly in this environment ;)

I think we should always prefer execution environments over development only environments in our testing.

I agree. This is why we should most probably add new CI leg(s) rather that change the existing ones

[iSazonov]

What distro would be most interesting?

You could start with Ubuntu LTS 18/20.

[ViktorHofer]

there can be also WSL-specific performance issues, e.g. #24839

This is WSL1 specific. Do we know if such issues can happen on WSL2 only? Wondering if we need the extra coverage if WSL2 behaves exactly the same as Debian/RedHat/CentOS/etc.