@@ -100,37 +100,35 @@ See `README.md` for more information.
100
100
python -m pytest -m "not long_running"
101
101
```
102
102
103
- ### Configurable groups
103
+ ### Configurable tags
104
104
105
- Runners can configure which groups they belong to, and benchmark runs can be
106
- started on whole groups. Unlike when using 'all' or individual runners, runs
107
- for which the result already exists are skipped. For example, a
108
- configuration like:
105
+ Runners can have tags attached, and benchmark runs can be started on
106
+ everything with a specific tag. For example, a configuration like:
109
107
110
108
``` toml
111
109
[runners .linux_clang ]
112
110
os = " linux"
113
111
arch = " x86_64"
114
112
hostname = " pyperf1"
115
113
env.CC = " clang"
116
- groups = [" linux" , " pyperf1" , " clang" ]
114
+ tags = [" linux" , " pyperf1" , " clang" ]
117
115
118
116
[runners .linux_gcc ]
119
117
os = " linux"
120
118
arch = " x86_64"
121
119
hostname = " pyperf1"
122
- groups = [" linux" , " pyperf1" , " gcc" ]
120
+ tags = [" linux" , " pyperf1" , " gcc" ]
123
121
124
122
[runners .linux2_gcc ]
125
123
os = " linux"
126
124
arch = " x86_64"
127
125
hostname = " pyperf2"
128
- groups = [" linux" , " pyperf2" , " gcc" ]
126
+ tags = [" linux" , " pyperf2" , " gcc" ]
129
127
```
130
128
131
- ... will add ` group linux` , ` group pyperf1` , ` group pyperf2` , ` group gcc`
132
- and ` group clang` to the list of possible machines for benchmark runs.
133
- Selecting ` group linux` will queue a run for all three runners, and `group
129
+ ... will add ` tag linux` , ` tag pyperf1` , ` tag pyperf2` , ` tag gcc`
130
+ and ` tag clang` to the list of possible machines for benchmark runs.
131
+ Selecting ` tag linux` will queue a run for all three runners, and `tag
134
132
pyperf1` only for the first two.
135
133
136
134
## v1.8.0
0 commit comments