search

rapidsai / build-planning

Tracking for RAPIDS-wide build tasks
https://github.com/rapidsai
0 stars 4 forks source link

Enable WSL testing in CI #114

Open vyasr opened 2 hours ago

vyasr commented 2 hours ago

Currently RAPIDS claims support for WSL but only tests this support via ad hoc testing on individual machines. The primary purpose of this testing is to verify that the CUDA driver in WSL2 works properly and handles everything that RAPIDS libraries need. We would like to be able to run these tests in a more systematic manner, ideally in CI. However, there are currently a number of blockers for this. This issue is meant for tracking the various tasks that must be accomplished in order to get CI testing on WSL2.

  1. Windows GPU runners: Currently we have some limited support for Windows runners. We do not have WSL2 support because you cannot do nested virtualization on the EC2 runners. Enabling WSL will require that we transition CI to NVKS. That is currently being handled by @ajschmidt8's team.
  2. WSL2 vs WSL: It looks like currently the Windows VMs that we have support for on our runners are installing WSL. We would like to get these running WSL2. The nested virtualization requirement discussed above is only for WSL2, not WSL1, so we need to address 1 above before we can switch to WSL2 on GPU runners. However, we could update our setup to use WSL2 as long as we are just testing on CPU runners.
  3. We need to figure out how to set up the WSL2 instance so that it is ready to run everything that we need to test RAPIDS libraries, including perhaps installing Docker.
  4. We need scripts to actually run tests. This can be worked on by individual libraries.
vyasr commented 2 hours ago

I may work with @wmaxey on 2/3 as time permits.