You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docker/README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,15 +6,15 @@ This dockerfile sets up the dependencies required to run consensus-spec tests. T
6
6
7
7
Handy commands:
8
8
-`docker run -it $IMAGE_NAME /bin/sh` will give you a shell inside the docker container to manually run any tests
9
-
-`docker run $IMAGE_NAME make citest` will run the make citest command inside the docker container
9
+
-`docker run $IMAGE_NAME make citest` will run the make citest command inside the docker container
10
10
11
11
Ideally manual running of docker containers is for advanced users, we recommend the script based approach described below for most users.
12
12
13
-
The `scripts/build_run_docker_tests.sh` script will cover most usecases. The script allows the user to configure the fork(altair/bellatrix/capella..), `$IMAGE_NAME` (specifies the container to use), number of cores, preset type (mainnet/minimal), and test all forks flags. Ideally, this is the main way that users interact with the spec tests instead of running it locally with varying versions of dependencies.
13
+
The `scripts/build_run_docker_tests.sh` script will cover most usecases. The script allows the user to configure the fork(altair/bellatrix/capella..), `$IMAGE_NAME` (specifies the container to use), preset type (mainnet/minimal), and test all forks flags. Ideally, this is the main way that users interact with the spec tests instead of running it locally with varying versions of dependencies.
14
14
15
15
E.g:
16
-
-`./build_run_test.sh --p mainnet --n 16` will run the mainnet preset tests with 16 threads
16
+
-`./build_run_test.sh --p mainnet` will run the mainnet preset tests
17
17
-`./build_run_test.sh --a` will run all the tests across all the forks
18
-
-`./build_run_test.sh --f deneb --n 16` will only run deneb tests on 16 threads
18
+
-`./build_run_test.sh --f deneb` will only run deneb tests
19
19
20
20
Results are always placed in a folder called `./testResults`. The results are `.xml` files and contain the fork they represent and the date/time they were run at.
0 commit comments