Terzt/Cloud/Layer1: prepare the artifacts directory and write the configuration file in it
What
Ensures the artifacts directory exists and write the full configuration files.
Why
Useful to redo an experiment with the exact same parameters
How
At the beginning of the experiment:
- Encode the configuration in JSON
- Create the artifact directory
- Write the configuration in
<artifacts_dir>/configuration.json
Manually testing the MR
dune exec tezt/tests/cloud/main.exe -- LAYER1 -v <your usual parameters> --artifacts-dir /tmp/layer1-$(date -Iseconds)
then
dune exec tezt/tests/cloud/main.exe -- LAYER1 -v --config-file /tmp/layer1-<date>/configuration.json --artifacts-dir /tmp/layer1-$(date -Iseconds)
both should run the exact same experiment (don't forget to override artifact-dir, otherwise it will reuse the one in the configuration file, and fail because the directory is not empty).
Checklist
-
Document the interface of any function added or modified (see the coding guidelines) -
Document any change to the user interface, including configuration parameters (see node configuration) -
Provide automatic testing (see the testing guide). -
For new features and bug fixes, add an item in the appropriate changelog ( docs/protocols/alpha.rstfor the protocol and the environment,CHANGES.rstat the root of the repository for everything else). -
Select suitable reviewers using the Reviewersfield below. -
Select as Assigneethe next person who should take action on that MR