| Summary: | elfutils ptest results are inconsistent per image | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Joshua Watt <JPEWhacker> | ||||||
| Component: | core | Assignee: | Mingli Yu <mingli.yu> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | Medium+ | CC: | meta.mr.watcher, meta.watcher, randy.macleod | ||||||
| Version: | 2.7 | ||||||||
| Target Milestone: | 2.8 M1 | ||||||||
| Hardware: | x86 | ||||||||
| OS: | Multiple | ||||||||
| Whiteboard: | |||||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||||
| Attachments: |
|
||||||||
|
Description
Joshua Watt
2019-04-18 18:14:30 UTC
Created attachment 4483 [details]
ptest log from core-image-sato build
Created attachment 4484 [details]
ptest log from core-image-sato-sdk build
Hi Joshua Watt, There is some fix for elfutils ptest as https://git.openembedded.org/openembedded-core/commit/?id=7ff76b86299289a4a5741f910399d95232f64f32, could you help to rerun the test? Currently: core-image-sato report: 25 of 197 tests failed (6 tests were not run) core-image-sato-sdk report: 23 of 199 tests failed (4 tests were not run) This is because below 4 cases PASS for core-image-sato-sdk as gcc available. PASS: run-strip-nothing.sh PASS: run-strip-g.sh PASS: run-disasm-x86.sh PASS: run-disasm-x86-64.sh And correspondingly, the above 4 cases for core-image-sato behaves 2 cases SKIP and 2 cases FAIL as gcc unavailable as below: which: no gcc in (/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin) SKIP: run-strip-nothing.sh which: no gcc in (/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin) SKIP: run-strip-g.sh ./run-disasm-x86.sh: line 25: gcc: command not found FAIL: run-disasm-x86.sh ./run-disasm-x86-64.sh: line 25: gcc: command not found So basically, the elfutils ptest results should be consistent if no gcc gap. Adding gcc as a dependency is an option. Commit currently in master-next: commit b8373f3a213f2001d4c698d56f02f6c0e7a36c3c Author: Richard Purdie <richard.purdie@linuxfoundation.org> Date: Mon Apr 29 13:00:37 2019 +0100 elfutils: Add gcc to ptest RDEPENDS Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> diff --git a/meta/recipes-devtools/elfutils/elfutils_0.176.bb b/meta/recipes-devtools/elfutils/elfutils_0.176.bb index fb2868723a..1362f4e42d 100644 --- a/meta/recipes-devtools/elfutils/elfutils_0.176.bb +++ b/meta/recipes-devtools/elfutils/elfutils_0.176.bb @@ -43,8 +43,7 @@ inherit autotools gettext ptest EXTRA_OECONF = "--program-prefix=eu- --without-lzma" EXTRA_OECONF_append_class-native = " --without-bzlib" -# gcc has been added to blacklist, we will find workaround solution -RDEPENDS_${PN}-ptest = "libasm libelf bash" +RDEPENDS_${PN}-ptest = "libasm libelf bash gcc" EXTRA_OECONF_append_class-target += "--enable-tests-rpath" The gcc dependency isn't quite right, it needs to be gcc-symlinks and may involve some binutils and some other pieces (maybe libgcc). |