tag:help.appveyor.com,2012-11-13:/discussions/problems/27410-byoc-pathology-in-evenly-group-scheduling-of-jobsAppVeyor: Discussion 2020-05-26T19:00:34Ztag:help.appveyor.com,2012-11-13:Comment/483625612020-05-26T19:00:33Z2020-05-26T19:00:33ZBYOC: Pathology in "evenly" group scheduling of jobs<div><p>Hi,</p>
<p>I've noticed that when a job gets canceled because of a newer commit, the new job gets scheduled before the old one gets canceled.<br>
This leads to the following pathology with "evenly" with distribution strategy;<br>
one job is running on "cloud A" one job is running on "cloud B"</p>
<p>a new commit creates a new job, it gets scheduled on "cloud A", however the commit forces cancellation the job on "clout B".<br>
The result is 2 jobs on "cloud A" and 0 jobs on "cloud B".<br>
There's 50:50 chance of this happening with 2 clouds.<br>
However, if the cancelled jobs were removed before the new one is scheduled it should always schedule the job on the idle cloud.</p></div>Jan Vesely