Interesting.

Guess one of our "master" timeout codepath's is not working as expected?

On Mon, Nov 26, 2012 at 11:00 AM, Dave Pigott dave.pigott@linaro.org wrote:

Now that we have to spend less time looking at failed health jobs, we should start looking at stuck jobs:

---

origen02

http://validation.linaro.org/lava-server/scheduler/job/39388

Been running since Nov. 20, 2012, 3:57 a.m.

Submitted its bundle, but just never actually stopped. At the end, it had failed because the Android home screen never displayed, i.e. bootanim never stopped. Don't know if that is relevant or not.

I cancelled the job but, as often happens in these cases, the job ends up in a continually cancelling state. Went onto control and did a kill -2.

---

snowball08

http://validation.linaro.org/lava-server/scheduler/job/39394

Running since Nov. 20, 2012, 4:44 a.m.

Again, failed to get into Android test image and submitted results, but is stuck. Looked on control - no process. Cancelled job. Again, stuck. Did a kill -2.

---

snowball03

http://validation.linaro.org/lava-server/scheduler/job/39894

Running since Nov. 24, 2012, 5:54 p.m.

Same as the others. Failed to get into Android test image, stuck in cancelling. Kill -2.

---

snowball07

http://validation.linaro.org/lava-server/scheduler/job/39940

Running since Nov. 25, 2012, 4:39 a.m.

Same.

---

snowball04

http://validation.linaro.org/lava-server/scheduler/job/39970

Running since Nov. 25, 2012, 8:46 a.m.

Same.

Thanks

Dave

---

linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation