[x] Maybe a --jobserver BOOL option to allow turning it off if it causes trouble
[x] Maybe --jobserver-slots N to configure the number of slots away from the default of NCPUS
[x] Document
[x] CI job to test it? - It's on by default and should be covered by the default jobs
This seems hard to test; what we really care about is the maximum number of rustc or similar child processes ever spawned at any moment. In principle we could run ps and parse the output, at least on Unix, but in fact this would be slightly racy because it probably doesn't observe the whole process tree, and so the test might be slightly flaky...
Fixes #317
std::process::Command
, since jobserver supports specifically that #376--jobserver BOOL
option to allow turning it off if it causes trouble--jobserver-slots N
to configure the number of slots away from the default of NCPUSCI job to test it?- It's on by default and should be covered by the default jobsThis seems hard to test; what we really care about is the maximum number of
rustc
or similar child processes ever spawned at any moment. In principle we could runps
and parse the output, at least on Unix, but in fact this would be slightly racy because it probably doesn't observe the whole process tree, and so the test might be slightly flaky...