New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make sure we're passing the right number of jobs to dune everywhere #162
Comments
in
in
|
The dune documentation still recommends providing
|
That's correct, not sure why the docs recommend it: ocaml/dune#726 |
I now think that if you restrict the number of processes for Opam, this information needs to be passed on to Dune. It does not matter if you want to maximise concurrency. |
Yes I think the point of this is that you can control the number of processes from opam when installing multiple things in parallel. |
Discussion here: https://discuss.ocaml.org/t/opam-and-dune-j-parameter/4299 The interaction of |
There are no packages remaining in xs-extra, for xs the same packages are present |
As the dune manuals says here: https://dune.readthedocs.io/en/latest/usage.html#invocation-from-opam , we should pass the number of jobs from OPAM to dune, both for the build and test instructions:
We don't do this for all of our packages, so we should update our
opam
files where necessary. This will ensure that dune will use the concurrency option provided by opam, and that we can centrally control the number of jobs when buildingxs-opam
by passing the-j
parameter to OPAM - dune uses all the cores by default.The text was updated successfully, but these errors were encountered: