#789 backend: implement max_build_count_per_vm option
Closed: Fixed 3 years ago by praiskup. Opened 4 years ago by praiskup.

This used to be planed, but never implemented - so I removed that option from config by e22863e.

This would very useful for temporary work-arounds at least; if there are some known resource leaks on builders. E.g. now I triggered one build in @python/python3.8 (requested hundreds of builds on one builder) -- and I suppose I caused the failure by enabling yum caches on builders: https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=9988126185fb4152a18f83bcd7b8a5e551830720


Just to confirm that the guess was right:

[root@copr-builder-937456795 mock]# pwd
/var/cache/mock
[root@copr-builder-937456795 mock]# du --max-depth=0 . -h
11G     .

This is only counting root cache tarballs; that bulder has builds_count: 208 so far.

This is now available in resalloc pools.yaml configuration.

Metadata Update from @praiskup:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata