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)
[exec] make[1]: Entering directory
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Anderson updated ZOOKEEPER-1958:
-
Attachment: ZOOKEEPER-1958.patch
A second submission, without the extraneous #define
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14054576#comment-14054576
]
Patrick Hunt commented on ZOOKEEPER-1801:
-
I'm seeing this same failure on
See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/1425/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 252 lines...]
.\src\zookeeper.c(2244): warning
See https://builds.apache.org/job/ZooKeeper-3.4-WinVS2008_java/523/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 186941 lines...]
[junit] 2014-07-08
See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008_java/768/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 273032 lines...]
[junit] 2014-07-08
See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/68/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 284302 lines...]
[junit] 2014-07-08 10:49:55,940
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14054843#comment-14054843
]
Hudson commented on ZOOKEEPER-1810:
---
SUCCESS: Integrated in ZooKeeper-trunk #2359
[
https://issues.apache.org/jira/browse/ZOOKEEPER-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14054842#comment-14054842
]
Hudson commented on ZOOKEEPER-827:
--
SUCCESS: Integrated in ZooKeeper-trunk #2359 (See
See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/1426/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 161 lines...]
.\src\zookeeper.c(2505): warning
nijel created ZOOKEEPER-1959:
Summary: Move zkEnv files to conf folder, since it is expected to
be configured by user
Key: ZOOKEEPER-1959
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1959
nijel created ZOOKEEPER-1960:
Summary: Improve logs in PurgeTxnLog.java to give more details
Key: ZOOKEEPER-1960
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1960
Project: ZooKeeper
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)
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated ZOOKEEPER-1961:
--
Description: while trying to stop a server that appears not to have started
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14055077#comment-14055077
]
Steve Loughran commented on ZOOKEEPER-1961:
---
stack
{code}
at
Steve Loughran created ZOOKEEPER-1961:
-
Summary: NPE in ZooKeeperServerMain.shutdown()
Key: ZOOKEEPER-1961
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1961
Project: ZooKeeper
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
The
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
The test _failure_ is a different issue, e.g.:
https://issues.apache.org/jira/browse/ZOOKEEPER-1801
What's I'm highlighting in this thread is that the c client test logs
that were being output to stdout are missing. Who turned it off?
Patrick
On Tue, Jul 8, 2014 at 9:03 AM, FPJ
The test _failure_ is a different issue, e.g.:
https://issues.apache.org/jira/browse/ZOOKEEPER-1801
What's I'm highlighting in this thread is that the c client test logs
that were being output to stdout are missing. Who turned it off?
Patrick
On Tue, Jul 8, 2014 at 9:03 AM, FPJ
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
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14055085#comment-14055085
]
Erik Anderson commented on ZOOKEEPER-1677:
--
The zookeeper client was offline
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://issues.apache.org/jira/browse/ZOOKEEPER-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14055133#comment-14055133
]
Hadoop QA commented on ZOOKEEPER-1677:
--
+1 overall. Here are the results of
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated ZOOKEEPER-1222:
Attachment: ZOOKEEPER-1222-br3_4.patch
Attaching branch 3.4 patch. Please ignore QA failure
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14055265#comment-14055265
]
Hadoop QA commented on ZOOKEEPER-1222:
--
-1 overall. Here are the results of
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1222
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2180/
###
## LAST 60 LINES OF THE CONSOLE
###
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14055268#comment-14055268
]
Rakesh R commented on ZOOKEEPER-1222:
-
Committed to trunk :
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated ZOOKEEPER-1222:
Fix Version/s: 3.4.7
getACL should only call DataTree.copyStat when passed in stat is not
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23259/#review47463
---
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Carter updated ZOOKEEPER-1865:
-
Attachment: ZOOKEEPER-1865.patch
Fix retry logic in Learner.connectToLeader()
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1865
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2181/
###
## LAST 60 LINES OF THE CONSOLE
###
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14055477#comment-14055477
]
Hadoop QA commented on ZOOKEEPER-1865:
--
-1 overall. Here are the results of
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14055547#comment-14055547
]
adroit commented on ZOOKEEPER-1237:
---
I am using 3.4.6 and we have same issue.
ERROR
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1403#comment-1403
]
Hudson commented on ZOOKEEPER-1222:
---
FAILURE: Integrated in ZooKeeper-trunk #2360
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14055580#comment-14055580
]
Flavio Junqueira commented on ZOOKEEPER-1955:
-
I've just made this comment
See https://builds.apache.org/job/ZooKeeper-trunk/2363/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 1475 lines...]
at
See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/1427/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 162 lines...]
.\src\zookeeper.c(2505): warning
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Biju Nair updated ZOOKEEPER-1948:
-
Attachment: zookeeper-1948.patch
Enable JMX remote monitoring
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1948
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2182/
###
## LAST 60 LINES OF THE CONSOLE
###
[
https://issues.apache.org/jira/browse/BOOKKEEPER-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14054926#comment-14054926
]
Hudson commented on BOOKKEEPER-203:
---
FAILURE: Integrated in Hadoop-trunk-Commit
43 matches
Mail list logo
