You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,10 +64,9 @@ Each runner must have the following labels:
64
64
65
65
Once the runner is set up, [enable it as a service](https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/configuring-the-self-hosted-runner-application-as-a-service) so it will start automatically on boot.
66
66
67
-
In addition, the metadata about the runner must be added to `runners` section in `bench_runner.toml`, for example:
67
+
In addition, the metadata about the runner(s) must be added to `runners` section in `bench_runner.toml`, for example:
68
68
69
69
```toml
70
-
[[runners]]
71
70
[runners.linux]
72
71
os = "linux"
73
72
arch = "x86_64"
@@ -93,7 +92,7 @@ If you don't want a machine to be included when the user selects "machine == 'al
93
92
include_in_all = false
94
93
```
95
94
96
-
You may limit the number of cores used to build Python with the `use_cores` option. This may be necessary, for example, on cloud VMs.
95
+
You may limit the number of cores used to build Python with the `use_cores` option. This may be necessary, for example, on cloud VMs with limited RAM.
0 commit comments