On Fri, Oct 21, 2016 at 1:43 AM, Jeff King <p...@peff.net> wrote: > prove t5547-push-quarantine.sh :: -v > > The Travis tests do exactly this (along with --tee to actually save the > output). It seems like a minor miracle that this is the first test > output that has actually triggered as TAP input. I'd suggest that the > problem is not in the test, though, but that our "--verbose" option is > unsuitable for using with a TAP harness. > > The obvious fix would be to send "--verbose" output to stderr, but I > suspect that would end up annoying for people who do: > > ./t5547-push-quarantine.sh -v | less > > to read long output. Probably we need some option like "--log" which > logs in the same way that "--tee" does, but _without_ sending the data > to stdout. Naively, that just means replacing the "tee" invocation with > "cat", but I suspect it will be a lot more complicated than that, > because we still need to let the TAP output go to stdout. > > -Peff
Can we determine that we're running with something monitoring the TAP output? Because then we could make verbose go to stderr instead dynamically? Thanks, Jake
