flush output stream after writing

[danchr]

This should make Jenkins print the output immediately, rather than as
chunks.

[coveralls]

Coverage increased (+0.001%) to 99.463% when pulling b7034b6 on danchr:master into d6d8734 on xmlrunner:master.

[dnozay]

This should make Jenkins print the output immediately, rather than as chunks.

Flushing after each line is usually very bad for write-heavy workloads.

[danchr]

This should make Jenkins print the output immediately, rather than as chunks.

Flushing after each line is usually very bad for write-heavy workloads.

True, but a test run isn't exactly I/O-intensive, and doesn't become so by performing a single write per test IMO. If you look at the relevant sources in CPython, they do a flush per test in non-verbose output, so it should be quite safe.

[codecov-io]

Codecov Report

Merging #172 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #172      +/-   ##
==========================================
+ Coverage   99.46%   99.46%   +<.01%     
==========================================
  Files          17       17              
  Lines        1303     1306       +3     
==========================================
+ Hits         1296     1299       +3     
  Misses          7        7

Impacted Files	Coverage Δ
xmlrunner/result.py	98.18% <100%> (+0.01%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d6d8734...b7034b6. Read the comment docs.