Re: Crazy display

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Tue, 2016-09-27 at 15:50 +1000, Jonathan Liu wrote:
> Hi Gary,
> 
> On 15 September 2016 at 21:30, Gary Thomas <gary@mlbassoc.com> wrote:
> > 
> > I haven't seen this before, just thought I'd toss it out there.
> > I was doing a build (actually three in parallel in separate
> > windows on my build box) and noticed this:
> > 
> > Currently  3 running tasks (3282 of 5081)  64%
> > > 
> > > ###################################################        |
> > 0: busybox-1.24.1-r0 do_compile (pid 29425)
> > Currently  3 running tasks (3283 of 5081)  64%
> > > 
> > > ###################################################        |
> > Currently  3 running tasks (3429 of 5081)  67%
> > > 
> > > #####################################################        |
> > 0: gstreamer1.0-libav-1.8.3-r0 do_configure (pid 10393)
> > Currently  1 running tasks (3560 of 5081)  70%
> > > 
> > > ########################################################        |
> > 0: gstreamer1.0-libav-1.8.3-r0 do_compile (pid 17458)
> > Currently  3 running tasks (3601 of 5081)  70%
> > > 
> > > ########################################################        |
> > 0: gstreamer1.0-libav-1.8.3-r0 do_compile (pid 17458)
> > 1: gdk-pixbuf-2.34.0-r0 do_package_write_ipk (pid 12673)
> > 2: unifdef-native-2.11-r0 do_populate_lic (pid 24548)
> > 
> > Somehow the task tracker (that does a nice job of telling the user
> > what's going on without being overwhelming BTW) got very confused!
> > 
> > I doubt if I can every repeat this, just passing on the
> > observation!
> This seems to be related to
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=10024.
> I get this issue after it prints "Child process exit status 4:
> lock_held" and then that message is overridden by the task status
> with
> the progress bar duplicated down one line.

Paul did fix some progress bar issues which were one cause of this.
pseudo is another cause and we've not gotten to the bottom of the
pseudo issue :(. It writes to the console unknown to knotty so there
isn't much we can do about it from the bitbake side, it should be a)
making it clear the messages come from psuedo and b) likely going to a
logfile, not the main console.

Cheers,

Richard