| Summary: | [QA/Test] Add a perl-test recipe to test perl | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Robert Yang <liezhi.yang> |
| Component: | devtools / tool chain | Assignee: | Kai Kang <kai.kang> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | bjst, corneliux.stoicescu, jessica.zhang, liang.li2, liezhi.yang, mark.hatle, meta.mr.watcher, meta.watcher, richard.purdie, sgw, zhenfeng.zhao |
| Version: | 1.4 | ||
| Target Milestone: | 1.4 M1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | (D3)(Patch Merged) | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Robert Yang
2012-10-18 07:42:55 UTC
Can we make this recipe and future similar ones output their results in a test_results folder for easy QA checking? Would be great for qemu and BSP tests. Also if this works well, we could make this kind of recipes for rpm, zypper, vnc, gcc, g++ and other such test cases that require simple commands? Another thing: I talked to my colleagues and as it is some of these tests are done by sanity checks. We could also integrate our test cases with sanity checks? I would like to note that this bug matches very closely the ptest initiative I'm developing. Description: https://lists.yoctoproject.org/pipermail/yocto/2012-June/009443.html Latest patch set: http://lists.linuxtogo.org/pipermail/openembedded-core/2012-November/032076.html Yocto commit 61583fe11f2494e37ec0dd6e3bdeadf33f25f199 build qemuarm sato-sdk images, can run following command: /opt/perl-tests/t/TEST git info: 66f4c8a674d9f8db958b13866af4d63ab8cbcd44 git branch: poky/master (In reply to comment #4) > build qemuarm sato-sdk images, can run following command: > /opt/perl-tests/t/TEST command run as "cd /opt/perl-tests/t && ./TEST" |