diff options
author | Richard Ipsum <richard.ipsum@codethink.co.uk> | 2015-04-28 16:00:51 +0100 |
---|---|---|
committer | Richard Ipsum <richardipsum@fastmail.co.uk> | 2015-04-29 16:11:36 +0000 |
commit | dd755f80c09b45fc39a3af65eb239c92f9da3669 (patch) | |
tree | d187ee812bfea98f8250cedc2aa9e98365b32970 | |
parent | ac6d1896b3acdf9f6d0cf6019b14b32c570d1e58 (diff) | |
download | morph-dd755f80c09b45fc39a3af65eb239c92f9da3669.tar.gz |
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
-rw-r--r-- | distbuild/initiator.py | 1 |
1 files changed, 0 insertions, 1 deletions
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'] |