Added the list.
We have a manual test for this, that should be automatable. See:
https://wiki.linaro.org/Platform/QA/TestCases/Android
Actually any of those that you can automate would be good.
On 21 March 2012 06:33, Le.chi Thu le.chi.thu@linaro.org wrote:
Hi Zach,
Do you know who can help me on this ? linaro-android@linaro.org does not exist.
BR
/Chi Thu
---------- Forwarded message ---------- From: Le.chi Thu le.chi.thu@linaro.org Date: 21 March 2012 12:29 Subject: add gator test to lava test plan To: linaro-android linaro-android@linaro.org Cc: Paul Sokolovsky paul.sokolovsky@linaro.org, YongQin Liu yongqin.liu@linaro.org
Hi
Can you please add gator test for lava test plan for android builds ?
See the chat below.
BR
/Chi Thu
<ChiThu> pfalcon, are you take care of the lava test plan for android builds ? <pfalcon> ChiThu: Hi, nope, liuyq does ;-) <ChiThu> liuyq, ping <liuyq> ChiThu, pong <liuyq> ChiThu, this not need to modify post-build-lava.py, you can ask the android team member to modify LAVA_TEST_PLAN to include it at android-build page <liuyq> ChiThu, like modify to LAVA_TEST_PLAN="gatortest,busybox,0xbench,glmark2,skia,v8,mmtest,cts,monkey" <liuyq> ChiThu, I don't have the permission to modify Official builds parameters too. <ChiThu> pfalcon, can you help to modify to LAVA_TEST_PLAN="gatortest,busybox,0xbench,glmark2,skia,v8,mmtest,cts,monkey" ? <pfalcon> ChiThu, liuyq: easiest way would be probably to send message to linaro-android@ asking folks to update it <pfalcon> ChiThu: I can't do that easily either, would require some work. IMHO, would be better to ask Android folks to do that, so they were in loop on what's happening
Hi.
I think an automated test for gator should:
1. Use adb to verify that the daemon gatord is running. Gatord will not start if it is unhappy with the kernel module, so this is a confirmation of that the stuff is at least running. just do a ps and grep for gatord. 2) (ambitious) Connect to gatord using the default port and ask e.g. about version. There are python scripts for connecting in DS-5 CE that can be cannibalized if ARM approves license-wise. 3) (Highest ambition) capture something. If you get data you are fine.
AFAIU it's all very Python-friendly.
On 22 March 2012 04:28, Zach Pfeffer zach.pfeffer@linaro.org wrote:
Added the list.
We have a manual test for this, that should be automatable. See:
https://wiki.linaro.org/Platform/QA/TestCases/Android
Actually any of those that you can automate would be good.
On 21 March 2012 06:33, Le.chi Thu le.chi.thu@linaro.org wrote:
Hi Zach,
Do you know who can help me on this ? linaro-android@linaro.org does
not exist.
BR
/Chi Thu
---------- Forwarded message ---------- From: Le.chi Thu le.chi.thu@linaro.org Date: 21 March 2012 12:29 Subject: add gator test to lava test plan To: linaro-android linaro-android@linaro.org Cc: Paul Sokolovsky paul.sokolovsky@linaro.org, YongQin Liu yongqin.liu@linaro.org
Hi
Can you please add gator test for lava test plan for android builds ?
See the chat below.
BR
/Chi Thu
<ChiThu> pfalcon, are you take care of the lava test plan for android
builds ?
<pfalcon> ChiThu: Hi, nope, liuyq does ;-) <ChiThu> liuyq, ping <liuyq> ChiThu, pong <liuyq> ChiThu, this not need to modify post-build-lava.py, you can ask the android team member to modify LAVA_TEST_PLAN to include it at android-build page <liuyq> ChiThu, like modify to
LAVA_TEST_PLAN="gatortest,busybox,0xbench,glmark2,skia,v8,mmtest,cts,monkey"
<liuyq> ChiThu, I don't have the permission to modify Official builds parameters too. <ChiThu> pfalcon, can you help to modify to
LAVA_TEST_PLAN="gatortest,busybox,0xbench,glmark2,skia,v8,mmtest,cts,monkey"
? <pfalcon> ChiThu, liuyq: easiest way would be probably to send message to linaro-android@ asking folks to update it <pfalcon> ChiThu: I can't do that easily either, would require some work. IMHO, would be better to ask Android folks to do that, so they were in loop on what's happening
-- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
Hi
The gator test which is done by David Stubb in ARM is already included in the lava-android-test. The test that the point 1 as Tonys list. That is verify the gator daemon is running.
David.Stubbs: What about the implement the point 2 & 3 ?
BR
/Chi Thu
On 22 March 2012 13:08, Tony Mansson tony.mansson@linaro.org wrote:
Hi.
I think an automated test for gator should:
- Use adb to verify that the daemon gatord is running. Gatord will not
start if it is unhappy with the kernel module, so this is a confirmation of that the stuff is at least running. just do a ps and grep for gatord. 2) (ambitious) Connect to gatord using the default port and ask e.g. about version. There are python scripts for connecting in DS-5 CE that can be cannibalized if ARM approves license-wise. 3) (Highest ambition) capture something. If you get data you are fine.
AFAIU it's all very Python-friendly.
On 22 March 2012 04:28, Zach Pfeffer zach.pfeffer@linaro.org wrote:
Added the list.
We have a manual test for this, that should be automatable. See:
https://wiki.linaro.org/Platform/QA/TestCases/Android
Actually any of those that you can automate would be good.
On 21 March 2012 06:33, Le.chi Thu le.chi.thu@linaro.org wrote:
Hi Zach,
Do you know who can help me on this ? linaro-android@linaro.org does not exist.
BR
/Chi Thu
---------- Forwarded message ---------- From: Le.chi Thu le.chi.thu@linaro.org Date: 21 March 2012 12:29 Subject: add gator test to lava test plan To: linaro-android linaro-android@linaro.org Cc: Paul Sokolovsky paul.sokolovsky@linaro.org, YongQin Liu yongqin.liu@linaro.org
Hi
Can you please add gator test for lava test plan for android builds ?
See the chat below.
BR
/Chi Thu
<ChiThu> pfalcon, are you take care of the lava test plan for android builds ? <pfalcon> ChiThu: Hi, nope, liuyq does ;-) <ChiThu> liuyq, ping <liuyq> ChiThu, pong <liuyq> ChiThu, this not need to modify post-build-lava.py, you can ask the android team member to modify LAVA_TEST_PLAN to include it at android-build page <liuyq> ChiThu, like modify to
LAVA_TEST_PLAN="gatortest,busybox,0xbench,glmark2,skia,v8,mmtest,cts,monkey" <liuyq> ChiThu, I don't have the permission to modify Official builds parameters too. <ChiThu> pfalcon, can you help to modify to
LAVA_TEST_PLAN="gatortest,busybox,0xbench,glmark2,skia,v8,mmtest,cts,monkey" ? <pfalcon> ChiThu, liuyq: easiest way would be probably to send message to linaro-android@ asking folks to update it <pfalcon> ChiThu: I can't do that easily either, would require some work. IMHO, would be better to ask Android folks to do that, so they were in loop on what's happening
-- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
Hi,
I am planning to implement 2 and 3 over the next sprint - hopefully on both Linux and Android.
I will also have to make a small change to the current android test relating to a change in which it is launched:
https://bugs.launchpad.net/bugs/942592
Regards,
Dave.
-----Original Message----- From: Le.chi Thu [mailto:le.chi.thu@linaro.org] Sent: 22 March 2012 13:20 To: Tony Mansson; David Stubbs (SDVL) Cc: Zach Pfeffer; linaro-android; Paul Larson Subject: Re: add gator test to lava test plan
Hi
The gator test which is done by David Stubb in ARM is already included in the lava-android-test. The test that the point 1 as Tonys list. That is verify the gator daemon is running.
David.Stubbs: What about the implement the point 2 & 3 ?
BR
/Chi Thu
On 22 March 2012 13:08, Tony Mansson tony.mansson@linaro.org wrote:
Hi.
I think an automated test for gator should:
- Use adb to verify that the daemon gatord is running. Gatord will not
start if it is unhappy with the kernel module, so this is a confirmation of that the stuff is at least running. just do a ps and grep for gatord. 2) (ambitious) Connect to gatord using the default port and ask e.g. about version. There are python scripts for connecting in DS-5 CE that can be cannibalized if ARM approves license-wise. 3) (Highest ambition) capture something. If you get data you are fine.
AFAIU it's all very Python-friendly.
On 22 March 2012 04:28, Zach Pfeffer zach.pfeffer@linaro.org wrote:
Added the list.
We have a manual test for this, that should be automatable. See:
https://wiki.linaro.org/Platform/QA/TestCases/Android
Actually any of those that you can automate would be good.
On 21 March 2012 06:33, Le.chi Thu le.chi.thu@linaro.org wrote:
Hi Zach,
Do you know who can help me on this ? linaro-android@linaro.org does not exist.
BR
/Chi Thu
---------- Forwarded message ---------- From: Le.chi Thu le.chi.thu@linaro.org Date: 21 March 2012 12:29 Subject: add gator test to lava test plan To: linaro-android linaro-android@linaro.org Cc: Paul Sokolovsky paul.sokolovsky@linaro.org, YongQin Liu yongqin.liu@linaro.org
Hi
Can you please add gator test for lava test plan for android builds ?
See the chat below.
BR
/Chi Thu
<ChiThu> pfalcon, are you take care of the lava test plan for android builds ? <pfalcon> ChiThu: Hi, nope, liuyq does ;-) <ChiThu> liuyq, ping <liuyq> ChiThu, pong <liuyq> ChiThu, this not need to modify post-build-lava.py, you can ask the android team member to modify LAVA_TEST_PLAN to include it at android-build page <liuyq> ChiThu, like modify to
LAVA_TEST_PLAN="gatortest,busybox,0xbench,glmark2,skia,v8,mmtest,cts,monkey" <liuyq> ChiThu, I don't have the permission to modify Official builds parameters too. <ChiThu> pfalcon, can you help to modify to
LAVA_TEST_PLAN="gatortest,busybox,0xbench,glmark2,skia,v8,mmtest,cts,monkey" ? <pfalcon> ChiThu, liuyq: easiest way would be probably to send message to linaro-android@ asking folks to update it <pfalcon> ChiThu: I can't do that easily either, would require some work. IMHO, would be better to ask Android folks to do that, so they were in loop on what's happening
-- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hello David:
On 22 March 2012 09:42, David Stubbs (SDVL) David.Stubbs2@arm.com wrote:
Hi,
I am planning to implement 2 and 3 over the next sprint - hopefully on both Linux and Android.
That would be great. Any idea when is the next sprint is?
anmar
On Wed, 2012-03-21 at 22:28 -0500, Zach Pfeffer wrote:
Added the list.
We have a manual test for this, that should be automatable. See:
https://wiki.linaro.org/Platform/QA/TestCases/Android
Actually any of those that you can automate would be good.
There might already be some automated tests that can be borrowed/hacked. I will enquire if that is true...
On Thu, 2012-03-22 at 12:34 +0000, Jon Medhurst (Tixy) wrote:
On Wed, 2012-03-21 at 22:28 -0500, Zach Pfeffer wrote:
Added the list.
We have a manual test for this, that should be automatable. See:
https://wiki.linaro.org/Platform/QA/TestCases/Android
Actually any of those that you can automate would be good.
There might already be some automated tests that can be borrowed/hacked. I will enquire if that is true...
I beleive the tests I was thinking of are those being done by David Stubb as mentioned in another part of this thread.
linaro-android@lists.linaro.org