bitbake/runqueue: fix clash when setscene & real tasks done in same build

If a build causes a real task to be run when the setscene task has already
run then it was possible for dependent packages to be rebuilding at the same
time as a rebuild of the packages they depended on, resulting in failures
when files were missing. This change looks in the setscene covered list and
removes anything where a dependency of the real task is going to be run (e.g.
do_install is going to be run even though the setscene equivalent of
do_populate_sysroot has already been run).

As an additional safeguard we also delete the stamp file for the setscene
task under these circumstances.

Fixes [YOCTO #792]

(From Poky rev: b4268c08c350a7928a0b1a041b04ffe5a44e77b4)

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake/runqueue: show correct task name for setscene task failure

If a setscene task failed previously it was showing an incorrect task
name in the error line. This patch ensures we show the correct name, also
including the "_setscene" suffix.

(From Poky rev: 9d9c68e3536387150e3ce7261f4770576e724dd9)

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake/runqueue: When we successfully fork off a task and there are more processes we can start do so immediately

(From Poky rev: 974ea1a190167dcfd831ba1fc5f733e0dc9a6fda)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake/runqueue: When we have successfully collected a pid value return True to ensure we don't sleep in the main loop

(From Poky rev: 5a178b547bbf6d99c42cba6821b3f559e585a079)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake/cooker: Ensure delays are accurately transfered to the idle loops from runqueue

(From Poky rev: 579ecccc2244da43b9bc03fb09bb71d8a0219a8b)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake/cooker.py: Fix debug message arguments

(From Poky rev: 06bb59d)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake/server/process: Move implementation knowledge of event queue into the server

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake/server: Move server specific code into the server backend and create a server API

Move the server implementation specific code into the server backend where
it belongs and replace this with a set of object method calls which
establish the server, detach it and then connect to it using appropriate
IPC.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake/server: Add the none server back for now

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
xmlrpc/event: Add ability to send pickled events to UI if requested

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
hob/crumbs/hobeventhandler: Remove server specific implementation details missed in the precious cleanup

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake/hob: only show one progress dialog when changing machine

Remove a spurious signal emission which resulted in two progress dialogs
being shown after changing the machine.

(From Poky rev: 7738e86e8b4881056bd44d0f767d17b36159a7bb)

Signed-off-by: Joshua Lock <josh@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake/depexp: closing progress dialog kills gui

It seems safe to assume a user hitting the close button
on the dialog wants to kill the whole UI.

(From Poky rev: e21150f2b18ff4ac85e64ed8814f0268007830c0)

Signed-off-by: Joshua Lock <josh@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake/goggle: closing the progress dialog kills the UI

It's unlikely that someone wants to close the progress dialog
yet leave the UI (and BitBake process) running, so hook up
the progress dialogs delete-event to exit gtk.

(From Poky rev: c9bb30b232396bbdd3c97c1059e972d6a4abf637)

Signed-off-by: Joshua Lock <josh@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake/hob: fix cancel button

An accidental logic inversion (aka thinko) had the cancel button only
cancel a build when the user didn't confirm the cancellation (i.e. clicked
no)...

(From Poky rev: ff3e326269d27662c830b04e05b571d257b89346)

Signed-off-by: Joshua Lock <josh@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
knotty: If any error messages are seen, set our exit code accordingly

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
data.py: Ensure vardeps flags get expanded

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
runqueue.py: Export further hash information into the task environment

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake-layers: Add comment header

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
build/runqueue: Pass quieterrors flag around to supress errors at task execution time

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>