You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a short section on the QEMU tessting documentation that describes
how the QEMU UART console output and log output are muxed into stdout
without line buffering, to avoid confusion about interleaving of
characters from both inputs.
Signed-off-by: Alex Jones <[email protected]>
Copy file name to clipboardExpand all lines: third_party/qemu/README.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,3 +53,10 @@ For example, to manually add some traces for the USB device and alert updates wh
53
53
```
54
54
./bazelisk.sh test //path_to_qemu_test:my_test --test_arg=--qemu-args="--trace ot_usbdev* --trace ot*update_alert*"
55
55
```
56
+
57
+
### Logging
58
+
59
+
When executing a test in a QEMU execution environment, the default behavior is that the QEMU log output stream is combined with the regular UART console output stream.
60
+
When both interfaces are simultaneously written, it is possible that output may be disrupted by the characters interleaved from both streams.
61
+
This can be particularly noticeable when tracing, where the QEMU log is often written much faster than regular console output.
62
+
These outputs are not currently buffered by line breaks before combining the streams, meaning that it is possible for one line of console output to be split across multiple QEMU log lines.
0 commit comments