client: fix non-CPU-intensive logic #5483
Merged
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.
Problem: If a project is non-CPU-intensive and has no jobs we ask it for work repeatedly, without backoff.
A project is marked as non-CPU-intensive if
it has no CPU-intensive apps.
This means that a project with no apps
(e.g. because it doesn't have any jobs)
is marked as non-CPU-intensive and pinged without backoff.
Solution: mark a project as non-CPU-intensive only if its scheduler reply says it is
(i.e. there's <non_cpu_intensive/> in its config.xml).