Skip to content

Commit

Permalink
Merge branch 'latest' into net
Browse files Browse the repository at this point in the history
Signed-off-by: Matthieu Baerts (NGI0) <[email protected]>
  • Loading branch information
matttbe committed Apr 4, 2024
2 parents e0d4cef + 4e397b3 commit b83d4cd
Showing 1 changed file with 8 additions and 8 deletions.
16 changes: 8 additions & 8 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
# MPTCP Upstream Virtme Docker

This repo contains files to build a vitual environment with virtme to validate
This repo contains files to build a virtual environment with Virtme to validate
[mptcp_net-next](https://github.com/multipath-tcp/mptcp_net-next) repo.

The idea here is to have automatic builds to published a docker that can be used
by devs and CI.
The idea here is to have automatic builds to publish a docker image that can be
used by devs and CI.

## Entrypoint options

Expand All @@ -13,7 +13,7 @@ When launching the docker image, you have to specify the mode you want to use:
- `manual-normal`: This will compile a kernel without a debug config and leave
you with a shell prompt.
- `manual-debug`: Same but with a kernel debug config.
- `auto-normal`: All the automatic tests are ran in a kernel without a debug
- `auto-normal`: All the automatic tests are run in a kernel without a debug
config.
- `auto-debug`: Same but with a kernel debug config.
- `auto-all`: Same but both non-debug and debug config are used.
Expand Down Expand Up @@ -63,10 +63,10 @@ This will build and start the docker image.
- `.virtme-exec-run`
- `.virtme-exec-post`

`pre` and `post` are ran before and after the tests suite. `run` is ran instead
of the tests suite.
`pre` and `post` are run before and after the tests' suite. `run` is run instead
of the tests' suite.

These scripts are sourced and can used functions from the virtme script.
These scripts are sourced and can use functions from the virtme script.

### Env vars

Expand All @@ -84,7 +84,7 @@ This is useful if you need to do a `git bisect`.
### Not stop after an error is detected with `run_loop`

You can set `INPUT_RUN_LOOP_CONTINUE=1` env var to continue even if an error is
detected. Failed iterations are loggued in `${CONCLUSION}.failed`.
detected. Failed iterations are logged in `${CONCLUSION}.failed`.

#### Packetdrill

Expand Down

0 comments on commit b83d4cd

Please sign in to comment.