summaryrefslogtreecommitdiffstats
path: root/scripts/test-reexec
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.intel.com>2016-06-23 22:59:12 +1200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-07-08 09:57:27 +0100
commit1b930b41a5e677eea0adae3d247f43b77d1945f6 (patch)
treee3d3c0099efb6820c3bdc403d8842db4b4d73200 /scripts/test-reexec
parentf3b62c1c2e47968084342d1fe2a9af596a3ba93c (diff)
downloadpoky-1b930b41a5e677eea0adae3d247f43b77d1945f6.tar.gz
bitbake: runqueue: report progress for "Preparing RunQueue" step
When "Preparing RunQueue" shows up you can expect to wait up to 30 seconds while it works - which is a bit long to leave the user waiting without any kind of output. Since the work being carried out during this time is divided into stages such that it's practical to determine internally how it's progressing, replace the message with a progress bar. Actually what happens during this time is two major steps rather than just one - the runqueue preparation itself, followed by the initialisation prior to running setscene tasks. I elected to have the progress bar cover both as one (there doesn't appear to be much point in doing otherwise from a user perspective). I did however describe it as "initialising tasks". (Bitbake rev: 591e9741e108487ff437e77cb439ef2dbca42e03) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/test-reexec')
0 files changed, 0 insertions, 0 deletions