ad91a835c0
* update python to 3.12 * drop down to 3.12.4 for compatibility * setup rust toolchain for deps * fix typo * fix linter * fixing linter * adding rust dep * trying to fix circleci * trying to fix circleci * trying to fix circleci * trying to fix circleci * trying to fix circleci * trying to fix circleci * trying to fix circleci * trying to fix circleci * trying to fix circleci * trying to fix circleci * trying to fix circleci * trying to fix circleci * trying to fix circleci * trying to fix circleci * trying to fix circleci * trying to fix circleci * trying new image * trying new image * trying new image * trying new image * invalidate cache * bump reqs * remove cache invalidation * fix cache name * update to use latest image |
||
|---|---|---|
| .. | ||
| Dockerfile | ||
| README.md | ||
README.md
Docker related information
This dockerfile sets up the dependencies required to run consensus-spec tests. The docker image can be locally built with:
docker build ./ -t $IMAGE_NAME -f ./docker/Dockerfile
Handy commands:
docker run -it $IMAGE_NAME /bin/shwill give you a shell inside the docker container to manually run any testsdocker run $IMAGE_NAME make citestwill run the make citest command inside the docker container
Ideally manual running of docker containers is for advanced users, we recommend the script based approach described below for most users.
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.
E.g:
./build_run_test.sh --p mainnetwill run the mainnet preset tests./build_run_test.sh --awill run all the tests across all the forks./build_run_test.sh --f denebwill only run deneb tests
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.