| Summary: |
bitbake -e with knotty spins if stdout is paginated |
| Product: |
[Build System, Metadata & Runtime] BitBake
|
Reporter: |
Magnus Olsson <magnus> |
| Component: |
bitbake | Assignee: |
Richard Purdie <richard.purdie> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
|
| Severity: |
normal
|
|
|
| Priority: |
Low
|
CC: |
poky.bs.watcher, poky.watcher
|
| Version: |
unspecified | |
|
| Target Milestone: |
1.8 | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
No (bug/feature does not impact docs)
|
|---|
I often use "bitbake -e core-image-minimal | less" to interactively grep for variable values etc. While 'less' is blocking stdout, bitbake will use 100% CPU on one core until I scroll to the end of output (or quit 'less' to break the pipe). This is not a big deal, but if you like me keep one of these less-invokations running while writing recipes (to review variables), the CPU fan on my laptop will go nuts. I use bitbake 1.22, but I was also able to reproduce this on bitbake master (1ea658dcdfde5465d3ecdb97550e0a66cb8b122e as of writing, 2015-01-14). I expect bitbake with knotty UI to behave like other console programs, such as: python -c 'while True: print("foo")' | less .. which consumes no CPU while being blocked.