Greedy job scheduler should allow more than one job to run

Open lbradstreet opened this issue 9 years ago • 1 comments

In cases where max-peers is already allocated on all tasks, more than one job should be allowed to run. We received a report that this is not the case.

Apr 13 '16 12:04 lbradstreet

Confirming this bug when there are extra peers after scheduling the first job, the next job does not get any. In this case I was just using n-peers.

Oct 24 '18 11:10 sundbry