On Mon, 2 Nov 2020 at 13:09, Daniel P. Berrangé <[email protected]> wrote: > > It is hard to diagnose why Sphinx fails in a CI environment, as we > discard the stdout/err and just print a generic error message. > > Signed-off-by: Daniel P. Berrangé <[email protected]>
This kind of detailed-diagnostics should go into whatever meson's equivalent of config.log is. There's an argument for printing it if the user asked for --enable-docs specifically, but if we're doing the usual "see if it works, use it if it does" logic then we shouldn't be printing diagnostic logging from Sphinx (which can be pretty ugly and longwinded) in the middle of the meson output, IMHO. thanks -- PMM
