job is running now, but there is no doubt we need to give it some love and improve flow with timeouts,etc... we'll open different tasks for it and make improvements there.

Had to reboot the slave and take it offline/online in Jenkins to kill the job.

Here's the part of the log where this job went into a loop:

10:30:55 + CLI=lago
10:30:55 + DO_CLEANUP=false
10:30:55 + RECOMMENDED_RAM_IN_MB=8196
10:30:55 + EXTRA_SOURCES=()
10:30:55 ++ getopt -o ho:e:n:b:cs --long help,output:,engine:,node:,boot-iso:,cleanup,extra-rpm-source -n run_suite.sh – -s '"conf:/home/jenkins/workspace/test-repo_ovirt_experimental_4.0/ovirt-system-tests/extra_sources"' basic_suite_4.0
10:30:55 + options=' -s – '\''"conf:/home/jenkins/workspace/test-repo_ovirt_experimental_4.0/ovirt-system-tests/extra_sources"'\'' '\''basic_suite_4.0'\'''
10:30:55 + [[ 0 != \0 ]]
10:30:55 + eval set – ' -s – '\''"conf:/home/jenkins/workspace/test-repo_ovirt_experimental_4.0/ovirt-system-tests/extra_sources"'\'' '\''basic_suite_4.0'\'''
10:30:55 ++ set – -s – '"conf:/home/jenkins/workspace/test-repo_ovirt_experimental_4.0/ovirt-system-tests/extra_sources"' basic_suite_4.0
10:30:55 + true
10:30:55 + case $1 in
10:30:55 + EXTRA_SOURCES+=("$2")
10:30:55 + shift 2
10:30:55 + true
10:30:55 + case $1 in
10:30:55 + true
10:30:55 + case $1 in
10:30:55 + true
10:30:55 + case $1 in
10:30:55 + true

the next run has started, let's see if the issue persists.

There is a link inside the job console which will let you abandon the patch

On Sep 12, 2016 12:01 PM, "Evgheni Dereveanchin (oVirt JIRA)" <