Ensure kernel ci testing works on mx53 boards

Registered by Paul Larson

Enable kernel ci testing on mx53 boards

Blueprint information

Status:
Complete
Approver:
Paul Larson
Priority:
High
Drafter:
Paul Larson
Direction:
Approved
Assignee:
Spring Zhang
Definition:
Approved
Series goal:
Accepted for trunk
Implementation:
Implemented
Milestone target:
milestone icon 2011.12
Started by
Spring Zhang
Completed by
Spring Zhang

Related branches

Sprints

Whiteboard

[pwlars, 2011-10-25] If bugs are found, please file them and link them to the blueprint, might have to delay actually enabling the runs if hardware is too constrained
[fboudra, 2011-11-18] re-target to 2011.12.
[qzhang, 2011-12-07] Enabled in mx53 CI job in https://ci.linaro.org/jenkins/view/Ubuntu%20CI%20-%20FSLLT/, see if it works the next day.
[qzhang, 2011-12-08] One result is on http://validation.linaro.org/lava-server/dashboard/streams/anonymous/ci-packaged-linux-linaro-lt-3_1/bundles/4ae1e4385ed313a53a20e657ccb1794eb9904e31/, but it failed on lava-install-test.
[qzhang, 2011-12-09] #action springz, mwhudson to make sure mx53 ci results are displayed on kernel ci page
[qzhang, 2011-12-09] kernel CI page accepts input from ci-linux-*-build, the mx53 CI job result goes to ci-packaged-linux-...-build, so it's not collected. Need a discussion to decide cloning a new job to ci-linux-*-build or just change the existing result to ci-linux-*-build.
[qzhang, 2011-12-14] One CI task is on https://ci.linaro.org/jenkins/view/Ubuntu%20CI%20-%20FSLLT/, linux-linaro-3.1_lt-mx53loco, also result displayed on kernel CI view with an ugly config name "packaged_kernel_config".
[qzhang, 2011-12-15] File a bug: #904808, the platform can't show on kernel-ci-view, and I'll continue to tune the CI job.

Meta:
Headline: LAVA now runs kernel continuous integration testing on i.MX53 boards.
Acceptance: LAVA/Kernel CI loop runs tests on i.MX53 boards and result displayed on kernel CI view
Roadmap id: LAVA2011-KERNEL-CI

(?)

Work Items

Work items:
Test local deployment with i.MX53 using the dispatcher: DONE
Add i.MX53 testing to kernel ci loop: DONE
Make sure CI result displayed on validation.l.o: DONE

This blueprint contains Public information 
Everyone can see this information.