On 23 March 2012 08:07, Le.chi Thu le.chi.thu@linaro.org wrote:
sorry not include the link to blueprints.
Here they are :
https://blueprints.launchpad.net/lava-scheduler/+spec/manually-health-check https://blueprints.launchpad.net/lava-test/+spec/linaro-validation-ste-kerne... https://blueprints.launchpad.net/lava-scheduler/+spec/health-check-job-vexpr... https://blueprints.launchpad.net/lava-test/+spec/ui-drive-test-for-android
Whatever lands in the Android build should land across all targets at the platform level. The tests should also be integrated into the build so that people can run them manually.
I think the first 3 BPs should be joined by other BPs that track health checks on the remaining targets.
It looks like https://blueprints.launchpad.net/lava-test/+spec/ui-drive-test-for-android can be integrated into the build. We can put together a new git for it. Does:
git://android.git.linaro.org/test/linaro/android/tema.git
sound good?
BR
/Chi Thu
On 23 March 2012 11:56, Fathi Boudra fathi.boudra@linaro.org wrote:
On 23 March 2012 12:51, Alexander Sack asac@linaro.org wrote:
On Thu, Mar 22, 2012 at 10:22:00PM -0500, Paul Larson wrote:
On Thu, Mar 22, 2012 at 9:26 AM, Le.chi Thu le.chi.thu@linaro.org wrote:
Here is the blueprints I would like to work with in next cycle and the highest first
- health-check-job-vexpress (very small task)
- Include STE kernel test suite in LAVA and CI
The above two are good ones, I know the STE kernel suite has some issues to sort out wrt building though.
Do we already have a blueprint with details about inclusion of the STE test suite in the backlog? in particular what is this "building" problem about...
Here's the blueprint: https://blueprints.launchpad.net/lava-test/+spec/linaro-validation-ste-kerne...