Skip to contentSkip to conversation

tap-driver.sh: flush stdout after each test result

PATCH Mathieu Desnoyers 1 participant 1 message Mar 14, 2019 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

Mathieu Desnoyers

author Applied
#1 lore raw

Merged into liburcu master branch (only), thanks!

Mathieu

Quoted 24 lines · ----- On Mar 14, 2019, at 11:35 AM, Michael Jeanson [email protected] 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.

---
config/tap-driver.sh | 3 +++

1 file changed, 3 insertions(+)
config/tap-driver.sh +3 -1
index 4254e2b..12742ca 100755
@@ -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

Signature · 3 lines
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com