Bug 8768 - No output during build if curses.tigetstr("cuu") fails in knotty.py
Summary: No output during build if curses.tigetstr("cuu") fails in knotty.py
Status: RESOLVED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: 2.2
Hardware: x86 Multiple
: Medium normal
Target Milestone: 2.1 M2
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-12-04 10:35 UTC by ulfalizer
Modified: 2016-01-08 19:20 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ulfalizer 2015-12-04 10:35:41 UTC 
updateFooter() in knotty.py returns early if 'not self.cuu', meaning no output at all is printed in that case. self.ccu is initialized to curses.tigetstr("cuu") earlier.

An improvement would be to switch to verbose mode instead of curses.tigetstr("cuu") fails.
Comment 1 ulfalizer 2015-12-04 10:48:20 UTC 
An easy way to reproduce this problem on my system is

  $ TERM=dumb bitbake <foo>