Make it clear when buildman actually starts building. This happens when it has prepared the threads, working directory and output directories.
Signed-off-by: Simon Glass sjg@chromium.org ---
tools/buildman/builder.py | 1 + tools/buildman/test.py | 4 ++-- 2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/tools/buildman/builder.py b/tools/buildman/builder.py index a80333f..d4ea13e 100644 --- a/tools/buildman/builder.py +++ b/tools/buildman/builder.py @@ -1443,6 +1443,7 @@ class Builder: self._PrepareWorkingSpace(min(self.num_threads, len(board_selected)), commits is not None) self._PrepareOutputSpace() + Print('\rStarting build...', newline=False) self.SetupBuild(board_selected, commits) self.ProcessResult(None)
diff --git a/tools/buildman/test.py b/tools/buildman/test.py index d8f3c81..ed2a3a8 100644 --- a/tools/buildman/test.py +++ b/tools/buildman/test.py @@ -198,9 +198,9 @@ class TestBuild(unittest.TestCase): if line.text.strip(): count += 1
- # We should get one starting message, then an update for every commit + # We should get two starting messages, then an update for every commit # built. - self.assertEqual(count, len(commits) * len(boards) + 1) + self.assertEqual(count, len(commits) * len(boards) + 2) build.SetDisplayOptions(show_errors=True); build.ShowSummary(self.commits, board_selected) #terminal.EchoPrintTestLines()