Skip to content

Added wsl reboot instructions to debugging documentation #5508

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 13, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions docs/community/contributing/debugging.md
Original file line number Diff line number Diff line change
Expand Up @@ -92,6 +92,27 @@ memory=2GB # Limits VM memory in WSL 2 up to 2GB
processors=2 # Makes the WSL 2 VM use two virtual processors
```

#### Rebooting `wsl` With Updated Settings

Once you've made your changes to `.wslconfig` you'll need to reboot your instance for them to take effect.

You can list all of your `wsl` distributions via `wsl -l` or `wsl --list`:

```shell
Windows Subsystem for Linux Distributions:
Ubuntu (Default)
docker-desktop-data
docker-desktop
```

In this case we need to terminate our default `Ubuntu` `wsl` instance:

```shell
wsl --terminate Ubuntu
```

The next time we try to launch `wsl` our `.wslconfig` settings will be active inside the environment.

### Repeating a Test Until It Fails

If you're using JetBrains Rider, you can use their unit test feature to run a test until it fails.
Expand Down