[backend] support memory per job constraint #10008
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## master #10008 +/- ##
=======================================
Coverage 90.53% 90.53%
=======================================
Files 568 568
Lines 21252 21252
=======================================
Hits 19241 19241
Misses 2011 2011 |
mlschroe
requested changes
Aug 13, 2020
To increase the memory need per used job on the worker. This can be potentionally racy, because parallel builds may happened on different times so the need of memory might differ depending on build speed.
adrianschroeter
force-pushed
the
memoryperjob
branch
from
c5ba11a to
ec73240
Compare
|
@adrianschroeter One small note, can you please document the newly added param here: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To increase the memory need per used job on the worker. This can be
potentionally racy, because parallel builds may happened on different
times so the need of memory might differ depending on build speed.