On Jul 25 19:57, Colin Walters wrote:
On Mon, Jul 25, 2016, at 06:40 PM, Karanbir Singh wrote:
how long was this machine deployed for ? The machine reaper will silently kill power to the node.
Right, but that's 8 hours, correct? I do have a "transparent duffy reuse" tool in https://github.com/cgwalters/centos-ci-skeleton which is used a lot in my jobs, but it generally avoids retaining machines for greater than an hour.
Take https://ci.centos.org/job/atomic-fedora-ws-treecompose/50/console if you click through to https://ci.centos.org/job/atomic-fedora-ws-duffy-allocate/6699/console
At: 22:09:11 Assigning host: n8.pufty.ci.centos.org (SSID=jenkins-atomic-fedora-ws-treecompose-50) Then at this point it hung and I finally aborted it: 22:32:45 Installing packages: 75% 23:53:14 Build was aborted
So that host had only been assigned for less than 30 minutes. Is there anything relevant in the Duffy logs about this?
Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
Can we work together to start one of those jobs and see if it hangs? If so, before aborting the jenkins job we can fail out the node and jump in on a serial console to grab some logs from the machine itself.
--Brian