Hi Andy and Michael,


We need to enable CTS tests for few of the builds as they are a requirement for few projects. Is there anyone looking at the issue from the lava-dispatcher end since load could be an issue once we enable back CTS.


On 14 November 2012 12:18, YongQin Liu <yongqin.liu@linaro.org> wrote:
Hi, Andy & Michael


About the problem that the telnet process consumes CPU(bug1034218), 
For now I tried two ways to verify it:
1. Run the CTS test via submitting a lava-job
    In this way, the process that consumes CPU is telnet
2. Run the CTS test via command line "lava-android-test run cts"
    In this way, there is no process that consumes CPU to 100%,
    In the meanwhile, I also opened the telnet session.

So I guess the problem is the way we calling the telnet command in lava-dispatcher.
From my investigation, it's the select syscall in telnet that consumes CPU,
So I doubt if there is some place in lava-dispatcher that reads the ouput of telnet in a loop without sleep in the loop.
but I did not find such place in lava-dispatcher.

How do you think about it?

Finally, I feel that this problem is of lava-dispatcher, not the problem of lava-android-test or CTS,
so can we change it to be a bug of lava-dispatcher?

--
Thanks,
Yongqin Liu
---------------------------------------------------------------
#mailing list
linaro-android@lists.linaro.org