On 16 February 2011 06:24, Paul Larson wrote:
>
>
> On Wed, Feb 16, 2011 at 8:16 AM, Zygmunt Krynicki <
> zygmunt.kryni...@linaro.org> wrote:
>
>>
>> Yeah, when you mentioned this now I started thinking. Do we really need a
>> daemon-like component for the dispatcher in general or just in the far
On 16 February 2011 06:10, Paul Larson wrote:
>
>
>
>> Another crazy option would be to expose LAVA Job Dispatcher directly and
>>> allow people to run jobs. In this case one job would use abrek and some
>>> other tools to invoke tests, process results and send them to the dashboard
>>> while oth
On Wed, Feb 16, 2011 at 8:16 AM, Zygmunt Krynicki <
zygmunt.kryni...@linaro.org> wrote:
>
> Yeah, when you mentioned this now I started thinking. Do we really need a
> daemon-like component for the dispatcher in general or just in the farm
> environment. Can we assume that having the implementatio
W dniu 16.02.2011 15:10, Paul Larson pisze:
Another crazy option would be to expose LAVA Job Dispatcher
directly and allow people to run jobs. In this case one job
I hope you don't really think this is a crazy idea, because it's
*exactly* what we discussed doing, and I think i
> Another crazy option would be to expose LAVA Job Dispatcher directly and
>> allow people to run jobs. In this case one job would use abrek and some
>> other tools to invoke tests, process results and send them to the dashboard
>> while other job (one for android) would not run abrek at all, inste
On 16 February 2011 05:27, Zygmunt Krynicki wrote:
> W dniu 16.02.2011 11:22, Mirsad Vojnikovic pisze:
>
>
>
> Zygmunt has already identified key points for Job Dispatcher to support
>> this, but one thing I would like to comment:
>>
>>Another crazy option would be to expose LAVA Job Dispatch
W dniu 16.02.2011 11:22, Mirsad Vojnikovic pisze:
Zygmunt has already identified key points for Job Dispatcher to support
this, but one thing I would like to comment:
Another crazy option would be to expose LAVA Job Dispatcher directly
and allow people to run jobs. In this case one job
2011/2/16 Mirsad Vojnikovic :
> Hi all!
>
hi Mirsad,
> This is very good analysis you have done, and I would just add that Monkey
> is only one simpler example where the test execution using abrek is not an
> option.
True.
> Another example from Android world is CTS:
> http://source.android.com
Hi all!
This is very good analysis you have done, and I would just add that Monkey
is only one simpler example where the test execution using abrek is not an
option. Another example from Android world is CTS:
http://source.android.com/compatibility/cts-intro.html. Most certainly, all
test suites a
W dniu 16.02.2011 10:28, Jeremy Chang pisze:
Jeremy, could you prepare the testing environment using Android emulator?
We could write down the instructions in wiki for reference.
Emulator is a good start. I created a page for reference, introducing
Android emulator based testing environment.
as
[omit..]
>>> ** Show me the use case
>>> The attached patch is just trivial proof-of concept implementation
>>> done by Jeremy Chang that adds a 'monkey'
>>> test definition file for abrek. Once TCP/IP or USB is ready, for
>>> Android's monkey testing, the procedure is like
>>> as following:
>>> (
2011/2/16 Zygmunt Krynicki :
> W dniu 15.02.2011 21:01, Jim Huang pisze:
>
> Hi Jim, great work!
hi Zygmunt,
Thanks. It is my pleasure to work with Linaro validation team.
>> ** Why can't we execute LAVA/Abrek directly on Android devices?
> I agree that direct abrek is not the right solution fo
W dniu 15.02.2011 21:01, Jim Huang pisze:
Hi Jim, great work!
** Why can't we execute LAVA/Abrek directly on Android devices?
I agree that direct abrek is not the right solution for Android. I think
there is a class of use cases that also falls into this category:
* testing early silicon
Hello list,
Regarding integration of LAVA [1] architecture with Android devices,
we would like to reuse the existing
infrastructure and framework design. Abrek [2] is a great testsuite
framework for running test cases and
benchmarks. However, due to the restrictions of unusual Android
runtime, w
14 matches
Mail list logo
