From: Gary Thomas <gary@mlbassoc.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: Parsing recipes progress bar doesn't show incremental progress
Date: Fri, 16 Jan 2015 04:53:06 -0700 [thread overview]
Message-ID: <54B8FBA2.1060904@mlbassoc.com> (raw)
In-Reply-To: <1421396904.1798.5.camel@linuxfoundation.org>
On 2015-01-16 01:28, Richard Purdie wrote:
> On Thu, 2015-01-15 at 11:22 -0700, Gary Thomas wrote:
>> I think there has been a recent change in behaviour. When
>> you start up bitbake there is a progress bar during the recipe
>> parsing:
>> Parsing recipes: 100% |##########################################| Time: 00:00:05
>>
>> I used to see this bar fill as it went, but now it sits there
>> at 0% until it is completely done and then BAM goes to 100%
>>
>> Has anyone else seen this? I'm running Poky/Yocto updated
>> to 2b925045877aeb44d9823a8c9515e8ab8fca1e52 as of 2015-01-15
>
> My guess is that the delay introduced after parsing from pyinotify is
> causing the bar to be visible at 100% for a while. I've just merged the
> performance fix for pyinotify, can you see if its still doing what you
> describe after that?
It may be better, certainly less of the "pregnant pause" now.
The progress bar for 'parsing recipes' seems to work fine when it's
actually parsing a lot of recipes. The behaviour I was seeing happens
when bitbake is able to use cached data, e.g.
Loading cache: 100% |####################################################################################| ETA: 00:00:00
Loaded 1587 entries from dependency cache.
Parsing recipes: 100% |##################################################################################| Time: 00:00:01
Parsing of 1165 .bb files complete (1164 cached, 1 parsed). 1586 targets, 115 skipped, 0 masked, 0 errors.
In this case, the second progress bar was empty for the one second that
phase took and there were no intermediate changes to it.
Maybe it's just an impression I got yesterday when that second
progress bar sat empty for 5 seconds. Today it took only one
(for the same build tree), so perhaps you did improve it.
Thanks for looking at this.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2015-01-16 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 18:22 Parsing recipes progress bar doesn't show incremental progress Gary Thomas
2015-01-16 8:28 ` Richard Purdie
2015-01-16 11:53 ` Gary Thomas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54B8FBA2.1060904@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=bitbake-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox