From dd755f80c09b45fc39a3af65eb239c92f9da3669 Mon Sep 17 00:00:00 2001 From: Richard Ipsum Date: Tue, 28 Apr 2015 16:00:51 +0100 Subject: Ignore BuildProgress messages Once building starts we close the json machine on the initiator, but we may have received build progress events between processing our build-started event and closing the json machine, since there is not a nice way to tell the different types of build progress apart (they all use BuildProgress) we will ignore all BuildProgress messages for now. A possible fix for this is to introduce GraphProgress messages so that we can report the building of the graph without reporting other types of BuildProgress ("Waiting for worker" or "Transferring artifact to cache") that we're not interested in. Note that we will still report build failures or build success, so if there's a mistake in the definitions this will be reported before the detach can occur, similarly if the system is already built this will be reported before the detach happens. Change-Id: Ia006ccfba826d2c91f4dea6c028ecdcb5a2b02d6 --- distbuild/initiator.py | 1 - 1 file changed, 1 deletion(-) diff --git a/distbuild/initiator.py b/distbuild/initiator.py index 359c9dbf..d0185608 100644 --- a/distbuild/initiator.py +++ b/distbuild/initiator.py @@ -298,7 +298,6 @@ class InitiatorStart(Initiator): 'build-finished': self._handle_build_finished_message, 'build-failed': self._handle_build_failed_message, 'build-cancelled': self._handle_build_cancelled_message, - 'build-progress': self._handle_build_progress_message, } msg_type = event.msg['type'] -- cgit v1.2.1