| Summary: |
wic: errors from exec_cmd don't show the error output |
| Product: |
[Build System, Metadata & Runtime] OE-Core
|
Reporter: |
Christopher Larson <kergoth> |
| Component: |
Scripts and Tools | Assignee: |
Ed Bartosh <eduard.bartosh> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
|
| Severity: |
normal
|
|
|
| Priority: |
Medium
|
CC: |
richard.purdie, ross.burton
|
| Version: |
unspecified | |
|
| Target Milestone: |
2.3 M2 | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
No (bug/feature does not impact docs)
|
|---|
| Bug Depends on: |
10815
|
|
|
| Bug Blocks: |
|
|
|
| Attachments: |
| Description |
Flags |
|
v1
|
none
|
|
See this logic: if out: msger.debug('"%s" output: %s' % (args[0], out)) if ret != 0: S> msger.error("exec_cmd: '%s' returned '%s' instead of 0" % \ (cmd_and_args, ret)) So it fails to show stdout/stderr to the user on failure unless the user passed -D to wic. This is not useful. Also, all of this runner/exec code duplicates the other wrapping of subprocess done elsewhere in bitbake and oe-core.