| Summary: | builds for valgrind ptests are failing for a number of arm tunings | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Dave Lerner <dave.lerner> |
| Component: | devtools / tool chain | Assignee: | Dave Lerner <dave.lerner> |
| Status: | VERIFIED DUPLICATE | QA Contact: | Alexandru Roman <alexandru.costinx.roman> |
| Severity: | normal | ||
| Priority: | Medium | CC: | alexandru.costinx.roman, bogdanx.a.voiculescu, kexin.hao, meta.mr.watcher, meta.watcher |
| Version: | 1.7.1 | ||
| Target Milestone: | 1.9 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Dave Lerner
2015-05-12 21:14:20 UTC
Several arm tunings cause valgrind builds to fail, specifically in the regression tests that the poky DISTRO_FEATURE 'ptest' is always forcing to be built. Bug 7543 was just once instance of this failure. After discussions with MarkH, he suggested that a comprehensive list of tunings that fail should be determined, added to the valgrind recipe, and then that list should be used to exclude building ptests for the tunings that compile the ptests with errors. I was incorrect in Comment 1, and solving Bug 7543 as well as correcting the original ptest patch that wiped out CFLAGS settings for particular tests, has eliminated reduced the number of arm ptest build failures to two. The patch submitted for 7543 included build tests of the ptest apps, for all possible build tunings of beaglebone. This defect 7750 seems unnecessary. *** This bug has been marked as a duplicate of bug 7543 *** Do you really mean Bug 7543? https://bugzilla.yoctoproject.org/show_bug.cgi?id=7543 Changing to duplicate of 7453, originally had marked dup of 7543. *** This bug has been marked as a duplicate of bug 7453 *** verified |