| Summary: | Add specific WIC tests | ||
|---|---|---|---|
| Product: | [QA/Testing] Runtime Testing | Reporter: | Alexandru Georgescu <alexandru.c.georgescu> |
| Component: | general | Assignee: | Daniel Istrate <daniel.alexandrux.istrate> |
| Status: | RESOLVED FIXED | QA Contact: | Costin <costin.c.constantin> |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | bluelightning, eduard.bartosh |
| Version: | 2.1 | ||
| Target Milestone: | 2.1 M3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
| Bug Depends on: | 8498, 8691 | ||
| Bug Blocks: | |||
|
Description
Alexandru Georgescu
2015-10-13 07:24:41 UTC
These would be oe-selftest testcases what would also run the created image in Qemu. The tests that can be run on the loaded image in Qemu can be specific to the change made when building the image, or a generic test like TestImage to test the overall integrity of the build. At the moment QemuRunner fails to start the wic created image because: - When qemu boots with a disk (like one generated by wic) the kernel parameters are no longer accepted by qemu. One of these parameters is the IP address that QemuRunner requires. - A solution regarding this issue hasn’t been addressed in detail, and requires major changes to the mechanism that handles the qemu machines connectivity and correlation to the running tests (oe-selftest). Would it make sense to create a bug for mentioned QemuRunner issue? Blocking issues added. Added one testcase: http://lists.openembedded.org/pipermail/openembedded-core/2016-February/116637.html just discussed this on bug Triage meeting and decided to close it as adding more tests can slow down AB. It would make sense to test the rest of canned immages when it's possible to run them in parallel. For now we're happy with one we have. |