[urcu] tap-driver.sh: flush stdout after eachtest result
Commit Message
This is useful in a CI system where stdout is fully buffered and you
look at the console output to see which test is hanging.
Signed-off-by: Michael Jeanson <mjeanson at efficios.com>
---
config/tap-driver.sh | 3 +++
1 file changed, 3 insertions(+)
Comments
Merged into liburcu master branch (only), thanks!
Mathieu
----- On Mar 14, 2019, at 11:35 AM, Michael Jeanson mjeanson at efficios.com wrote:
> This is useful in a CI system where stdout is fully buffered and you
> look at the console output to see which test is hanging.
>
> Signed-off-by: Michael Jeanson <mjeanson at efficios.com>
> ---
> config/tap-driver.sh | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/config/tap-driver.sh b/config/tap-driver.sh
> index 4254e2b..12742ca 100755
> --- a/config/tap-driver.sh
> +++ b/config/tap-driver.sh
> @@ -273,6 +273,9 @@ function report(result, details)
> msg = msg " " details
> # Output on console might be colorized.
> print decorate_result(result) msg
> + # Flush stdout after each test result, this is useful when stdout
> + # is buffered, for example in a CI system.
> + fflush()
> # Log the result in the log file too, to help debugging (this is
> # especially true when said result is a TAP error or "Bail out!").
> print result msg | "cat >&3";
> --
> 2.17.1
@@ -273,6 +273,9 @@ function report(result, details)
msg = msg " " details
# Output on console might be colorized.
print decorate_result(result) msg
+ # Flush stdout after each test result, this is useful when stdout
+ # is buffered, for example in a CI system.
+ fflush()
# Log the result in the log file too, to help debugging (this is
# especially true when said result is a TAP error or "Bail out!").
print result msg | "cat >&3";