| Summary: | IMAGE_GEN_DEBUGFS should be tested | ||
|---|---|---|---|
| Product: | [QA/Testing] Build Testing | Reporter: | Ross Burton <ross.burton> |
| Component: | general | Assignee: | yeoh ee peng <ee.peng.yeoh> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | leonardo.sandoval.gonzalez, randy.macleod, srikanthx.x.bheemanadhuni |
| Version: | 2.3 | ||
| Target Milestone: | 4.99 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Ross Burton
2017-01-10 17:28:55 UTC
I guess we should also be checking that the generated tarball does in fact contain debug symbols that work, but that can be step 2. Didn't made it to M1, moving to M2. This wasn't integrated on 2.4 M3. Moving the target to 2.5 M1. Rebased and sent patch v4 http://lists.openembedded.org/pipermail/openembedded-core/2017-December/145415.html patch send in comment 3,4 and 5 the changes are similar and the commit Id is same in all the three patches. This is expected ? Consider the patches from comment 3 and comment 7, applied these patches to the latest 2.5.1 release and tested the test_image_gen_debugfs case and successfully passed. Enhanced patch submitted. https://lists.openembedded.org/g/openembedded-core/topic/patch/72694485?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,72694485 |