[Notes] [Git][BuildStream/buildstream][tristan/fix-cache-exclusivity] _scheduler/resources.py: Set CACHE max resources to 0

[Tristan Van Berkom <gitlab mg gitlab com>]

Title: GitLab

Tristan Van Berkom pushed to branch tristan/fix-cache-exclusivity at BuildStream / buildstream

Commits:

• 0844cc4f
  by Tristan Van Berkom at 2018-09-03T12:17:54Z

  _scheduler/resources.py: Set CACHE max resources to 0
  
  This means there is no cap for shared resource requests.
  
  Together with the previous commit, this causes the cleanup
  job and the pull/build jobs to all require unlimited shared
  access to the CACHE resource; while only the cleanup job
  requires exclusive access to the resource.
  
  This is a part of #623
  

1 changed file:

• buildstream/_scheduler/resources.py

Changes:

buildstream/_scheduler/resources.py

---

...	...	@@ -8,7 +8,7 @@ class ResourceType():
8	8	class Resources():
9	9	def __init__(self, num_builders, num_fetchers, num_pushers):
10	10	self._max_resources = {
11		- ResourceType.CACHE: 1,
	11	+ ResourceType.CACHE: 0,
12	12	ResourceType.DOWNLOAD: num_fetchers,
13	13	ResourceType.PROCESS: num_builders,
14	14	ResourceType.UPLOAD: num_pushers

—
View it on GitLab.
You're receiving this email because of your account on gitlab.com. If you'd like to receive fewer emails, you can adjust your notification settings.