_pipeline.py: Add task progress to resolve_elements()

Resolving the initial cached state of Elements could
potentially take a while, especially for large projects
or local caches which are on a latent filesystem. We should
report progress.

1 files changed, 8 insertions, 1 deletions

diff --git a/src/buildstream/_pipeline.py b/src/buildstream/_pipeline.py
index 4b0c6ad94..b5711109e 100644
--- a/src/buildstream/_pipeline.py
+++ b/src/buildstream/_pipeline.py
@@ -138,7 +138,11 @@ class Pipeline():
     #    targets (list of Element): The list of toplevel element targets
     #
     def resolve_elements(self, targets):
-        with self._context.messenger.timed_activity("Resolving cached state", silent_nested=True):
+        with self._context.messenger.simple_task("Resolving cached state", silent_nested=True) as task:
+            # We need to go through the project to access the loader
+            if task:
+                task.set_maximum_progress(self._project.loader.loaded)
+
             # XXX: Now that Element._update_state() can trigger recursive update_state calls
             # it is possible that we could get a RecursionError. However, this is unlikely
             # to happen, even for large projects (tested with the Debian stack). Although,
@@ -154,6 +158,9 @@ class Pipeline():
                 # dependencies.
                 element._update_ready_for_runtime_and_cached()
 
+                if task:
+                    task.add_current_progress()
+
     # check_remotes()
     #
     # Check if the target artifact is cached in any of the available remotes