Configuration fixed. The problem was job parallelism, not affinity.

Jason, can you fix this in your pending PR?

On Wed, Nov 30, 2016 at 11:57 PM, Kenneth Knowles <k...@google.com.invalid>
wrote:

> It appears that the new job beam_PreCommit_Java_MavenInstall has an
> affinity for Jenkins worker beam3 while workers beam1 and beam2 sit idle.
> Is this intentional? There seems to be a backlog of half a dozen builds.
>

Reply via email to