Closed PegasusPlusUS closed 1 week ago
duplicate of https://github.com/ziglang/zig/issues/15091
Thank a lot! Checking #15091, it was marked as "added this to the 0.11.0 milestone on Apr 10, 2023" So still not resolved?
It's really confusing because if zig want to update building progress, I guess before build complete, test runner already started? Maybe after zig complete building, then test runner start, there will be no conflict on stdout.
Zig Version
0.13.0
Steps to Reproduce and Observed Behavior
Expected Behavior
If comment out the 'bw.flush();', test can run normally. Since the generated code emphasized 'don't forget to flush!', it might be something wrong within implementation of std.io.bufferedWriter?