| Summary: | Regression do_package_write_rpm error since 3.1.11 | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Chanho Park <parkch98> |
| Component: | core | Assignee: | Ross Burton <ross.burton> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | akuster808, meta.mr.watcher, meta.watcher, pavel, randy.macleod, ross.burton, steve |
| Version: | 3.1.12 | ||
| Target Milestone: | 3.1.16 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Chanho Park
2021-12-20 02:44:59 UTC
There's no way that a change to oeqa will cause that issue. How are you reproducing the failure? Is it just bitbake libxml2? Does it happen every time, or occasionally? This recipe, or any recipe? (In reply to comment #1) > There's no way that a change to oeqa will cause that issue. > > How are you reproducing the failure? Is it just bitbake libxml2? Does it > happen every time, or occasionally? This recipe, or any recipe? The same errors can be seen from perl as well. Once I executed "bitbake -c cleansstate perl" and build it again, the errors were not reproduced anymore. So, I only can reproduce this issue once I wipe out tmp directory and sstate cache directory. Below error was coming from rpmbuild on do_package_write_rpm stage. > error: create archive failed: cpio: write failed - Invalid argument MV may be seeing this. Let me double check. There is a patch in stable/dunfell-nut that may be helpful. MV has passed that along to its customer to test as well. https://git.yoctoproject.org/poky-contrib/commit/?h=stable/dunfell-nut&id=7b27c85ed93cd6d193971a0d535bfa47454801f9 (In reply to comment #4) > There is a patch in stable/dunfell-nut that may be helpful. MV has passed > that along to its customer to test as well. > > https://git.yoctoproject.org/poky-contrib/commit/?h=stable/dunfell- > nut&id=7b27c85ed93cd6d193971a0d535bfa47454801f9 Great. The issue cannot be reproduced anymore with this patch. I saw it was included in dunfell branch and it will be release on 3.1.15 release, right? (In reply to comment #5) > (In reply to comment #4) > > There is a patch in stable/dunfell-nut that may be helpful. MV has passed > > that along to its customer to test as well. > > > > https://git.yoctoproject.org/poky-contrib/commit/?h=stable/dunfell- > > nut&id=7b27c85ed93cd6d193971a0d535bfa47454801f9 > > Great. The issue cannot be reproduced anymore with this patch. I saw it was > included in dunfell branch and it will be release on 3.1.15 release, right? This patch did fix our Customer's issue. Yes I believe it should be if I understand the release processes. Fixed in 3.1.15. |