On 7 July 2014 23:18, Patrick Hunt ph...@apache.org wrote:
The test output for the c client seems to be broken. afaict this is a
recent change because the jenkins console output shows the test
details, but I don't see them in the latest trunk.
I now see this (along with a long pause)
The latter - test-core-cppunit.
Patrick
On Tue, Jul 8, 2014 at 8:56 AM, Raúl Gutiérrez Segalés
r...@itevenworks.net wrote:
On 7 July 2014 23:18, Patrick Hunt ph...@apache.org wrote:
The test output for the c client seems to be broken. afaict this is a
recent change because the jenkins
Yeah, I was pretty much sure we had a jira for this latest failure, but I
couldn't find it...
-Flavio
-Original Message-
From: Patrick Hunt [mailto:ph...@apache.org]
Sent: 08 July 2014 17:00
To: DevZooKeeper
Subject: Re: c client test output seems to be broken for trunk
Well, it still invokes make check-TESTS but I don't think it sets anything
else up. Hmm, looks like latest autoconf might redirect check-TESTS to
$test-name.log by default as opposed to stdout.
Still checking, but you can probably find the .log files in the build dirs,
i.e.:
$ tailf
...@yahoo.com.invalid wrote:
Yeah, I was pretty much sure we had a jira for this latest failure, but I
couldn't find it...
-Flavio
-Original Message-
From: Patrick Hunt [mailto:ph...@apache.org]
Sent: 08 July 2014 17:00
To: DevZooKeeper
Subject: Re: c client test output seems
...@yahoo.com.invalid wrote:
Yeah, I was pretty much sure we had a jira for this latest failure, but I
couldn't find it...
-Flavio
-Original Message-
From: Patrick Hunt [mailto:ph...@apache.org]
Sent: 08 July 2014 17:00
To: DevZooKeeper
Subject: Re: c client test output seems
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.
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
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:
