Skip to content

Clarify why and how to start second session for tests #14566

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.

Sign up for GitHub

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
Jun 9, 2025
Merged

Clarify why and how to start second session for tests #14566

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 3 additions & 1 deletion lib/elixir/pages/mix-and-otp/distributed-tasks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,6 +124,7 @@ Distributed tasks are exactly the same as supervised tasks. The only difference
Now, let's start two named nodes again, but inside the `:kv` application:

```console
$ cd apps/kv
$ iex --sname foo -S mix
$ iex --sname bar -S mix
```
Expand Down Expand Up @@ -231,9 +232,10 @@ The first test invokes `Kernel.node/0`, which returns the name of the current no

The second test checks that the code raises for unknown entries.

In order to run the first test, we need to have two nodes running. Move into `apps/kv` and let's restart the node named `bar` which is going to be used by tests.
In order to run the first test, we need to have two nodes running. Let's move into `apps/kv` and restart the node named `bar` which is going to be used by tests. This way, `bar` will not load the `:kv_server` app and leave the port available for `foo` and tests.

```console
$ cd apps/kv
$ iex --sname bar -S mix
```

Expand Down