Skip to content
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

Update CI build scripts to not hardcode -j4 #10506

Closed
marek-safar opened this issue Sep 7, 2018 · 3 comments
Labels
Projects

Comments

@marek-safar
Copy link
Member

@marek-safar marek-safar commented Sep 7, 2018

We have been updating our infrastructure but most of our CI script still have hardcoded make -j4 even if we nowadays build on machines like Intel Xeon E5-2667 which can handle more.

We should look into the more future proof handling of this which would scale automatically

@marek-safar marek-safar added the task label Sep 7, 2018
@marek-safar marek-safar added this to Backlog in CI Tasks via automation Sep 7, 2018
@lewurm

This comment has been minimized.

Copy link
Member

@lewurm lewurm commented Sep 12, 2018

how about make -j?

@marek-safar

This comment has been minimized.

Copy link
Member Author

@marek-safar marek-safar commented Sep 12, 2018

I would be worried that it'd make the system unresponsive to the point that to get any crash reports might be too hard

@jaykrell

This comment has been minimized.

Copy link
Collaborator

@jaykrell jaykrell commented Sep 12, 2018

Ancient unsolved global scheduling problem -- maximize system resources.
Don't induce failure (or induce failure and then backoff and retry).
Be responsive to any interactive use that occurs.
Not going be solved soon or nearby. More likely to "farm all work out to cloud".

lewurm added a commit to lewurm/mono that referenced this issue Sep 12, 2018
getconf should work on both, macOS and linux.

Fixes mono#10506
CI Tasks automation moved this from Backlog to Done Sep 12, 2018
luhenry added a commit that referenced this issue Sep 12, 2018
getconf should work on both, macOS and linux.

Fixes #10506
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
3 participants
You can’t perform that action at this time.