[go: up one dir, main page]

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.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
  • Select suitable reviewers using the Reviewers field below.
  • Select as Assignee the next person who should take action on that MR

Merge request reports

Loading