Comment 12 for bug 1194533

No, when I give it a timeout, it does timeout, but that doesn't really
solve the problem, it just solves what was scaring me, which was the idea
that the utah client would never time out when running something.

On Sat, Jun 29, 2013 at 12:39 AM, Andy Doan <email address hidden>wrote:

> So just simply giving this thing a timeout makes the whole bug go away?
> Could we simply just give an arbitrarily large value like 24hr and see
> this issue go away?
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1194533
>
> Title:
> utah test is hanging and does not timeout
>
> Status in Ubuntu Test Automation Harness:
> New
>
> Bug description:
> Starting from 20130624, the floodlight server tests on amd64 are
> hanging when run using utah. The test does not appear to timeout
> either. I could not figure out the reason for the hang, but killing
> the utah process completes the jenkins job.
>
> This job has been being impacted by another bug, bug 1181315 but the
> current hang does not appear to be related to this kernel bug.
>
> Please see the run #58 for saucy-server-amd64-smoke-floodlight test in
> the internal instance for the impacted job.
> In
> https://jenkins.qa.ubuntu.com/view/Saucy/view/Smoke%20Testing/job/saucy-server-amd64-smoke-floodlight/56/I had to log into the VM concerned and killed the utah process to make the
> job complete.
>
> The issue does not appear to occur in i386.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/utah/+bug/1194533/+subscriptions
>