On 30/05/13 09:06 PM, Dev Priya wrote:
Hi,
Yesterday, I did a fresh install of autotest with the latest code in
master. Whenever I am trying to run any of the server-side tests like
netperf2, netpipe etc. they all start and go into running state and then
remain there forever. I waited for hours but they just don't end.
Looking into the INFO file for the job I see that it completed
successfully but the state of the job is still showing as "Running".
Well, this symptom leads me to believe that the scheduler died, or that
there is some bug in the code that keeps track of autoserv instances.
I don't see this behavior for server side sleeptest.
After some research, as embarassing as this might be, there's an open
bug that I couldn't look back then:
https://github.com/autotest/autotest/issues/490
Has someone noticed similar behavior before? Can I get some pointers on
how to fix/debug this?
At least I didn't. I'm assuming it is a bug that wasn't caught before,
I'll work on it this week. As more info is always welcome, it's a good
idea to take a look at the scheduler logs, typically located at
/usr/local/autotest/logs
Log file name format is something like
scheduler.log.2013-04-09-23.38.37
As I'm guessing it is a scheduler problem, the scheduler log file might
have some useful information on why the problem is happening.
Also, it's good to take a careful look at the autoserv log (autoserv.DEBUG).
Cheers,
Lucas
_______________________________________________
Autotest-kernel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/autotest-kernel
