check-patch jobs are running on integ-tests machines

Description

Hey,
I've noticed that all of the 'integ-tests' machines are busy with running check-patch for various projects. This causes jobs that actually require bare metal slaves to wait for more then 15 minutes in the queue.
Can you please change the configuration so that only jobs that specfically requests to run on those slaves will have them, and the rest just use the vm slaves?

Activity

Show:

Former user March 1, 2017 at 2:47 PM

el7/fc24 label can be removed as they are used by various jobs that can all run in VMs.

Former user March 1, 2017 at 2:37 PM

All x86_64 VM slaves now have the "Use this slave as much as possible" policy set. ppc64le VMs and bare metals on the other hand run just labeled jobs.

Former user March 1, 2017 at 2:24 PM

On the other side - we've got a bunch of el7 VM slaves all having the "Only build jobs with label expressions matching this node" so they are currently idle while they could be running check-patch jobs (after double-checking this job does not attach to a label). Will change this setting on VMs to get the queue processed faster.

Former user March 1, 2017 at 2:18 PM
Edited

I haven't changed the labels, only the setting to only build jobs with label expressions matching the slaves label.
should we just leave the 'integ-tests' label for those slaves?

Fixed

Details

Assignee

Reporter

Priority

Created March 1, 2017 at 10:44 AM
Updated April 2, 2017 at 12:51 PM
Resolved March 1, 2017 at 1:45 PM

Flag notifications