[PATCH 08/26] isar-events: Do not start cleanup early

[Jan Kiszka <jan.kiszka@siemens.com>]

From: Jan Kiszka <jan.kiszka@siemens.com>

Umounting already on runQueueExitWait just pulls the carpet under the
feet of still running builds, causing follow-up errors when just one
recipe failed. Even worse, terminating builds with ctrl-c does not allow
to finish most of the running tasks because they will stumble over
disappearing mounts.

While at it, give the handler a clearer name, namely that of its
trigger.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
 meta/classes/isar-events.bbclass | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/classes/isar-events.bbclass b/meta/classes/isar-events.bbclass
index 7dd1ed5..62eb25d 100644
--- a/meta/classes/isar-events.bbclass
+++ b/meta/classes/isar-events.bbclass
@@ -4,9 +4,9 @@
 # Copyright (C) 2015-2017 ilbers GmbH
 # Copyright (c) Siemens AG, 2018
 
-addhandler isar_handler
+addhandler build_completed
 
-python isar_handler() {
+python build_completed() {
     import subprocess
 
     tmpdir = d.getVar('TMPDIR', True)
@@ -25,4 +25,4 @@ python isar_handler() {
                 )
 }
 
-isar_handler[eventmask] = "bb.runqueue.runQueueExitWait bb.event.BuildCompleted"
+build_completed[eventmask] = "bb.event.BuildCompleted"
-- 
2.16.4