|
62 | 62 | `subprocess.*` directly (or otherwise bypasses `ctx.exec`), wrappers/sharedlibs |
63 | 63 | cannot be injected by this compatibility layer. |
64 | 64 | - **Fetch arguments must be single-valued** in a legacy cartesian campaign. If a fetch |
65 | | - parameter appears in `parameter_space`, it must have exactly one value because |
| 65 | + parameter appears in `variables`, it must have exactly one value because |
66 | 66 | `fetch()` is executed once during `bootstrap()`. |
67 | 67 |
|
68 | 68 | API |
|
81 | 81 | >>> from benchkit.benches.leveldb import LevelDBBench |
82 | 82 | >>> from benchkit.core.compat.new2old import CampaignCartesianProduct |
83 | 83 | >>> |
84 | | - >>> parameter_space = { |
| 84 | + >>> variables = { |
85 | 85 | ... "bench_name": ["readrandom", "seekrandom"], |
86 | 86 | ... "nb_threads": [2, 4, 8], |
87 | 87 | ... } |
88 | 88 | >>> campaign = CampaignCartesianProduct( |
89 | 89 | ... benchmark=LevelDBBench(), |
90 | | - ... parameter_space=parameter_space, |
| 90 | + ... variables=variables, |
91 | 91 | ... nb_runs=1, |
92 | 92 | ... duration_s=5, |
93 | 93 | ... ) |
|
99 | 99 | such as `parent_dir`, `commit`, `patches`, etc. In a legacy cartesian campaign we |
100 | 100 | expect fetch parameters to be fixed (single-valued). Therefore this adapter enforces: |
101 | 101 |
|
102 | | -- If a fetch parameter appears in the provided `parameter_space`, it must have exactly |
| 102 | +- If a fetch parameter appears in the provided `variables`, it must have exactly |
103 | 103 | one value. |
104 | 104 |
|
105 | 105 | If you want to vary fetch parameters, use the new engine directly rather than the |
|
0 commit comments