Hi,
AFAIK, we reverted our experiments to use =eng instead of =test ...
I understand this was done to prevent ICS/JB from slowing down due to hundreds of apps getting registered and displayed in the launcher...
Now, what's the plan on how to get the AOSP tests produced in a way that we can run/use them?
ASAP, I'm on leave today (and I'm sick too) but this is part of my work plan.
On Mon, Aug 6, 2012 at 11:05 AM, Alexander Sack asac@linaro.org wrote:
Hi,
AFAIK, we reverted our experiments to use =eng instead of =test ...
I understand this was done to prevent ICS/JB from slowing down due to hundreds of apps getting registered and displayed in the launcher...
Now, what's the plan on how to get the AOSP tests produced in a way that we can run/use them?
-- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs 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
On 6 August 2012 04:05, Alexander Sack asac@linaro.org wrote:
Hi,
AFAIK, we reverted our experiments to use =eng instead of =test ...
I understand this was done to prevent ICS/JB from slowing down due to hundreds of apps getting registered and displayed in the launcher...
Now, what's the plan on how to get the AOSP tests produced in a way that we can run/use them?
We didn't revert them, we just started building both variants.
The tests in the "tests" target are not really automateable. tests is more like a hacking build where people can run local tests to make sure things work, etc...
The current plan is refocus on providing actually tests to test each interface, but I want to make sure we work in a way that's most useful to our build's users and takes into account our members goals etc...
-- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs 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
On 6 August 2012 13:42, Zach Pfeffer zach.pfeffer@linaro.org wrote:
On 6 August 2012 04:05, Alexander Sack asac@linaro.org wrote:
Hi,
AFAIK, we reverted our experiments to use =eng instead of =test ...
I understand this was done to prevent ICS/JB from slowing down due to hundreds of apps getting registered and displayed in the launcher...
Now, what's the plan on how to get the AOSP tests produced in a way that we can run/use them?
We didn't revert them, we just started building both variants.
Correction, we will start building both.
The tests in the "tests" target are not really automateable. tests is more like a hacking build where people can run local tests to make sure things work, etc...
The current plan is refocus on providing actually tests to test each interface, but I want to make sure we work in a way that's most useful to our build's users and takes into account our members goals etc...
-- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs 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
-- 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@lists.linaro.org
-
Alexander Sack -
Zach Pfeffer -
Zygmunt Krynicki