From: Gary Thomas <gary@mlbassoc.com>
To: "bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Subject: Parsing recipes progress bar doesn't show incremental progress
Date: Thu, 15 Jan 2015 11:22:33 -0700 [thread overview]
Message-ID: <54B80569.5030507@mlbassoc.com> (raw)
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
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2015-01-15 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 18:22 Gary Thomas [this message]
2015-01-16 8:28 ` Parsing recipes progress bar doesn't show incremental progress Richard Purdie
2015-01-16 11:53 ` Gary Thomas
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=54B80569.5030507@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