Yeah, same version same behavior here. Lemme try this in an older box. FWIW, tried this with others projects and make check-TESTS redirects stdout by default too... So maybe it is autoconf.
-rgs On 8 July 2014 09:17, Patrick Hunt <ph...@apache.org> wrote: > Ah, that might be it! fwiw I have this: > > autoconf (GNU Autoconf) 2.69 > > Are you seeing the same issue? Same version of autoconf? > > Looking at the last trunk build on apache jenkins it seems that the > output is still to stdout: > > https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper-trunk/2359/console > > So must be me! (well my autoconf version). Very odd. > > Patrick > > On Tue, Jul 8, 2014 at 9:10 AM, Raúl Gutiérrez Segalés > <r...@itevenworks.net> wrote: > > On 8 July 2014 09:08, Patrick Hunt <ph...@apache.org> wrote: > > > >> Yes, I found the redirected output. However what I would like to see > >> is that the stdout not be redirected. I'm not sure when that went it > >> but it seems recent. > >> > >> Having those high level messages output to stdout is helpful as it > >> simplifies debugging - esp for things like the jenkins failures. > >> > > > > Sure, agreed. I am git grepping around but nothing obvious yet, hence the > > fallback to blaming (maybe) latest autoconf tools. Still checking though. > > > > > > -rgs >
