[ https://issues.jboss.org/browse/JBIDE-22630?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22630: ------------------------------------ Jobs are configured to run on the following slaves/labels: jiralint-bzira: (RHEL6||RHEL7||beaker||jboss-prod)&&!ia64&&!ppc64&&!rhts jiralint-daily: (RHEL6||RHEL7||beaker||jboss-prod)&&!ia64&&!ppc64&&!rhts jiralint-weekly: (RHEL6||RHEL7||beaker||jboss-prod)&&!ia64&&!ppc64&&!rhts I would need to see the console log from a job which failed in order to be able to remove it from the slave pool used. Re-reading your JIRA report, I see you mention that the snippet is from an email. These appear to be the slaves which are missing pip. {code} dev218-virt4 (RHEL-any mem2G RHEL7 linux general eap-sustaining docker EAP-RHEL7 mwqa_drives_services RHEL beaker mwqa_drives_tools mem4G unix) dev148-virt2 (eap-sustaining docker EAP-RHEL7 mwqa_drives_services mem2G beaker mwqa_drives_tools mem4G) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)