| Summary: | QA Tests: Add recipe for ltp/posix tests and automate test | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Richard Purdie <richard.purdie> |
| Component: | meta-yocto | Assignee: | Jiajun Xu <jiajun.xu> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | CC: | jessica.zhang, jiajun.xu, poky.bs.watcher, poky.watcher |
| Version: | unspecified | ||
| Target Milestone: | 1.2 M1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | (P2)(No QA needed) Done | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Richard Purdie
2011-10-03 07:58:12 UTC
Posix is maintained as one sub-test in LTP now. So let us add recipe for LTP and automate them. Change the owner to me and I plan to finish it in 1.2 M1. What I want to implement for LTP/POSIX automation is like following: 1. Port LTP recipe from OE-core and use latest stable version, binaries installed into /opt/ltp. 2. Provide a script to run QA customized test list for LTP/POSIX 3. Extend task-core-tools-testapps in task-core-tools.bb, add LTP into RDEPENS of "task-core-tools-testapps" 4. LTP/POXIS tests will be built into core-image-sato-sdk by default Richard, Saul, Could you help to review if my thinking is OK and sign off the design? Thanks a lot. LTP/POSIX is in poky upstream now, as commit 2d1a411dc4f50d149e623cfb2b40b4fab7877b96, 1a260d0d3a8ae9b93ae249a5e097dedd924c371f and 7a708b17754486e61d9971d762e8d8fa768cc799. The feature is finished with following patches in poky tree: 2d1a411dc4f50d149e623cfb2b40b4fab7877b96, "ltp: Add recipe from OE" 1a260d0d3a8ae9b93ae249a5e097dedd924c371f, "distro_tracking_fields: add information for ltp" 7a708b17754486e61d9971d762e8d8fa768cc799, "task-core-tools: add ltp to testapps list" |