build runner prints "failed command" when step has non-failure stderr
Writing to stdout is illegal, writing to stderr isn't (AFAIK).
build runner prints "failed command" when step has non-failure stderr
build runner prints "failed command" when step has non-failure stderr
OK, I can undestand the part about not swallowing stderr and outputting in case of failure. I thought that it was how it was supposed to work, but it is fine if it doesn't do that.
build runner prints "failed command" when step has non-failure stderr
build runner prints "failed command" when step has non-failure stderr
May I ask why? Even for unit tests having debug logging can be useful, particularly if tests fail. Why prohibit any output on both stdout and stderr? This is not very user friendly, IMO.
build runner prints "failed command" when step has non-failure stderr
Also, I think that the test runner is supposed to capture stderr and only show it in case of failure?
zig build test printing "failed command:" if the test writes to stderr