[PATCH 13/13] qemu: note the build-output capture limitation

From: Daniel Gomez <[email protected]>

ninja re-execs after regenerating its build manifest and the re-exec'd main
build's stdout does not survive Ansible's pipe capture, so the build output
recorded in the task result and the callback log stops at the [1/18]
manifest-regeneration fragment. The build still succeeds; only the captured
log is short. Note this by the build task so a future change can redirect the
build to a file and read it back to record the full output.

Generated-by: Claude AI
Signed-off-by: Daniel Gomez <[email protected]>
---
 playbooks/roles/qemu/tasks/main.yml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/playbooks/roles/qemu/tasks/main.yml b/playbooks/roles/qemu/tasks/main.yml
index 599ca736..2ed8daed 100644
--- a/playbooks/roles/qemu/tasks/main.yml
+++ b/playbooks/roles/qemu/tasks/main.yml
@@ -87,6 +87,8 @@
   tags: ["qemu_build"]
   register: qemu_nproc
 
+# ninja re-execs after regenerating its manifest, losing the main build's
+# stdout to Ansible's pipe capture (log stops at [1/18]); redirect to a file.
 - name: Build QEMU
   community.general.make:
     chdir: "{{ qemu_build_dir }}"

-- 
2.54.0