Comment 1 for bug 1160247

Looking at the log, it seems that the signal was handled and the cleanup
methods were called. However, the timestamps don't match, so maybe the signal
wasn't handled at all, but then it looks like nothing from the run that failed
was logged, which is also quite weird.

2013-03-25 14:27:06,869 dx-autopilot-nvidia DEBUG: Changing permissions of /tmp/dx-autopilot-nvidia_nhksAu/initrd.d/scripts/init-premount/brltty
2013-03-25 14:27:06,869 dx-autopilot-nvidia DEBUG: Changing permissions of /tmp/dx-autopilot-nvidia_nhksAu/initrd.d/scripts/init-premount/ORDER
2013-03-25 14:27:06,869 dx-autopilot-nvidia DEBUG: Changing permissions of /tmp/dx-autopilot-nvidia_nhksAu/initrd.d/scripts/init-premount/lvm2
2013-03-25 14:27:06,869 dx-autopilot-nvidia DEBUG: Recursively Removing directory /tmp/dx-autopilot-nvidia_nhksAu
2013-03-25 14:27:07,369 dx-autopilot-nvidia DEBUG: Running cleanup
2013-03-26 08:47:47,901 root DEBUG: Logging already configured. Skipping logging configuration.
2013-03-26 08:47:47,976 root DEBUG: Executing SQL statement: SELECT COUNT(*) FROM machines, []
2013-03-26 08:47:47,988 root DEBUG: Executing SQL statement: SELECT * FROM machines WHERE name=?, ['dx-autopilot-nvidia']
2013-03-26 08:47:47,988 root ERROR: Exception: All machines meeting criteria are currently unavailable