> **Note** This guide will use `$DATA_DIR` as a shortcut for where your data (bin-envs, data-envs, results) will reside. A config file will be available shortly
> **Note** This guide will use `$DATA_DIR` as a shortcut for where your data
> (bin-envs, data-envs, results) will reside. A config file will be available
> shortly
Creating a bin-env
==================
You can use `poulpe bin-env-util` to create and query binary environments.
...
...
@@ -21,10 +23,13 @@
Creating a bin-env
==================
You can use `poulpe bin-env-util` to create and query binary environments.
The `setup-one` command will run a script that takes care of setting up the environment. There is currently only one script in this repository (which sets up a Mercurial repository), feel free to adapt and create your own.
The `setup-one` command will run a script that takes care of setting up the
environment. There is currently only one script in this repository (which sets
up a Mercurial repository), feel free to adapt and create your own.
creating new file: "$DATA_DIR/data-envs/my-repo-dirstate-v2/data-env.poulpe"
...
...
@@ -97,9 +109,11 @@
Running a benchmark
===================
You can use `poulpe run-util` to run a benchmark. There are many benchmarks in `suites/hg/benchmarks` that are specific to benchmarking Mercurial. Feel free to create your own.
You can use `poulpe run-util` to run a benchmark. There are many benchmarks in
`suites/hg/benchmarks` that are specific to benchmarking Mercurial. Feel free