On 17 Jul 2012 23:30, "Andy Doan" <andy.doan@linaro.org> wrote:
>
> + android team
>
> This is becoming a big problem. I just checked and the load on the system was growing out of control again.
>
> Upon inspection, I found several Java (CTS) processes that were consuming lots of CPU cycles, but upon inspection there was no ADB connection to the board they were supposed to be testing.
>
> I also found a couple of places where MonkeyRunner seemed to crash, but keep running (and also consume CPU cycles).
>
> In addition the mmtest output is ridiculous. It just dumps %download info throughout our log file making it really hard to read through the logs.
>
> I think we need to do a few things quickly here:
>
> 1) We need to limit the amount of builds sending CTS jobs until we understand what's going on. I'd suggest doing it for something like Origen or Panda since we have the most of those boards. Right now, the jobs are queuing up on snowball faster than it can unsuccessfully execute them
>
> 2) We need to understand what's going on with CTS. Is this due to the patched version we deployed, etc?
I have a suggestion. Should we run CTS on release candidates only?
This is a time consuming test. Do we need to run it on all daily builds?
>
> 3) For sanity sake update the logic for the wgets in mmtest.py to not dump so much junk.
>
> We'll need the android team's help on item 1. I also think we may need their help on item 2.
>
> On 07/16/2012 10:06 PM, Michael Hudson-Doyle wrote:
>>
>> Hi gang,
>>
>> We had a fright today with LAVA being unreachable. Luckily, we could
>> log in again after a time and notice the cause of the load: 10 or so
>> Java processes like this:
>>
>> root 31180 53.2 0.5 8175148 159856 ? Sl Jul16 603:22 java -cp :./android-cts/tools/../../android-cts/tools/ddmlib-prebuilt.jar:./android-cts/tools/../../android-cts/tools/tradefed-prebuilt.jar:./android-cts/tools/../../android-cts/tools/hosttestlib.jar:./android-cts/tools/../../android-cts/tools/cts-tradefed.jar -DCTS_ROOT=./android-cts/tools/../.. com.android.cts.tradefed.command.CtsConsole run cts --serial 192.168.1.199:5555 --plan CTS
>>
>> Clearly, this is related to the CTS upgrades we've done recently. There
>> was no device connected to 192.168.1.199:5555 so somehow we're leaking
>> these processes. I guess we should stop that :-)
>>
>> While looking into this, I noticed that monkeyrunner tests are quite CPU
>> heavy. Is this expected? Do we need to limit how many of these we run
>> at once?
>>
>> Cheers,
>> mwh
>>
>
>
>
> _______________________________________________
> linaro-android mailing list
> linaro-android@lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-android