$PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS
See ${BUILD_URL}
###
## LAST 60 LINES OF THE CONSOLE
###
${BUILD_LOG, maxLines=60}
###
## FAILED TESTS (if any)
##
${FAILED_TESTS}
$PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS
See ${BUILD_URL}
###
## LAST 60 LINES OF THE CONSOLE
###
${BUILD_LOG, maxLines=60}
###
## FAILED TESTS (if any)
##
${FAILED_TESTS}
[jira] [Commented] (ZOOKEEPER-2380) Deadlock while shutting down the zookeeper
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179387#comment-15179387
]
Arshad Mohammad commented on ZOOKEEPER-2380:
It is very similar to ZOOKEEPER-2347 but it is different.
> Deadlock while shutting down the zookeeper
> --
>
> Key: ZOOKEEPER-2380
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2380
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
>Affects Versions: 3.5.0
>Reporter: Arshad Mohammad
>Assignee: Arshad Mohammad
>Priority: Blocker
>
> Zookeeper enters into deadlock while shutting down itself, thus making
> zookeeper service unavailable as deadlocked server is a leader. Here is the
> thread dump:
> {code}
> "QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled)" #25 prio=5
> os_prio=0 tid=0x7fbc502a6800 nid=0x834 in Object.wait()
> [0x7fbc4d9a8000] java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method) at
> java.lang.Thread.join(Thread.java:1245) - locked <
> 0xfeb78000> (a org.apache.zookeeper.server.SyncRequestProcessor)
> at java.lang.Thread.join(Thread.java:1319) at
> org.apache.zookeeper.server.SyncRequestProcessor.shutdown(SyncRequestProcessor.java:196)
> at
> org.apache.zookeeper.server.quorum.ProposalRequestProcessor.shutdown(ProposalRequestProcessor.java:90)
> at
> org.apache.zookeeper.server.PrepRequestProcessor.shutdown(PrepRequestProcessor.java:1016)
> at
> org.apache.zookeeper.server.quorum.LeaderRequestProcessor.shutdown(LeaderRequestProcessor.java:78)
> at
> org.apache.zookeeper.server.ZooKeeperServer.shutdown(ZooKeeperServer.java:561)
> - locked <
> 0xfeb61e20> (a
> org.apache.zookeeper.server.quorum.LeaderZooKeeperServer) at
> org.apache.zookeeper.server.quorum.QuorumZooKeeperServer.shutdown(QuorumZooKeeperServer.java:169)
> - locked <
> 0xfeb61e20> (a
> org.apache.zookeeper.server.quorum.LeaderZooKeeperServer) at
> org.apache.zookeeper.server.quorum.LeaderZooKeeperServer.shutdown(LeaderZooKeeperServer.java:102)
> - locked <
> 0xfeb61e20> (a
> org.apache.zookeeper.server.quorum.LeaderZooKeeperServer) at
> org.apache.zookeeper.server.quorum.Leader.shutdown(Leader.java:637) at
> org.apache.zookeeper.server.quorum.Leader.lead(Leader.java:590) - locked
> <
> 0xfeb781a0> (a org.apache.zookeeper.server.quorum.Leader) at
> org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:1108)
> "SyncThread:1" #46 prio=5 os_prio=0 tid=0x7fbc5848f000 nid=0x867 waiting
> for monitor entry [0x7fbc4ca9] java.lang.Thread.State: BLOCKED
> (on object monitor) at
> org.apache.zookeeper.server.quorum.Leader.processAck(Leader.java:784) -
> waiting to lock <0xfeb781a0> (a
> org.apache.zookeeper.server.quorum.Leader) at
> org.apache.zookeeper.server.quorum.AckRequestProcessor.processRequest(AckRequestProcessor.java:46)
> at
> org.apache.zookeeper.server.SyncRequestProcessor.flush(SyncRequestProcessor.java:183)
> at
> org.apache.zookeeper.server.SyncRequestProcessor.run(SyncRequestProcessor.java:113)
> {code}
> Leader.lead() calls shutdown() from the synchronized block, it acquired lock
> on Leader.java instance
> {code}
> while (true) {
> synchronized (this) {
> long start = Time.currentElapsedTime();
> .
> {code}
> In the shutdown flow SyncThread is trying to acquire lock on the same
> Leader.java instance.
> Leader thread acquired lock and waiting for SyncThread shutdown. SyncThread
> waiting for the lock to complete its shutdown. This is how ZooKeeper entered
> into deadlock
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2366) Reconfiguration of client port causes a socket leak
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179382#comment-15179382
]
Hadoop QA commented on ZOOKEEPER-2366:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12791407/ZOOKEEPER-2366.patch
against trunk revision 1733525.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 11 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
-1 findbugs. The patch appears to introduce 1 new Findbugs (version 2.0.3)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3082//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3082//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3082//console
This message is automatically generated.
> Reconfiguration of client port causes a socket leak
> ---
>
> Key: ZOOKEEPER-2366
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2366
> Project: ZooKeeper
> Issue Type: Bug
> Components: quorum
>Affects Versions: 3.5.0
>Reporter: Timothy Ward
>Assignee: Timothy Ward
>Priority: Critical
> Fix For: 3.5.2
>
> Attachments: ZOOKEEPER-2366.patch, zookeeper.patch
>
>
> The NIOServerCnxnFactory reconfigure method can leak server sockets, and
> hence make ports unusable until the JVM restarts:
> The first line of the method takes a reference to the current
> ServerSocketChannel and then the next line replaces it. The subsequent
> interactions with the server socket can fail (for example if the
> reconfiguration tries to bind to an in-use port). If they fail *before* the
> call to oldSS.close() then oldSS is *never* closed. This holds that port open
> forever, and prevents the user from rolling back to the previous port!
> The code from reconfigure is shown below:
> ServerSocketChannel oldSS = ss;
> try {
>this.ss = ServerSocketChannel.open();
>ss.socket().setReuseAddress(true);
>LOG.info("binding to port " + addr);
>ss.socket().bind(addr);
>ss.configureBlocking(false);
>acceptThread.setReconfiguring();
>oldSS.close();
>acceptThread.wakeupSelector();
>try {
> acceptThread.join();
> } catch (InterruptedException e) {
> LOG.error("Error joining old acceptThread when
> reconfiguring client port " + e.getMessage());
> }
>acceptThread = new AcceptThread(ss, addr, selectorThreads);
>acceptThread.start();
> } catch(IOException e) {
>LOG.error("Error reconfiguring client port to " + addr + " " +
> e.getMessage());
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Failed: ZOOKEEPER-2366 PreCommit Build #3082
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2366 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3082/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 449173 lines...] [exec] [exec] +1 tests included. The patch appears to include 11 new or modified tests. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] -1 findbugs. The patch appears to introduce 1 new Findbugs (version 2.0.3) warnings. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. [exec] [exec] -1 core tests. The patch failed core unit tests. [exec] [exec] +1 contrib tests. The patch passed contrib unit tests. [exec] [exec] Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3082//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3082//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3082//console [exec] [exec] This message is automatically generated. [exec] [exec] [exec] == [exec] == [exec] Adding comment to Jira. [exec] == [exec] == [exec] [exec] [exec] Comment added. [exec] a4eb769a68f92fa4e0b6af2461e9de162bbada14 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1646: exec returned: 2 Total time: 15 minutes 31 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Compressed 547.11 KB of artifacts by 23.4% relative to #3049 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-2366 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## 4 tests failed. FAILED: org.apache.zookeeper.server.quorum.ReconfigRecoveryTest.testCurrentObserverIsParticipantInNewConfig Error Message: waiting for server 2 being up Stack Trace: junit.framework.AssertionFailedError: waiting for server 2 being up at org.apache.zookeeper.server.quorum.ReconfigRecoveryTest.testCurrentObserverIsParticipantInNewConfig(ReconfigRecoveryTest.java:529) at org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79) FAILED: org.apache.zookeeper.test.ReconfigTest.testPortChangeToBlockedPort Error Message: Address already in use Stack Trace: java.net.BindException: Address already in use at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:376) at java.net.ServerSocket.bind(ServerSocket.java:376) at java.net.ServerSocket.bind(ServerSocket.java:330) at org.apache.zookeeper.test.ReconfigTest.testPortChangeToBlockedPort(ReconfigTest.java:687) at org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79) FAILED: org.apache.zookeeper.test.ReconfigTest.testPortChangeToBlockedPort Error Message: Address already in use Stack Trace: java.net.BindException: Address already in use at
$PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS
See ${BUILD_URL}
###
## LAST 60 LINES OF THE CONSOLE
###
${BUILD_LOG, maxLines=60}
###
## FAILED TESTS (if any)
##
${FAILED_TESTS}
[jira] [Updated] (ZOOKEEPER-2089) Improve the building blocks part of the programmer's guide
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2089: Hadoop Flags: (was: Incompatible change) > Improve the building blocks part of the programmer's guide > -- > > Key: ZOOKEEPER-2089 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2089 > Project: ZooKeeper > Issue Type: Improvement > Components: documentation >Affects Versions: 3.4.6, 3.5.0 >Reporter: Flavio Junqueira >Assignee: Flavio Junqueira > Fix For: 3.5.2, 3.6.0 > > > This part of the documentation has been incomplete since 3.1.2. The main > reason seems to be that the information that was supposed to be there exists > elsewhere in a different form. It needs a revision nonetheless. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2366) Reconfiguration of client port causes a socket leak
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-2366:
Attachment: ZOOKEEPER-2366.patch
I updated the patch to apply cleanly - ZOOKEEPER-2366.patch
> Reconfiguration of client port causes a socket leak
> ---
>
> Key: ZOOKEEPER-2366
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2366
> Project: ZooKeeper
> Issue Type: Bug
> Components: quorum
>Affects Versions: 3.5.0
>Reporter: Timothy Ward
>Assignee: Timothy Ward
>Priority: Critical
> Fix For: 3.5.2
>
> Attachments: ZOOKEEPER-2366.patch, zookeeper.patch
>
>
> The NIOServerCnxnFactory reconfigure method can leak server sockets, and
> hence make ports unusable until the JVM restarts:
> The first line of the method takes a reference to the current
> ServerSocketChannel and then the next line replaces it. The subsequent
> interactions with the server socket can fail (for example if the
> reconfiguration tries to bind to an in-use port). If they fail *before* the
> call to oldSS.close() then oldSS is *never* closed. This holds that port open
> forever, and prevents the user from rolling back to the previous port!
> The code from reconfigure is shown below:
> ServerSocketChannel oldSS = ss;
> try {
>this.ss = ServerSocketChannel.open();
>ss.socket().setReuseAddress(true);
>LOG.info("binding to port " + addr);
>ss.socket().bind(addr);
>ss.configureBlocking(false);
>acceptThread.setReconfiguring();
>oldSS.close();
>acceptThread.wakeupSelector();
>try {
> acceptThread.join();
> } catch (InterruptedException e) {
> LOG.error("Error joining old acceptThread when
> reconfiguring client port " + e.getMessage());
> }
>acceptThread = new AcceptThread(ss, addr, selectorThreads);
>acceptThread.start();
> } catch(IOException e) {
>LOG.error("Error reconfiguring client port to " + addr + " " +
> e.getMessage());
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2380) Deadlock while shutting down the zookeeper
Arshad Mohammad created ZOOKEEPER-2380:
--
Summary: Deadlock while shutting down the zookeeper
Key: ZOOKEEPER-2380
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2380
Project: ZooKeeper
Issue Type: Bug
Components: server
Affects Versions: 3.5.0
Reporter: Arshad Mohammad
Assignee: Arshad Mohammad
Priority: Blocker
Zookeeper enters into deadlock while shutting down itself, thus making
zookeeper service unavailable as deadlocked server is a leader. Here is the
thread dump:
{code}
"QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled)" #25 prio=5
os_prio=0 tid=0x7fbc502a6800 nid=0x834 in Object.wait()
[0x7fbc4d9a8000] java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method) at
java.lang.Thread.join(Thread.java:1245) - locked <
0xfeb78000> (a org.apache.zookeeper.server.SyncRequestProcessor)
at java.lang.Thread.join(Thread.java:1319) at
org.apache.zookeeper.server.SyncRequestProcessor.shutdown(SyncRequestProcessor.java:196)
at
org.apache.zookeeper.server.quorum.ProposalRequestProcessor.shutdown(ProposalRequestProcessor.java:90)
at
org.apache.zookeeper.server.PrepRequestProcessor.shutdown(PrepRequestProcessor.java:1016)
at
org.apache.zookeeper.server.quorum.LeaderRequestProcessor.shutdown(LeaderRequestProcessor.java:78)
at
org.apache.zookeeper.server.ZooKeeperServer.shutdown(ZooKeeperServer.java:561)
- locked <
0xfeb61e20> (a
org.apache.zookeeper.server.quorum.LeaderZooKeeperServer) at
org.apache.zookeeper.server.quorum.QuorumZooKeeperServer.shutdown(QuorumZooKeeperServer.java:169)
- locked <
0xfeb61e20> (a
org.apache.zookeeper.server.quorum.LeaderZooKeeperServer) at
org.apache.zookeeper.server.quorum.LeaderZooKeeperServer.shutdown(LeaderZooKeeperServer.java:102)
- locked <
0xfeb61e20> (a
org.apache.zookeeper.server.quorum.LeaderZooKeeperServer) at
org.apache.zookeeper.server.quorum.Leader.shutdown(Leader.java:637) at
org.apache.zookeeper.server.quorum.Leader.lead(Leader.java:590) - locked <
0xfeb781a0> (a org.apache.zookeeper.server.quorum.Leader) at
org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:1108)
"SyncThread:1" #46 prio=5 os_prio=0 tid=0x7fbc5848f000 nid=0x867 waiting
for monitor entry [0x7fbc4ca9] java.lang.Thread.State: BLOCKED (on
object monitor) at
org.apache.zookeeper.server.quorum.Leader.processAck(Leader.java:784) -
waiting to lock <0xfeb781a0> (a
org.apache.zookeeper.server.quorum.Leader) at
org.apache.zookeeper.server.quorum.AckRequestProcessor.processRequest(AckRequestProcessor.java:46)
at
org.apache.zookeeper.server.SyncRequestProcessor.flush(SyncRequestProcessor.java:183)
at
org.apache.zookeeper.server.SyncRequestProcessor.run(SyncRequestProcessor.java:113)
{code}
Leader.lead() calls shutdown() from the synchronized block, it acquired lock on
Leader.java instance
{code}
while (true) {
synchronized (this) {
long start = Time.currentElapsedTime();
.
{code}
In the shutdown flow SyncThread is trying to acquire lock on the same
Leader.java instance.
Leader thread acquired lock and waiting for SyncThread shutdown. SyncThread
waiting for the lock to complete its shutdown. This is how ZooKeeper entered
into deadlock
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
ZooKeeper_branch35_openjdk7 - Build # 1 - Failure
See https://builds.apache.org/job/ZooKeeper_branch35_openjdk7/1/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 367833 lines...] [junit] 2016-03-04 05:09:30,938 [myid:] - INFO [New I/O worker #9277:ClientCnxn$SendThread@981] - Socket connection established, initiating session, client: /127.0.0.1:46959, server: 127.0.0.1/127.0.0.1:24767 [junit] 2016-03-04 05:09:30,938 [myid:] - INFO [New I/O worker #9277:ClientCnxnSocketNetty$1@146] - channel is connected: [id: 0xffdef488, /127.0.0.1:46959 => 127.0.0.1/127.0.0.1:24767] [junit] 2016-03-04 05:09:30,940 [myid:] - INFO [New I/O worker #9374:ZooKeeperServer@969] - Client attempting to renew session 0x101079b250c at /127.0.0.1:46959 [junit] 2016-03-04 05:09:30,941 [myid:] - INFO [New I/O worker #9374:ZooKeeperServer@678] - Established session 0x101079b250c with negotiated timeout 6000 for client /127.0.0.1:46959 [junit] 2016-03-04 05:09:30,944 [myid:] - INFO [New I/O worker #9277:ClientCnxn$SendThread@1408] - Session establishment complete on server 127.0.0.1/127.0.0.1:24767, sessionid = 0x101079b250c, negotiated timeout = 6000 [junit] 2016-03-04 05:09:30,946 [myid:] - INFO [SyncThread:0:FileTxnLog@200] - Creating new log file: log.7 [junit] 2016-03-04 05:09:31,955 [myid:] - INFO [ProcessThread(sid:0 cport:24767)::PrepRequestProcessor@649] - Processed session termination for sessionid: 0x101079b250c [junit] 2016-03-04 05:09:31,957 [myid:] - INFO [SyncThread:0:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port24767,name1=Connections,name2=127.0.0.1,name3=0x101079b250c] [junit] 2016-03-04 05:09:31,957 [myid:] - INFO [New I/O worker #9277:ClientCnxnSocketNetty$ZKClientHandler@377] - channel is disconnected: [id: 0xffdef488, /127.0.0.1:46959 :> 127.0.0.1/127.0.0.1:24767] [junit] 2016-03-04 05:09:31,957 [myid:] - INFO [New I/O worker #9277:ClientCnxnSocketNetty@201] - channel is told closing [junit] 2016-03-04 05:09:31,957 [myid:] - INFO [main:ClientCnxnSocketNetty@201] - channel is told closing [junit] 2016-03-04 05:09:31,957 [myid:] - INFO [main:ZooKeeper@1110] - Session: 0x101079b250c closed [junit] 2016-03-04 05:09:31,958 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 84155 [junit] 2016-03-04 05:09:31,958 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 86 [junit] 2016-03-04 05:09:31,958 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD testWatcherAutoResetWithLocal [junit] 2016-03-04 05:09:31,958 [myid:] - INFO [main:ClientBase@537] - tearDown starting [junit] 2016-03-04 05:09:31,958 [myid:] - INFO [main:ClientBase@507] - STOPPING server [junit] 2016-03-04 05:09:31,959 [myid:] - INFO [main:NettyServerCnxnFactory@463] - shutdown called 0.0.0.0/0.0.0.0:24767 [junit] 2016-03-04 05:09:31,959 [myid:] - WARN [New I/O worker #9374:NettyServerCnxnFactory$CnxnChannelHandler@141] - Exception caught [id: 0xbcf881f3, /127.0.0.1:46959 :> /127.0.0.1:24767] EXCEPTION: java.nio.channels.ClosedChannelException [junit] java.nio.channels.ClosedChannelException [junit] at org.jboss.netty.channel.socket.nio.AbstractNioWorker.cleanUpWriteBuffer(AbstractNioWorker.java:434) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioWorker.close(AbstractNioWorker.java:374) [junit] at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleAcceptedSocket(NioServerSocketPipelineSink.java:81) [junit] at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:36) [junit] at org.jboss.netty.channel.Channels.close(Channels.java:812) [junit] at org.jboss.netty.channel.AbstractChannel.close(AbstractChannel.java:197) [junit] at org.apache.zookeeper.server.NettyServerCnxn.close(NettyServerCnxn.java:111) [junit] at org.apache.zookeeper.server.NettyServerCnxn.sendBuffer(NettyServerCnxn.java:215) [junit] at org.apache.zookeeper.server.NettyServerCnxn.sendCloseSession(NettyServerCnxn.java:441) [junit] at org.apache.zookeeper.server.FinalRequestProcessor.processRequest(FinalRequestProcessor.java:472) [junit] at org.apache.zookeeper.server.SyncRequestProcessor.flush(SyncRequestProcessor.java:182) [junit] at org.apache.zookeeper.server.SyncRequestProcessor.run(SyncRequestProcessor.java:113) [junit] 2016-03-04 05:09:31,958 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@543] - EventThread shut down for session: 0x101079b250c [junit] 2016-03-04 05:09:31,967 [myid:] - INFO [main:ZooKeeperServer@498] - shutting down [junit] 2016-03-04 05:09:31,967 [myid:] - INFO [main:SessionTrackerImp
ZooKeeper-trunk-WinVS2008 - Build # 1882 - Failure
See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/1882/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 1537 lines...] [ivy:retrieve] downloading http://repo1.maven.org/maven2/io/netty/netty/3.7.0.Final/netty-3.7.0.Final.jar ... [ivy:retrieve] .. (1180kB) [ivy:retrieve] .. (0kB) [ivy:retrieve] [SUCCESSFUL ] io.netty#netty;3.7.0.Final!netty.jar (140ms) [ivy:retrieve] downloading http://repo1.maven.org/maven2/net/java/dev/javacc/javacc/5.0/javacc-5.0.jar ... [ivy:retrieve] . (291kB) [ivy:retrieve] .. (0kB) [ivy:retrieve] [SUCCESSFUL ] net.java.dev.javacc#javacc;5.0!javacc.jar (110ms) [ivy:retrieve] :: resolution report :: resolve 7094ms :: artifacts dl 1344ms - | |modules|| artifacts | | conf | number| search|dwnlded|evicted|| number|dwnlded| - | default | 10 | 10 | 10 | 0 || 10 | 10 | - [ivy:retrieve] :: retrieving :: org.apache.zookeeper#zookeeper [ivy:retrieve] confs: [default] [ivy:retrieve] 10 artifacts copied, 0 already retrieved (3561kB/16ms) generate_jute_parser: [mkdir] Created dir: f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\build\jute_compiler\org\apache\jute\compiler\generated [ivy:artifactproperty] DEPRECATED: 'ivy.conf.file' is deprecated, use 'ivy.settings.file' instead [ivy:artifactproperty] :: loading settings :: file = f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\ivysettings.xml [move] Moving 1 file to f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\build\lib [javacc] Java Compiler Compiler Version 5.0 (Parser Generator) [javacc] (type "javacc" with no arguments for help) [javacc] Reading from file f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\java\main\org\apache\jute\compiler\generated\rcc.jj . . . [javacc] File "TokenMgrError.java" does not exist. Will create one. [javacc] File "ParseException.java" does not exist. Will create one. [javacc] File "Token.java" does not exist. Will create one. [javacc] File "SimpleCharStream.java" does not exist. Will create one. [javacc] Parser generated successfully. jute: [javac] Compiling 39 source files to f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\build\classes compile_jute_uptodate: compile_jute: [mkdir] Created dir: f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\java\generated [mkdir] Created dir: f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\generated [java] ../../zookeeper.jute Parsed Successfully [java] ../../zookeeper.jute Parsed Successfully [touch] Creating f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\java\generated\.generated BUILD SUCCESSFUL Total time: 16 seconds [ZooKeeper-trunk-WinVS2008] $ cmd /c call C:\Windows\TEMP\hudson5875640629762534052.bat f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008>set ZOOKEEPER_HOME=f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008>msbuild trunk/src/c/zookeeper.sln /p:Configuration=Release 'msbuild' is not recognized as an internal or external command, operable program or batch file. f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008>exit 9009 Build step 'Execute Windows batch command' marked build as failure Email was triggered for: Failure - Any Sending email for trigger: Failure - Any ### ## FAILED TESTS (if any) ## No tests ran.
ZooKeeper_branch35_jdk8 - Build # 1 - Failure
See https://builds.apache.org/job/ZooKeeper_branch35_jdk8/1/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 371255 lines...] [junit] 2016-03-04 05:00:03,463 [myid:] - INFO [New I/O worker #9374:ZooKeeperServer@969] - Client attempting to renew session 0x10107927548 at /127.0.0.1:32898 [junit] 2016-03-04 05:00:03,464 [myid:] - INFO [New I/O worker #9374:ZooKeeperServer@678] - Established session 0x10107927548 with negotiated timeout 6000 for client /127.0.0.1:32898 [junit] 2016-03-04 05:00:03,465 [myid:] - INFO [New I/O worker #9277:ClientCnxn$SendThread@1408] - Session establishment complete on server 127.0.0.1/127.0.0.1:13995, sessionid = 0x10107927548, negotiated timeout = 6000 [junit] 2016-03-04 05:00:03,467 [myid:] - INFO [SyncThread:0:FileTxnLog@200] - Creating new log file: log.7 [junit] 2016-03-04 05:00:04,471 [myid:] - INFO [ProcessThread(sid:0 cport:13995)::PrepRequestProcessor@649] - Processed session termination for sessionid: 0x10107927548 [junit] 2016-03-04 05:00:04,473 [myid:] - INFO [New I/O worker #9277:ClientCnxnSocketNetty$ZKClientHandler@377] - channel is disconnected: [id: 0x5d048185, /127.0.0.1:32898 :> 127.0.0.1/127.0.0.1:13995] [junit] 2016-03-04 05:00:04,473 [myid:] - INFO [New I/O worker #9277:ClientCnxnSocketNetty@201] - channel is told closing [junit] 2016-03-04 05:00:04,473 [myid:] - INFO [main:ClientCnxnSocketNetty@201] - channel is told closing [junit] 2016-03-04 05:00:04,473 [myid:] - INFO [main:ZooKeeper@1110] - Session: 0x10107927548 closed [junit] 2016-03-04 05:00:04,473 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 38607 [junit] 2016-03-04 05:00:04,474 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 86 [junit] 2016-03-04 05:00:04,474 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD testWatcherAutoResetWithLocal [junit] 2016-03-04 05:00:04,474 [myid:] - INFO [main:ClientBase@537] - tearDown starting [junit] 2016-03-04 05:00:04,474 [myid:] - INFO [main:ClientBase@507] - STOPPING server [junit] 2016-03-04 05:00:04,474 [myid:] - INFO [main:NettyServerCnxnFactory@463] - shutdown called 0.0.0.0/0.0.0.0:13995 [junit] 2016-03-04 05:00:04,474 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@543] - EventThread shut down for session: 0x10107927548 [junit] 2016-03-04 05:00:04,476 [myid:] - WARN [New I/O worker #9374:NettyServerCnxnFactory$CnxnChannelHandler@141] - Exception caught [id: 0x3d04b1a6, /127.0.0.1:32898 :> /127.0.0.1:13995] EXCEPTION: java.nio.channels.ClosedChannelException [junit] java.nio.channels.ClosedChannelException [junit] at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:270) [junit] at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:461) [junit] at org.jboss.netty.channel.socket.nio.SocketSendBufferPool$UnpooledSendBuffer.transferTo(SocketSendBufferPool.java:203) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioWorker.write0(AbstractNioWorker.java:202) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioWorker.writeFromTaskLoop(AbstractNioWorker.java:152) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioChannel$WriteTask.run(AbstractNioChannel.java:335) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:366) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:290) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:90) [junit] at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) [junit] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [junit] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [junit] at java.lang.Thread.run(Thread.java:745) [junit] 2016-03-04 05:00:04,477 [myid:] - INFO [SyncThread:0:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port13995,name1=Connections,name2=127.0.0.1,name3=0x10107927548] [junit] 2016-03-04 05:00:04,485 [myid:] - INFO [main:ZooKeeperServer@498] - shutting down [junit] 2016-03-04 05:00:04,485 [myid:] - INFO [main:SessionTrackerImpl@232] - Shutting down [junit] 2016-03-04 05:00:04,485 [myid:] - INFO [main:PrepRequestProcessor@967] - Shutting down [junit] 2016-03-04 05:00:04,487 [myid:] - INFO [main:SyncRequestProcessor@191] - Shutting down [junit] 2016-03-04 05:00:04,487 [myid:] - INFO [ProcessThread(sid:0 cport:13995)::PrepRequestProcessor@154] - PrepRequestProcessor exited loop
Re: 3.5.2-alpha Release Planning
Also the flakey tests on jenkins are really painful. It's seems like it's gotten worse of late and it's more flakey than usual. Just me? Notice that we're missing a number of "standard" jobs for branch 3.5, I'll try to get the "standard" jobs setup asap. Patrick On Thu, Mar 3, 2016 at 4:28 PM, Patrick Hunt wrote: > Looks like Flavio reopened this one, it's another license issue - > needs to get into 3.5.2 and trunk: > > https://issues.apache.org/jira/browse/ZOOKEEPER-2235 > > Patrick > > On Thu, Mar 3, 2016 at 3:56 PM, Patrick Hunt wrote: >> FYI you can see my ZooKeeper Jira dashboard here: http://bit.ly/1UCURuM >> >> It's pretty useful to see overall project status as well as the in >> progress releases. >> >> Patrick >> >> On Thu, Mar 3, 2016 at 3:04 PM, Crowder Tim >> wrote: >>> Hi Chris- >>> >>> Any chance of getting ZOOKEEPER-1525 in there? >>> >>> Thanks! >>> .timrc >>> >>> >>> On Thu, 3/3/16, Chris Nauroth wrote: >>> >>> Subject: 3.5.2-alpha Release Planning >>> To: "dev@zookeeper.apache.org" >>> Date: Thursday, March 3, 2016, 10:12 AM >>> >>> This link shows issues currently >>> fixed for 3.5.2: >>> >>> https://s.apache.org/n2C6 >>> >>> This link shows issues still open targeted to 3.5.2: >>> >>> https://s.apache.org/nORc >>> >>> I had been planning to kick off the release process for a >>> 3.5.2-alpha >>> candidate right around now, but after reviewing these lists, >>> I'm inclined >>> to defer it a few more weeks while we work down more >>> blockers. What do >>> others think? >>> >>> On a related note, thank you to Patrick for the recent JIRA >>> clean-up. >>> >>> --Chris Nauroth
[jira] [Commented] (ZOOKEEPER-2266) Integrate JaCoCo Coverage Library
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179290#comment-15179290
]
Patrick Hunt commented on ZOOKEEPER-2266:
-
I think you mean to have jacoco enabled=false by default? See how we run the
"clover" target by passing an argument (it's in the clover build.xml xml doc
string)
I'm not familiar with jacoco I'm afraid. However it looks like it differs from
clover in that it does (prefers) online instrumentation (clover does offline
class file instrumentation). As a result you needed to update the junit.run-
targets to add jacoco-init as a dependency. This will result in pulling the
jacoco jars when running the unit tests. I think what you want to do is add a
dependency in between junit and jacoco-init that checks whether jacoco is
enabled. If it's not you shouldn't run the init code. If it is you should. I
believe this will result in jacoco jars not being pulled when jacoco is not
enabled, but you'll need to try it and verify.
can you replace stuff like this
with a fileset? (see other examples in the build.xml file) or at least move the
version to a property if that's not possible
PS: you need to replace the tabs with spaces and fix the indentation. (we don't
allow tabs for indentation)
> Integrate JaCoCo Coverage Library
> -
>
> Key: ZOOKEEPER-2266
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2266
> Project: ZooKeeper
> Issue Type: Improvement
> Components: tests
>Reporter: Akihiro Suda
>Assignee: Akihiro Suda
>Priority: Minor
> Attachments: ZOOKEEPER-2266-v1.patch, ZOOKEEPER-2266-v2.patch,
> ZOOKEEPER-2266-v3.patch, jacoco-report-example.zip
>
>
> I would like to propose integration of
> [JaCoCo|http://www.eclemma.org/jacoco/] coverage library with ZooKeeper.
> h4. Purposes
> - To find poorly covered methods, and improve JUnit testcases to cover them
> - To estimate causes of flaky testcases (e.g. ZOOKEEPER-2080,
> ZOOKEEPER-2252, ZOOKEEPER-1868) by comparing reports from succeeded
> experiments and failed ones (I'm recently interested in how we can
> systematically realize this.)
> h4. Advantages of JaCoCo
> - Support recent JDKs (including JDK 8)
> - Low overhead
> - Released under EPL
> -- Note: cobertura has been removed from the code base because it is
> released under GPL ( ZOOKEEPER-75,
> http://www.apache.org/legal/resolved.html#category-x )
> h4. Usage
> {panel}
> $ ant test #(plus optionally, -Dtestcase=.. -Dtest.method=..)
> $ ant jacoco-report
> $ x-www-browser build/test/jacoco/reports/index.html &
> {panel}
> Example: jacoco-report-example.zip
> h4. Possible Future Work
> - Integrate to Jenkins buildbot so that we can check coverage after each of
> builds
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Release planning and ZOOKEEPER-1604 - "remove rpm/deb/... packaging"
Just echoing my own comments on ZOOKEEPER-1604 here, I am +1 for the decision to remove packaging from the ZooKeeper project itself and instead declare a reliance on BigTop for packaging concerns. I stated my full rationale in the comments on ZOOKEEPER-1604. --Chris Nauroth On 3/3/16, 7:37 PM, "Patrick Hunt" wrote: >As part of the release planning I wanted to call attention to this JIRA: >https://issues.apache.org/jira/browse/ZOOKEEPER-1604 >I recently committed this for 3.5/trunk thinking it wasn't going to be >a big deal. However there are some recent (today) comments to the >contrary. Please take a look. If you feel strongly, or not, it would >be good to get some more comments on that jira. I committed the patch, >I personally think it's the right thing to do, but I'm happy to revert >the change if someone is interested in actively working in this area - >we need a committer as champion though, otherwise the work is unlikely >to get reviewed/committed. > >Patrick >
[jira] [Commented] (ZOOKEEPER-2266) Integrate JaCoCo Coverage Library
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179275#comment-15179275
]
Hadoop QA commented on ZOOKEEPER-2266:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12791389/ZOOKEEPER-2266-v3.patch
against trunk revision 1733525.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
-1 findbugs. The patch appears to introduce 1 new Findbugs (version 2.0.3)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3081//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3081//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3081//console
This message is automatically generated.
> Integrate JaCoCo Coverage Library
> -
>
> Key: ZOOKEEPER-2266
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2266
> Project: ZooKeeper
> Issue Type: Improvement
> Components: tests
>Reporter: Akihiro Suda
>Assignee: Akihiro Suda
>Priority: Minor
> Attachments: ZOOKEEPER-2266-v1.patch, ZOOKEEPER-2266-v2.patch,
> ZOOKEEPER-2266-v3.patch, jacoco-report-example.zip
>
>
> I would like to propose integration of
> [JaCoCo|http://www.eclemma.org/jacoco/] coverage library with ZooKeeper.
> h4. Purposes
> - To find poorly covered methods, and improve JUnit testcases to cover them
> - To estimate causes of flaky testcases (e.g. ZOOKEEPER-2080,
> ZOOKEEPER-2252, ZOOKEEPER-1868) by comparing reports from succeeded
> experiments and failed ones (I'm recently interested in how we can
> systematically realize this.)
> h4. Advantages of JaCoCo
> - Support recent JDKs (including JDK 8)
> - Low overhead
> - Released under EPL
> -- Note: cobertura has been removed from the code base because it is
> released under GPL ( ZOOKEEPER-75,
> http://www.apache.org/legal/resolved.html#category-x )
> h4. Usage
> {panel}
> $ ant test #(plus optionally, -Dtestcase=.. -Dtest.method=..)
> $ ant jacoco-report
> $ x-www-browser build/test/jacoco/reports/index.html &
> {panel}
> Example: jacoco-report-example.zip
> h4. Possible Future Work
> - Integrate to Jenkins buildbot so that we can check coverage after each of
> builds
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Failed: ZOOKEEPER-2266 PreCommit Build #3081
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2266 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3081/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 377998 lines...] [exec] -1 tests included. The patch doesn't appear to include any new or modified tests. [exec] Please justify why no new tests are needed for this patch. [exec] Also please list what manual steps were performed to verify this patch. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] -1 findbugs. The patch appears to introduce 1 new Findbugs (version 2.0.3) warnings. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. [exec] [exec] +1 core tests. The patch passed core unit tests. [exec] [exec] +1 contrib tests. The patch passed contrib unit tests. [exec] [exec] Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3081//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3081//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3081//console [exec] [exec] This message is automatically generated. [exec] [exec] [exec] == [exec] == [exec] Adding comment to Jira. [exec] == [exec] == [exec] [exec] [exec] Comment added. [exec] 07a6956f2b06a50b205f920c37cb1ce1215d06f4 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1646: exec returned: 2 Total time: 14 minutes 18 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-2266 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## All tests passed
Release planning and ZOOKEEPER-1604 - "remove rpm/deb/... packaging"
As part of the release planning I wanted to call attention to this JIRA: https://issues.apache.org/jira/browse/ZOOKEEPER-1604 I recently committed this for 3.5/trunk thinking it wasn't going to be a big deal. However there are some recent (today) comments to the contrary. Please take a look. If you feel strongly, or not, it would be good to get some more comments on that jira. I committed the patch, I personally think it's the right thing to do, but I'm happy to revert the change if someone is interested in actively working in this area - we need a committer as champion though, otherwise the work is unlikely to get reviewed/committed. Patrick
[jira] [Commented] (ZOOKEEPER-1604) remove rpm/deb/... packaging
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179195#comment-15179195 ] Patrick Hunt commented on ZOOKEEPER-1604: - Here are a couple things to also consider. Maybe the patches aren't getting reviewed because we (committers) don't have the expertise to review, nor the infrastructure to test the changes. (let's assume we have the time, although based on the PA load I don't think that's true). From what I saw folks were hesitant to move these forward w/o understanding and validating the impact. You can get ZooKeeper packages from Cloudera, certainly, but you can also get them from Hortonworks, or from Canonical (deb) http://packages.ubuntu.com/search?keywords=zookeeper or RPMs http://rpmfind.net/linux/rpm2html/search.php?query=zookeeper etc... The Hadoop ecosystem has moved forward. There just isn't the value in a project trying to maintain it's own packages when others are already doing so. Apache already has it's own packaging infrastructure that lots of folks are using and contributing to - Apache Bigtop. I'd rather see the investment go there. > remove rpm/deb/... packaging > > > Key: ZOOKEEPER-1604 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1604 > Project: ZooKeeper > Issue Type: Task > Components: build >Affects Versions: 3.3.0 >Reporter: Patrick Hunt >Assignee: Chris Nauroth > Fix For: 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-1604.001.patch, ZOOKEEPER-1604.patch > > > Remove rpm/deb/... packaging from our source repo. Now that BigTop is > available and fully supporting ZK it's no longer necessary for us to attempt > to include this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2266) Integrate JaCoCo Coverage Library
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akihiro Suda updated ZOOKEEPER-2266:
Attachment: ZOOKEEPER-2266-v3.patch
> Integrate JaCoCo Coverage Library
> -
>
> Key: ZOOKEEPER-2266
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2266
> Project: ZooKeeper
> Issue Type: Improvement
> Components: tests
>Reporter: Akihiro Suda
>Assignee: Akihiro Suda
>Priority: Minor
> Attachments: ZOOKEEPER-2266-v1.patch, ZOOKEEPER-2266-v2.patch,
> ZOOKEEPER-2266-v3.patch, jacoco-report-example.zip
>
>
> I would like to propose integration of
> [JaCoCo|http://www.eclemma.org/jacoco/] coverage library with ZooKeeper.
> h4. Purposes
> - To find poorly covered methods, and improve JUnit testcases to cover them
> - To estimate causes of flaky testcases (e.g. ZOOKEEPER-2080,
> ZOOKEEPER-2252, ZOOKEEPER-1868) by comparing reports from succeeded
> experiments and failed ones (I'm recently interested in how we can
> systematically realize this.)
> h4. Advantages of JaCoCo
> - Support recent JDKs (including JDK 8)
> - Low overhead
> - Released under EPL
> -- Note: cobertura has been removed from the code base because it is
> released under GPL ( ZOOKEEPER-75,
> http://www.apache.org/legal/resolved.html#category-x )
> h4. Usage
> {panel}
> $ ant test #(plus optionally, -Dtestcase=.. -Dtest.method=..)
> $ ant jacoco-report
> $ x-www-browser build/test/jacoco/reports/index.html &
> {panel}
> Example: jacoco-report-example.zip
> h4. Possible Future Work
> - Integrate to Jenkins buildbot so that we can check coverage after each of
> builds
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2266) Integrate JaCoCo Coverage Library
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179183#comment-15179183
]
Akihiro Suda commented on ZOOKEEPER-2266:
-
[~phunt]
Thank you for the comment.
I update the patch (based on JaCoCo v0.7.6): ZOOKEEPER-2266-v3.patch.
The new patch doesn't contain the license file, but unfortunately I could not
find how to ensure the lib is only pulled when a jacoco target is executed,
without complicating the xml.
The lib is small, so can we pull the lib for all the test targets?
{panel}
$ du -hs
252Kbuild/test/lib/org.jacoco.agent-0.7.6.201602180812.jar
40K build/test/lib/org.jacoco.ant-0.7.6.201602180812.jar
136Kbuild/test/lib/org.jacoco.core-0.7.6.201602180812.jar
140Kbuild/test/lib/org.jacoco.report-0.7.6.201602180812.jar
372Kbuild/test/lib/asm-debug-all-5.0.4.jar
{panel}
I will try again if needed.
> Integrate JaCoCo Coverage Library
> -
>
> Key: ZOOKEEPER-2266
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2266
> Project: ZooKeeper
> Issue Type: Improvement
> Components: tests
>Reporter: Akihiro Suda
>Assignee: Akihiro Suda
>Priority: Minor
> Attachments: ZOOKEEPER-2266-v1.patch, ZOOKEEPER-2266-v2.patch,
> jacoco-report-example.zip
>
>
> I would like to propose integration of
> [JaCoCo|http://www.eclemma.org/jacoco/] coverage library with ZooKeeper.
> h4. Purposes
> - To find poorly covered methods, and improve JUnit testcases to cover them
> - To estimate causes of flaky testcases (e.g. ZOOKEEPER-2080,
> ZOOKEEPER-2252, ZOOKEEPER-1868) by comparing reports from succeeded
> experiments and failed ones (I'm recently interested in how we can
> systematically realize this.)
> h4. Advantages of JaCoCo
> - Support recent JDKs (including JDK 8)
> - Low overhead
> - Released under EPL
> -- Note: cobertura has been removed from the code base because it is
> released under GPL ( ZOOKEEPER-75,
> http://www.apache.org/legal/resolved.html#category-x )
> h4. Usage
> {panel}
> $ ant test #(plus optionally, -Dtestcase=.. -Dtest.method=..)
> $ ant jacoco-report
> $ x-www-browser build/test/jacoco/reports/index.html &
> {panel}
> Example: jacoco-report-example.zip
> h4. Possible Future Work
> - Integrate to Jenkins buildbot so that we can check coverage after each of
> builds
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1604) remove rpm/deb/... packaging
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179103#comment-15179103 ] Eric Yang commented on ZOOKEEPER-1604: -- If ZOOKEEPER-2007 was committed, then ZOOKEEPER-2275 would not exist. Evidently, There are people that are willing to provide patch for packaging issues. Instead, ZOOKEEPER-2007 patch were left without review and code became stale. (Code did not apply due to pre-commit test did not verify patch depth, not the patch.) BigTop has some security issues, including non-uniform uid/gid generation on cluster, and including security vulnerable packages. I am only presenting facts for others to consider. It seems like it's a few steps backward because BigTop project create interlocks of open source projects instead of allow individual project to evolve on their own pace. Ex-Cloudera developers had made some poor choices in BigTop project direction, rather than allowing other projects to evolve. Granted that this is my opinion, and I respect yours. Good luck with BigTop. > remove rpm/deb/... packaging > > > Key: ZOOKEEPER-1604 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1604 > Project: ZooKeeper > Issue Type: Task > Components: build >Affects Versions: 3.3.0 >Reporter: Patrick Hunt >Assignee: Chris Nauroth > Fix For: 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-1604.001.patch, ZOOKEEPER-1604.patch > > > Remove rpm/deb/... packaging from our source repo. Now that BigTop is > available and fully supporting ZK it's no longer necessary for us to attempt > to include this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
ZooKeeper_branch34 - Build # 1447 - Failure
See https://builds.apache.org/job/ZooKeeper_branch34/1447/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 219349 lines...] [junit] 2016-03-04 01:22:33,041 [myid:] - INFO [main:JMXEnv@250] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11221 [junit] 2016-03-04 01:22:33,041 [myid:] - INFO [main:ClientBase@490] - STOPPING server [junit] 2016-03-04 01:22:33,041 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - NIOServerCnxn factory exited run method [junit] 2016-03-04 01:22:33,041 [myid:] - INFO [main:ZooKeeperServer@469] - shutting down [junit] 2016-03-04 01:22:33,042 [myid:] - INFO [main:SessionTrackerImpl@225] - Shutting down [junit] 2016-03-04 01:22:33,042 [myid:] - INFO [main:PrepRequestProcessor@767] - Shutting down [junit] 2016-03-04 01:22:33,042 [myid:] - INFO [main:SyncRequestProcessor@209] - Shutting down [junit] 2016-03-04 01:22:33,042 [myid:] - INFO [ProcessThread(sid:0 cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop! [junit] 2016-03-04 01:22:33,043 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@187] - SyncRequestProcessor exited! [junit] 2016-03-04 01:22:33,043 [myid:] - INFO [main:FinalRequestProcessor@415] - shutdown of request processor complete [junit] 2016-03-04 01:22:33,044 [myid:] - INFO [main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221 [junit] 2016-03-04 01:22:33,045 [myid:] - INFO [main:JMXEnv@146] - ensureOnly:[] [junit] 2016-03-04 01:22:33,046 [myid:] - INFO [main:ClientBase@443] - STARTING server [junit] 2016-03-04 01:22:33,047 [myid:] - INFO [main:ClientBase@364] - CREATING server instance 127.0.0.1:11221 [junit] 2016-03-04 01:22:33,047 [myid:] - INFO [main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2016-03-04 01:22:33,048 [myid:] - INFO [main:ClientBase@339] - STARTING server instance 127.0.0.1:11221 [junit] 2016-03-04 01:22:33,048 [myid:] - INFO [main:ZooKeeperServer@170] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/branch-3.4/build/test/tmp/test1347320816855118756.junit.dir/version-2 snapdir /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/branch-3.4/build/test/tmp/test1347320816855118756.junit.dir/version-2 [junit] 2016-03-04 01:22:33,053 [myid:] - INFO [main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221 [junit] 2016-03-04 01:22:33,054 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - Accepted socket connection from /127.0.0.1:50574 [junit] 2016-03-04 01:22:33,054 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing stat command from /127.0.0.1:50574 [junit] 2016-03-04 01:22:33,055 [myid:] - INFO [Thread-5:NIOServerCnxn$StatCommand@663] - Stat command output [junit] 2016-03-04 01:22:33,055 [myid:] - INFO [Thread-5:NIOServerCnxn@1008] - Closed socket connection for client /127.0.0.1:50574 (no session established for client) [junit] 2016-03-04 01:22:33,056 [myid:] - INFO [main:JMXEnv@229] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2016-03-04 01:22:33,058 [myid:] - INFO [main:JMXEnv@246] - expect:InMemoryDataTree [junit] 2016-03-04 01:22:33,058 [myid:] - INFO [main:JMXEnv@250] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree [junit] 2016-03-04 01:22:33,058 [myid:] - INFO [main:JMXEnv@246] - expect:StandaloneServer_port [junit] 2016-03-04 01:22:33,058 [myid:] - INFO [main:JMXEnv@250] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11221 [junit] 2016-03-04 01:22:33,059 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 31166 [junit] 2016-03-04 01:22:33,059 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20 [junit] 2016-03-04 01:22:33,059 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota [junit] 2016-03-04 01:22:33,059 [myid:] - INFO [main:ClientBase@520] - tearDown starting [junit] 2016-03-04 01:22:33,124 [myid:] - INFO [main:ZooKeeper@684] - Session: 0x1533f3812b6 closed [junit] 2016-03-04 01:22:33,124 [myid:] - INFO [main:ClientBase@490] - STOPPING server [junit] 2016-03-04 01:22:33,124 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for session: 0x1533f3812b6 [junit] 2016-03-04 01:22:33,124 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - NIOServerCnxn factory exited run method [junit] 20
[jira] [Commented] (ZOOKEEPER-1604) remove rpm/deb/... packaging
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179058#comment-15179058 ] Chris Nauroth commented on ZOOKEEPER-1604: -- [~eyang], I'm sorry to hear this change disappoints you. However, we did allow this issue to remain open for discussion for multiple years, with a lot of the discussion happening in the past 10 months. Based on past history, we have not had success maintaining packaging infrastructure within the ZooKeeper project itself. (It has been broken at various times without anyone noticing for a long time.) Many projects have externalized their packaging infrastructure to BigTop. We felt we had reached a consensus decision that the overall best choice for the project was to remove our own packaging infrastructure. Patrick and I and others are in agreement about this change, even though we don't share a common employer. We are trying our best to act in a way that benefits as much of the Apache community as possible. Unfortunately, any resolution of this issue is likely to be disappointing to someone. Sometimes compromise is necessary. I hope you can reconsider using BigTop. Would you consider raising your security concern with the BigTop community? > remove rpm/deb/... packaging > > > Key: ZOOKEEPER-1604 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1604 > Project: ZooKeeper > Issue Type: Task > Components: build >Affects Versions: 3.3.0 >Reporter: Patrick Hunt >Assignee: Chris Nauroth > Fix For: 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-1604.001.patch, ZOOKEEPER-1604.patch > > > Remove rpm/deb/... packaging from our source repo. Now that BigTop is > available and fully supporting ZK it's no longer necessary for us to attempt > to include this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1604) remove rpm/deb/... packaging
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179060#comment-15179060 ] Patrick Hunt commented on ZOOKEEPER-1604: - Hi [~eyang], I didn't mean to exclude anyone. Based on my reading of the recent comments it seemed like the questions had been answered, and we had reached consensus, e.g. Ralph's "I've come around on this issue" and comments from Chris and others. A patch had been posted (not by me) and no negative comments have come in in over six months. I also feel that your comments re Cloudera are unfair to me. My main goal here was just to clean things up and move forward. However you're entitled to your opinion. Additionally this is consistent with what a number of other components (Hadoop) have done over time. Our packaging was created before Bigtop existed, a number of issues have been reported but not resolved, and it seemed like it was causing more problems than it solved. e.g. Chris's comment "ZOOKEEPER-2275 is another new incoming issue where the presence of broken rpm packaging code in the build has caused confusion." EOD we just don't have community available to support packaging, we barely have enough folks to address issues found with the service itself, and while there may have been "interest" there unfortunately hasn't been enough "action". Wouldn't it make more sense to focus on the Bigtop packaging rather than duplicate it here, poorly? > remove rpm/deb/... packaging > > > Key: ZOOKEEPER-1604 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1604 > Project: ZooKeeper > Issue Type: Task > Components: build >Affects Versions: 3.3.0 >Reporter: Patrick Hunt >Assignee: Chris Nauroth > Fix For: 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-1604.001.patch, ZOOKEEPER-1604.patch > > > Remove rpm/deb/... packaging from our source repo. Now that BigTop is > available and fully supporting ZK it's no longer necessary for us to attempt > to include this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ZOOKEEPER-1743) Chocolatey package for automating Zookeeper installation in Windows
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt resolved ZOOKEEPER-1743. - Resolution: Won't Fix Given the packaging has been removed as of ZOOKEEPER-1604 I'm closing this. Please use Bigtop for ZK packaging. (or adding windows packaging support) > Chocolatey package for automating Zookeeper installation in Windows > --- > > Key: ZOOKEEPER-1743 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1743 > Project: ZooKeeper > Issue Type: Improvement > Components: build > Environment: Chocolatey (http://chocolatey.org/) > Windows XP+ >Reporter: Andrew Pennebaker >Priority: Minor > > Ubuntu has "apt-get install zookeeper", simplifying installation in Linux. > Similarly, Mac has "brew install zookeeper". Could we help out our Windows > users by submitting a Chocolatey package? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1604) remove rpm/deb/... packaging
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179013#comment-15179013 ] Eric Yang commented on ZOOKEEPER-1604: -- There are 4 people expressed interest to keep this in source code. Yet, Cloudera push in changes regardless of people protest against this issue. This is a sad day for Apache community. In addition, Bigtop contains /lib/lsb/init-functions which will import redhat-lsb-core which imports exim. Exim is known for common root escalation vulnerability. If you value your cluster security, I would recommend to think twice before using BigTop. > remove rpm/deb/... packaging > > > Key: ZOOKEEPER-1604 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1604 > Project: ZooKeeper > Issue Type: Task > Components: build >Affects Versions: 3.3.0 >Reporter: Patrick Hunt >Assignee: Chris Nauroth > Fix For: 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-1604.001.patch, ZOOKEEPER-1604.patch > > > Remove rpm/deb/... packaging from our source repo. Now that BigTop is > available and fully supporting ZK it's no longer necessary for us to attempt > to include this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: 3.5.2-alpha Release Planning
Looks like Flavio reopened this one, it's another license issue - needs to get into 3.5.2 and trunk: https://issues.apache.org/jira/browse/ZOOKEEPER-2235 Patrick On Thu, Mar 3, 2016 at 3:56 PM, Patrick Hunt wrote: > FYI you can see my ZooKeeper Jira dashboard here: http://bit.ly/1UCURuM > > It's pretty useful to see overall project status as well as the in > progress releases. > > Patrick > > On Thu, Mar 3, 2016 at 3:04 PM, Crowder Tim > wrote: >> Hi Chris- >> >> Any chance of getting ZOOKEEPER-1525 in there? >> >> Thanks! >> .timrc >> >> >> On Thu, 3/3/16, Chris Nauroth wrote: >> >> Subject: 3.5.2-alpha Release Planning >> To: "dev@zookeeper.apache.org" >> Date: Thursday, March 3, 2016, 10:12 AM >> >> This link shows issues currently >> fixed for 3.5.2: >> >> https://s.apache.org/n2C6 >> >> This link shows issues still open targeted to 3.5.2: >> >> https://s.apache.org/nORc >> >> I had been planning to kick off the release process for a >> 3.5.2-alpha >> candidate right around now, but after reviewing these lists, >> I'm inclined >> to defer it a few more weeks while we work down more >> blockers. What do >> others think? >> >> On a related note, thank you to Patrick for the recent JIRA >> clean-up. >> >> --Chris Nauroth
[jira] [Updated] (ZOOKEEPER-2235) License update
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2235: Fix Version/s: 3.5.2 > License update > -- > > Key: ZOOKEEPER-2235 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2235 > Project: ZooKeeper > Issue Type: Bug >Affects Versions: 3.4.6, 3.5.0 >Reporter: Flavio Junqueira >Assignee: Flavio Junqueira >Priority: Blocker > Fix For: 3.4.7, 3.5.1, 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-2235-3.4.patch, ZOOKEEPER-2235-3.5.patch, > ZOOKEEPER-2235.patch, ZOOKEEPER-2235.patch, ZOOKEEPER-2235.patch, > ZOOKEEPER-2235.patch, ZOOKEEPER-2235.patch, notice-dependencies.txt > > > Updating license files and notice.txt as needed. Here is a list of the jars > we are currently bundling with the release artifact with the corresponding > license: > # commons-cli-1.2.jar -- ASF > # javacc.jar -- BSD license > # jline-2.11.jar -- BSD license > # servlet-api-2.5-20081211.jar - CDDL > # jackson-core-asl-1.9.11.jar -- ALv2 > # jetty-6.1.26.jar -- ALv2 > # log4j-1.2.16.jar -- ALv2 > # jackson-mapper-asl-1.9.11.jar -- ALv2 > # jetty-util-6.1.26.jar -- ALv2 > # netty-3.7.0.Final.jar -- ALv2 > # slf4j-log4j12-1.7.5.jar -- MIT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2369) Flushing DataOutputStream before calling toByteArray on the underlying ByteArrayOutputStream
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178994#comment-15178994
]
Patrick Hunt commented on ZOOKEEPER-2369:
-
Makes sense. I don't see why we shouldn't do what you suggest (add the flush).
You see why it's a no-op currently though, right? (and why we haven't seen
issues with this code)
> Flushing DataOutputStream before calling toByteArray on the underlying
> ByteArrayOutputStream
>
>
> Key: ZOOKEEPER-2369
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2369
> Project: ZooKeeper
> Issue Type: Bug
>Reporter: emopers
>Assignee: emopers
>Priority: Minor
>
> In ./src/java/main/org/apache/zookeeper/server/ZooKeeperServer.java
> {code}
> ByteArrayOutputStream baos = new ByteArrayOutputStream();
> BinaryOutputArchive bos = BinaryOutputArchive.getArchive(baos);
> bos.writeInt(-1, "len");
> rsp.serialize(bos, "connect");
> if (!cnxn.isOldClient) {
> bos.writeBool(
> this instanceof ReadOnlyZooKeeperServer, "readOnly");
> }
> baos.close();
> ByteBuffer bb = ByteBuffer.wrap(baos.toByteArray());
> {code}
> BinaryOutputArchive internally uses DataOutputStream as its stream, and when
> a DataOutputStream instance wraps an underlying ByteArrayOutputStream
> instance,
> it is recommended to flush or close the DataOutputStream before invoking the
> underlying instances's toByteArray() . Also, it is a good practice to call
> flush/close explicitly as mentioned for example
> http://stackoverflow.com/questions/2984538/how-to-use-bytearrayoutputstream-and-dataoutputstream-simultaneously-java.
> Moreover, "baos.close()" at second last line is not required as it is no-op
> according to
> [javadoc|http://docs.oracle.com/javase/7/docs/api/java/io/ByteArrayOutputStream.html]
> {quote}
> Closing a ByteArrayOutputStream has no effect. The methods in this class can
> be called after the stream has been closed without generating an IOException.
> {quote}
> The patch is to add flush method on "bos" before calling toByteArray on
> "baos". Similar behavior is also present in the following files:
> ./src/java/main/org/apache/zookeeper/ClientCnxn.java
> ./src/java/main/org/apache/zookeeper/server/ZKDatabase.java
> ./src/java/main/org/apache/zookeeper/server/persistence/Util.java
> ./src/java/main/org/apache/zookeeper/server/NIOServerCnxn.java
> Let me know if this looks good. I can provide patch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2369) Flushing DataOutputStream before calling toByteArray on the underlying ByteArrayOutputStream
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-2369:
Assignee: emopers
> Flushing DataOutputStream before calling toByteArray on the underlying
> ByteArrayOutputStream
>
>
> Key: ZOOKEEPER-2369
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2369
> Project: ZooKeeper
> Issue Type: Bug
>Reporter: emopers
>Assignee: emopers
>Priority: Minor
>
> In ./src/java/main/org/apache/zookeeper/server/ZooKeeperServer.java
> {code}
> ByteArrayOutputStream baos = new ByteArrayOutputStream();
> BinaryOutputArchive bos = BinaryOutputArchive.getArchive(baos);
> bos.writeInt(-1, "len");
> rsp.serialize(bos, "connect");
> if (!cnxn.isOldClient) {
> bos.writeBool(
> this instanceof ReadOnlyZooKeeperServer, "readOnly");
> }
> baos.close();
> ByteBuffer bb = ByteBuffer.wrap(baos.toByteArray());
> {code}
> BinaryOutputArchive internally uses DataOutputStream as its stream, and when
> a DataOutputStream instance wraps an underlying ByteArrayOutputStream
> instance,
> it is recommended to flush or close the DataOutputStream before invoking the
> underlying instances's toByteArray() . Also, it is a good practice to call
> flush/close explicitly as mentioned for example
> http://stackoverflow.com/questions/2984538/how-to-use-bytearrayoutputstream-and-dataoutputstream-simultaneously-java.
> Moreover, "baos.close()" at second last line is not required as it is no-op
> according to
> [javadoc|http://docs.oracle.com/javase/7/docs/api/java/io/ByteArrayOutputStream.html]
> {quote}
> Closing a ByteArrayOutputStream has no effect. The methods in this class can
> be called after the stream has been closed without generating an IOException.
> {quote}
> The patch is to add flush method on "bos" before calling toByteArray on
> "baos". Similar behavior is also present in the following files:
> ./src/java/main/org/apache/zookeeper/ClientCnxn.java
> ./src/java/main/org/apache/zookeeper/server/ZKDatabase.java
> ./src/java/main/org/apache/zookeeper/server/persistence/Util.java
> ./src/java/main/org/apache/zookeeper/server/NIOServerCnxn.java
> Let me know if this looks good. I can provide patch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: 3.5.2-alpha Release Planning
FYI you can see my ZooKeeper Jira dashboard here: http://bit.ly/1UCURuM It's pretty useful to see overall project status as well as the in progress releases. Patrick On Thu, Mar 3, 2016 at 3:04 PM, Crowder Tim wrote: > Hi Chris- > > Any chance of getting ZOOKEEPER-1525 in there? > > Thanks! > .timrc > > > On Thu, 3/3/16, Chris Nauroth wrote: > > Subject: 3.5.2-alpha Release Planning > To: "dev@zookeeper.apache.org" > Date: Thursday, March 3, 2016, 10:12 AM > > This link shows issues currently > fixed for 3.5.2: > > https://s.apache.org/n2C6 > > This link shows issues still open targeted to 3.5.2: > > https://s.apache.org/nORc > > I had been planning to kick off the release process for a > 3.5.2-alpha > candidate right around now, but after reviewing these lists, > I'm inclined > to defer it a few more weeks while we work down more > blockers. What do > others think? > > On a related note, thank you to Patrick for the recent JIRA > clean-up. > > --Chris Nauroth
Re: 3.5.2-alpha Release Planning
Hi Chris- Any chance of getting ZOOKEEPER-1525 in there? Thanks! .timrc On Thu, 3/3/16, Chris Nauroth wrote: Subject: 3.5.2-alpha Release Planning To: "dev@zookeeper.apache.org" Date: Thursday, March 3, 2016, 10:12 AM This link shows issues currently fixed for 3.5.2: https://s.apache.org/n2C6 This link shows issues still open targeted to 3.5.2: https://s.apache.org/nORc I had been planning to kick off the release process for a 3.5.2-alpha candidate right around now, but after reviewing these lists, I'm inclined to defer it a few more weeks while we work down more blockers. What do others think? On a related note, thank you to Patrick for the recent JIRA clean-up. --Chris Nauroth
ZooKeeper_branch35_jdk7 - Build # 435 - Still Failing
See https://builds.apache.org/job/ZooKeeper_branch35_jdk7/435/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 380265 lines...] [exec] Log Message Received: [2016-03-03 22:25:03,437:28509(0x2b91b38f3780):ZOO_INFO@testLogCallbackInit@993: testLogCallbackInit #8] [exec] Log Message Received: [2016-03-03 22:25:03,437:28509(0x2b91b38f3780):ZOO_INFO@testLogCallbackInit@993: testLogCallbackInit #9] [exec] Log Message Received: [2016-03-03 22:25:03,438:28509(0x2b91b38f3780):ZOO_INFO@zookeeper_close@3257: Closing zookeeper sessionId=0x1ffc2cc000e to [127.0.0.1:22181] [exec] ] [exec] : elapsed 1001 : OK [exec] Zookeeper_simpleSystem::testLogCallbackClearLog Message Received: [2016-03-03 22:25:03,438:28509(0x2b91b38f3780):ZOO_INFO@log_env@1027: Client environment:zookeeper.version=zookeeper C client 3.5.1] [exec] Log Message Received: [2016-03-03 22:25:03,438:28509(0x2b91b38f3780):ZOO_INFO@log_env@1031: Client environment:host.name=jenkins-ubuntu-1404-4gb-5d8] [exec] Log Message Received: [2016-03-03 22:25:03,438:28509(0x2b91b38f3780):ZOO_INFO@log_env@1038: Client environment:os.name=Linux] [exec] Log Message Received: [2016-03-03 22:25:03,438:28509(0x2b91b38f3780):ZOO_INFO@log_env@1039: Client environment:os.arch=3.13.0-30-generic] [exec] Log Message Received: [2016-03-03 22:25:03,438:28509(0x2b91b38f3780):ZOO_INFO@log_env@1040: Client environment:os.version=#54-Ubuntu SMP Mon Jun 9 22:45:01 UTC 2014] [exec] Log Message Received: [2016-03-03 22:25:03,438:28509(0x2b91b38f3780):ZOO_INFO@log_env@1048: Client environment:user.name=jenkins] [exec] Log Message Received: [2016-03-03 22:25:03,438:28509(0x2b91b38f3780):ZOO_INFO@log_env@1056: Client environment:user.home=/home/jenkins] [exec] Log Message Received: [2016-03-03 22:25:03,438:28509(0x2b91b38f3780):ZOO_INFO@log_env@1068: Client environment:user.dir=/jenkins/workspace/ZooKeeper_branch35_jdk7/branch-3.5/build/test/test-cppunit] [exec] Log Message Received: [2016-03-03 22:25:03,438:28509(0x2b91b38f3780):ZOO_INFO@zookeeper_init_internal@: Initiating client connection, host=127.0.0.1:22181 sessionTimeout=1 watcher=0x45d2f0 sessionId=0 sessionPasswd= context=0x7fff587828d0 flags=0] [exec] Log Message Received: [2016-03-03 22:25:03,439:28509(0x2b91b5fc5700):ZOO_INFO@check_events@2357: initiated connection to server [127.0.0.1:22181]] [exec] Log Message Received: [2016-03-03 22:25:03,442:28509(0x2b91b5fc5700):ZOO_INFO@check_events@2409: session establishment complete on server [127.0.0.1:22181], sessionId=0x1ffc2cc000f, negotiated timeout=1 ] [exec] : elapsed 1001 : OK [exec] Zookeeper_simpleSystem::testAsyncWatcherAutoReset ZooKeeper server started : elapsed 10527 : OK [exec] Zookeeper_simpleSystem::testDeserializeString : elapsed 0 : OK [exec] Zookeeper_simpleSystem::testFirstServerDown : elapsed 1002 : OK [exec] Zookeeper_simpleSystem::testNullData : elapsed 1026 : OK [exec] Zookeeper_simpleSystem::testIPV6 : elapsed 1004 : OK [exec] Zookeeper_simpleSystem::testCreate : elapsed 1008 : OK [exec] Zookeeper_simpleSystem::testPath : elapsed 1016 : OK [exec] Zookeeper_simpleSystem::testPathValidation : elapsed 1051 : OK [exec] Zookeeper_simpleSystem::testPing : elapsed 17273 : OK [exec] Zookeeper_simpleSystem::testAcl : elapsed 1015 : OK [exec] Zookeeper_simpleSystem::testChroot : elapsed 3041 : OK [exec] Zookeeper_simpleSystem::testAuth ZooKeeper server started ZooKeeper server started : elapsed 31058 : OK [exec] Zookeeper_simpleSystem::testHangingClient : elapsed 1030 : OK [exec] Zookeeper_simpleSystem::testWatcherAutoResetWithGlobal ZooKeeper server started ZooKeeper server started ZooKeeper server started : elapsed 15652 : OK [exec] Zookeeper_simpleSystem::testWatcherAutoResetWithLocal ZooKeeper server started ZooKeeper server started ZooKeeper server started : elapsed 15631 : OK [exec] Zookeeper_simpleSystem::testGetChildren2 : elapsed 1034 : OK [exec] Zookeeper_simpleSystem::testLastZxid : elapsed 4515 : OK [exec] Zookeeper_simpleSystem::testRemoveWatchers ZooKeeper server started : elapsed 4697 : OK [exec] Zookeeper_readOnly::testReadOnly : elapsed 4337 : OK [exec] /jenkins/workspace/ZooKeeper_branch35_jdk7/branch-3.5/src/c/tests/TestReconfig.cc:183: Assertion: equality assertion failed [Expected: 1, Actual : 0] [exec] Failures !!! [exec] Run: 72 Failure total: 1 Failures: 1 Errors: 0 [exec] FAIL: zktest-mt [exec] == [exec] 1 of 2 tests failed [exec] Please report to u...@zookeeper.apache.org [exec] == [exec] make[1]: Leaving directory `/jenkins/workspace/ZooKeeper
ZooKeeper-trunk-solaris - Build # 1075 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-solaris/1075/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 348414 lines...] [junit] 2016-03-03 22:19:01,322 [myid:] - INFO [main:JMXEnv@146] - ensureOnly:[] [junit] 2016-03-03 22:19:01,323 [myid:] - INFO [main:ClientBase@460] - STARTING server [junit] 2016-03-03 22:19:01,323 [myid:] - INFO [main:ClientBase@380] - CREATING server instance 127.0.0.1:11222 [junit] 2016-03-03 22:19:01,323 [myid:] - INFO [main:NIOServerCnxnFactory@673] - Configuring NIO connection handler with 10s sessionless connection timeout, 2 selector thread(s), 16 worker threads, and 64 kB direct buffers. [junit] 2016-03-03 22:19:01,324 [myid:] - INFO [main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222 [junit] 2016-03-03 22:19:01,325 [myid:] - INFO [main:ClientBase@355] - STARTING server instance 127.0.0.1:11222 [junit] 2016-03-03 22:19:01,325 [myid:] - INFO [main:ZooKeeperServer@858] - minSessionTimeout set to 6000 [junit] 2016-03-03 22:19:01,325 [myid:] - INFO [main:ZooKeeperServer@867] - maxSessionTimeout set to 6 [junit] 2016-03-03 22:19:01,325 [myid:] - INFO [main:ZooKeeperServer@156] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test689146592126180556.junit.dir/version-2 snapdir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test689146592126180556.junit.dir/version-2 [junit] 2016-03-03 22:19:01,326 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test689146592126180556.junit.dir/version-2/snapshot.b [junit] 2016-03-03 22:19:01,328 [myid:] - INFO [main:FileTxnSnapLog@298] - Snapshotting: 0xb to /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test689146592126180556.junit.dir/version-2/snapshot.b [junit] 2016-03-03 22:19:01,330 [myid:] - INFO [main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222 [junit] 2016-03-03 22:19:01,330 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:44275 [junit] 2016-03-03 22:19:01,331 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from /127.0.0.1:44275 [junit] 2016-03-03 22:19:01,331 [myid:] - INFO [NIOWorkerThread-1:StatCommand@49] - Stat command output [junit] 2016-03-03 22:19:01,331 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client /127.0.0.1:44275 (no session established for client) [junit] 2016-03-03 22:19:01,331 [myid:] - INFO [main:JMXEnv@228] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2016-03-03 22:19:01,333 [myid:] - INFO [main:JMXEnv@245] - expect:InMemoryDataTree [junit] 2016-03-03 22:19:01,333 [myid:] - INFO [main:JMXEnv@249] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree [junit] 2016-03-03 22:19:01,333 [myid:] - INFO [main:JMXEnv@245] - expect:StandaloneServer_port [junit] 2016-03-03 22:19:01,333 [myid:] - INFO [main:JMXEnv@249] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11222 [junit] 2016-03-03 22:19:01,334 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17701 [junit] 2016-03-03 22:19:01,334 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24 [junit] 2016-03-03 22:19:01,334 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD testQuota [junit] 2016-03-03 22:19:01,334 [myid:] - INFO [main:ClientBase@537] - tearDown starting [junit] 2016-03-03 22:19:01,412 [myid:] - INFO [main:ZooKeeper@1110] - Session: 0x11fbb8e9741 closed [junit] 2016-03-03 22:19:01,412 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@543] - EventThread shut down for session: 0x11fbb8e9741 [junit] 2016-03-03 22:19:01,413 [myid:] - INFO [main:ClientBase@507] - STOPPING server [junit] 2016-03-03 22:19:01,413 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2016-03-03 22:19:01,413 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2016-03-03 22:19:01,414 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] - selector th
Re: 3.5.2-alpha Release Planning
I have noticed a bunch of security jiras recently, we should take care of at least some of these. I think historically we haven't been super good with the security stuff, and it'd be great if we could change it. -Flavio > On 03 Mar 2016, at 18:28, Chris Nauroth wrote: > > I forgot to mention that one issue I consider an absolute must is > ZOOKEEPER-2342: ZooKeeper cannot write logs, because there is no SLF4J > binding available on the runtime classpath. It won't be acceptable to > produce a release where the server side doesn't produce any logging out of > the box unless an admin deploys an extra SLF4J binding jar. The path > forward is to migrate to Log4J 2, but I have not yet found a solution that > perfectly replicates the behavior we had with Log4J 1. If this gets stuck > too much longer, then I'm going to suggest reverting ZOOKEEPER-1371, which > introduced the regression. > > ZOOKEEPER-2024 is in my review queue too for consideration of whether or > not to include in 3.5.2-alpha. > > --Chris Nauroth > > > > > On 3/3/16, 10:18 AM, "Patrick Hunt" wrote: > >> We have 5 PA blockers and 8 PA critical issues. Perhaps we can whittle >> down all/most of these? >> https://issues.apache.org/jira/issues/?filter=12334684 >> Any in particular that folks feel strongly about? >> >> On the flip side it would be good to get a new release out into folks >> hands. Unless we have a regression from 3.5.1 perhaps we should do >> 3.5.2 sooner rather than later? >> >> Alex also made a proposal recently around ZOOKEEPER-2024 that we >> should make a call on. It would be good if the RM (and the rest of the >> community) provided direction. >> >> Patrick >> >> On Thu, Mar 3, 2016 at 10:12 AM, Chris Nauroth >> wrote: >>> This link shows issues currently fixed for 3.5.2: >>> >>> https://s.apache.org/n2C6 >>> >>> This link shows issues still open targeted to 3.5.2: >>> >>> https://s.apache.org/nORc >>> >>> I had been planning to kick off the release process for a 3.5.2-alpha >>> candidate right around now, but after reviewing these lists, I'm >>> inclined >>> to defer it a few more weeks while we work down more blockers. What do >>> others think? >>> >>> On a related note, thank you to Patrick for the recent JIRA clean-up. >>> >>> --Chris Nauroth >>> >> >
[jira] [Commented] (ZOOKEEPER-2373) Licenses section missing from pom file
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178662#comment-15178662
]
Hudson commented on ZOOKEEPER-2373:
---
FAILURE: Integrated in ZooKeeper-trunk #2840 (See
[https://builds.apache.org/job/ZooKeeper-trunk/2840/])
ZOOKEEPER-2373 Licenses section missing from pom file - part 2 missed an added
file (phunt) (phunt:
[http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1733525])
* trunk/src/pom.template
> Licenses section missing from pom file
> --
>
> Key: ZOOKEEPER-2373
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2373
> Project: ZooKeeper
> Issue Type: Improvement
>Reporter: Flavio Junqueira
>Assignee: Patrick Hunt
>Priority: Blocker
> Fix For: 3.4.9, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2373.patch
>
>
> The pom file here:
> https://repo1.maven.org/maven2/org/apache/zookeeper/zookeeper/3.4.8/zookeeper-3.4.8.pom
> should have a section like this:
> {noformat}
>
>
> The Apache Software License, Version 2.0
> http://www.apache.org/licenses/LICENSE-2.0.txt
>
> repo
>
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
ZooKeeper-trunk - Build # 2840 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk/2840/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 387216 lines...] [junit] 2016-03-03 21:35:18,419 [myid:] - INFO [main:ZKTestCase$1@65] - SUCCEEDED testWatcherAutoResetWithLocal [junit] 2016-03-03 21:35:18,419 [myid:] - INFO [main:ZKTestCase$1@60] - FINISHED testWatcherAutoResetWithLocal [junit] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 28.825 sec, Thread: 2, Class: org.apache.zookeeper.test.WatcherTest [junit] 2016-03-03 21:36:31,397 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 24716 [junit] 2016-03-03 21:36:31,397 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 55 [junit] 2016-03-03 21:36:31,397 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD testManyChildWatchersAutoReset [junit] 2016-03-03 21:36:31,397 [myid:] - INFO [main:ClientBase@537] - tearDown starting [junit] 2016-03-03 21:36:31,397 [myid:] - INFO [ProcessThread(sid:0 cport:11225)::PrepRequestProcessor@649] - Processed session termination for sessionid: 0x1014dc06176 [junit] 2016-03-03 21:36:31,405 [myid:] - INFO [NIOWorkerThread-11:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port11225,name1=Connections,name2=127.0.0.1,name3=0x1014dc06176] [junit] 2016-03-03 21:36:31,405 [myid:] - INFO [main:ZooKeeper@1110] - Session: 0x1014dc06176 closed [junit] 2016-03-03 21:36:31,405 [myid:] - INFO [NIOWorkerThread-11:NIOServerCnxn@607] - Closed socket connection for client /127.0.0.1:35609 which had sessionid 0x1014dc06176 [junit] 2016-03-03 21:36:31,405 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@543] - EventThread shut down for session: 0x1014dc06176 [junit] 2016-03-03 21:36:31,406 [myid:] - INFO [ProcessThread(sid:0 cport:11225)::PrepRequestProcessor@649] - Processed session termination for sessionid: 0x1014dc061760001 [junit] 2016-03-03 21:36:31,413 [myid:] - INFO [NIOWorkerThread-24:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port11225,name1=Connections,name2=127.0.0.1,name3=0x1014dc061760001] [junit] 2016-03-03 21:36:31,413 [myid:] - INFO [main:ZooKeeper@1110] - Session: 0x1014dc061760001 closed [junit] 2016-03-03 21:36:31,414 [myid:] - INFO [main:ClientBase@507] - STOPPING server [junit] 2016-03-03 21:36:31,413 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@543] - EventThread shut down for session: 0x1014dc061760001 [junit] 2016-03-03 21:36:31,414 [myid:] - INFO [NIOWorkerThread-24:NIOServerCnxn@607] - Closed socket connection for client /127.0.0.1:35608 which had sessionid 0x1014dc061760001 [junit] 2016-03-03 21:36:31,415 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2016-03-03 21:36:31,422 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11225:NIOServerCnxnFactory$AcceptThread@219] - accept thread exitted run method [junit] 2016-03-03 21:36:31,424 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2016-03-03 21:36:31,424 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2016-03-03 21:36:31,424 [myid:] - INFO [main:ZooKeeperServer@498] - shutting down [junit] 2016-03-03 21:36:31,424 [myid:] - INFO [main:SessionTrackerImpl@232] - Shutting down [junit] 2016-03-03 21:36:31,425 [myid:] - INFO [main:PrepRequestProcessor@967] - Shutting down [junit] 2016-03-03 21:36:31,425 [myid:] - INFO [main:SyncRequestProcessor@191] - Shutting down [junit] 2016-03-03 21:36:31,425 [myid:] - INFO [ProcessThread(sid:0 cport:11225)::PrepRequestProcessor@154] - PrepRequestProcessor exited loop! [junit] 2016-03-03 21:36:31,425 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited! [junit] 2016-03-03 21:36:31,426 [myid:] - INFO [main:FinalRequestProcessor@492] - shutdown of request processor complete [junit] 2016-03-03 21:36:31,426 [myid:] - INFO [main:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port11225,name1=InMemoryDataTree] [junit] 2016-03-03 21:36:31,426 [myid:] - INFO [main:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port11225] [junit] 2016-03-03 21:36:31,427 [myid:] - INFO [main:FourLetterWordMain@85] - connecting to 127.0.0.1 11225 [junit] 2016-03-03 21:36:31,428 [myid:] - INFO [main:JMXEnv@146] - ensureOnly:[] [junit]
ZooKeeper-trunk-jdk8 - Build # 515 - Failure
See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/515/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 397110 lines...] [junit] 2016-03-03 21:34:25,689 [myid:] - INFO [main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222 [junit] 2016-03-03 21:34:25,690 [myid:] - INFO [main:JMXEnv@146] - ensureOnly:[] [junit] 2016-03-03 21:34:25,691 [myid:] - INFO [main:ClientBase@460] - STARTING server [junit] 2016-03-03 21:34:25,691 [myid:] - INFO [main:ClientBase@380] - CREATING server instance 127.0.0.1:11222 [junit] 2016-03-03 21:34:25,691 [myid:] - INFO [main:NIOServerCnxnFactory@673] - Configuring NIO connection handler with 10s sessionless connection timeout, 2 selector thread(s), 32 worker threads, and 64 kB direct buffers. [junit] 2016-03-03 21:34:25,692 [myid:] - INFO [main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222 [junit] 2016-03-03 21:34:25,692 [myid:] - INFO [main:ClientBase@355] - STARTING server instance 127.0.0.1:11222 [junit] 2016-03-03 21:34:25,692 [myid:] - INFO [main:ZooKeeperServer@858] - minSessionTimeout set to 6000 [junit] 2016-03-03 21:34:25,692 [myid:] - INFO [main:ZooKeeperServer@867] - maxSessionTimeout set to 6 [junit] 2016-03-03 21:34:25,692 [myid:] - INFO [main:ZooKeeperServer@156] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test5405604187794043794.junit.dir/version-2 snapdir /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test5405604187794043794.junit.dir/version-2 [junit] 2016-03-03 21:34:25,693 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test5405604187794043794.junit.dir/version-2/snapshot.b [junit] 2016-03-03 21:34:25,695 [myid:] - INFO [main:FileTxnSnapLog@298] - Snapshotting: 0xb to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test5405604187794043794.junit.dir/version-2/snapshot.b [junit] 2016-03-03 21:34:25,697 [myid:] - INFO [main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222 [junit] 2016-03-03 21:34:25,697 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:47137 [junit] 2016-03-03 21:34:25,698 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from /127.0.0.1:47137 [junit] 2016-03-03 21:34:25,698 [myid:] - INFO [NIOWorkerThread-1:StatCommand@49] - Stat command output [junit] 2016-03-03 21:34:25,698 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client /127.0.0.1:47137 (no session established for client) [junit] 2016-03-03 21:34:25,698 [myid:] - INFO [main:JMXEnv@228] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2016-03-03 21:34:25,700 [myid:] - INFO [main:JMXEnv@245] - expect:InMemoryDataTree [junit] 2016-03-03 21:34:25,700 [myid:] - INFO [main:JMXEnv@249] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree [junit] 2016-03-03 21:34:25,700 [myid:] - INFO [main:JMXEnv@245] - expect:StandaloneServer_port [junit] 2016-03-03 21:34:25,700 [myid:] - INFO [main:JMXEnv@249] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11222 [junit] 2016-03-03 21:34:25,700 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 55070 [junit] 2016-03-03 21:34:25,700 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24 [junit] 2016-03-03 21:34:25,701 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD testQuota [junit] 2016-03-03 21:34:25,701 [myid:] - INFO [main:ClientBase@537] - tearDown starting [junit] 2016-03-03 21:34:25,769 [myid:] - INFO [main:ZooKeeper@1110] - Session: 0x1009746b667 closed [junit] 2016-03-03 21:34:25,769 [myid:] - INFO [main:ClientBase@507] - STOPPING server [junit] 2016-03-03 21:34:25,769 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2016-03-03 21:34:25,769 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@543] - EventThread shut down for session: 0x1009746b667 [junit] 2016-03-03 21:34:25,769 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@219] - accept thread exitted run method [junit] 2016-03-03 21:34:25,770 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420
ZooKeeper-trunk-solaris - Build # 1074 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-solaris/1074/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 342446 lines...] [junit] 2016-03-03 19:50:47,162 [myid:] - INFO [main:NIOServerCnxnFactory@673] - Configuring NIO connection handler with 10s sessionless connection timeout, 2 selector thread(s), 16 worker threads, and 64 kB direct buffers. [junit] 2016-03-03 19:50:47,163 [myid:] - INFO [main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222 [junit] 2016-03-03 19:50:47,164 [myid:] - INFO [main:ClientBase@355] - STARTING server instance 127.0.0.1:11222 [junit] 2016-03-03 19:50:47,164 [myid:] - INFO [main:ZooKeeperServer@858] - minSessionTimeout set to 6000 [junit] 2016-03-03 19:50:47,164 [myid:] - INFO [main:ZooKeeperServer@867] - maxSessionTimeout set to 6 [junit] 2016-03-03 19:50:47,164 [myid:] - INFO [main:ZooKeeperServer@156] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test8416421387406115361.junit.dir/version-2 snapdir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test8416421387406115361.junit.dir/version-2 [junit] 2016-03-03 19:50:47,165 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test8416421387406115361.junit.dir/version-2/snapshot.b [junit] 2016-03-03 19:50:47,167 [myid:] - INFO [main:FileTxnSnapLog@298] - Snapshotting: 0xb to /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test8416421387406115361.junit.dir/version-2/snapshot.b [junit] 2016-03-03 19:50:47,169 [myid:] - INFO [main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222 [junit] 2016-03-03 19:50:47,169 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:64003 [junit] 2016-03-03 19:50:47,170 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from /127.0.0.1:64003 [junit] 2016-03-03 19:50:47,170 [myid:] - INFO [NIOWorkerThread-1:StatCommand@49] - Stat command output [junit] 2016-03-03 19:50:47,170 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client /127.0.0.1:64003 (no session established for client) [junit] 2016-03-03 19:50:47,170 [myid:] - INFO [main:JMXEnv@228] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2016-03-03 19:50:47,172 [myid:] - INFO [main:JMXEnv@245] - expect:InMemoryDataTree [junit] 2016-03-03 19:50:47,172 [myid:] - INFO [main:JMXEnv@249] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree [junit] 2016-03-03 19:50:47,172 [myid:] - INFO [main:JMXEnv@245] - expect:StandaloneServer_port [junit] 2016-03-03 19:50:47,172 [myid:] - INFO [main:JMXEnv@249] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11222 [junit] 2016-03-03 19:50:47,172 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17731 [junit] 2016-03-03 19:50:47,173 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24 [junit] 2016-03-03 19:50:47,173 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD testQuota [junit] 2016-03-03 19:50:47,173 [myid:] - INFO [main:ClientBase@537] - tearDown starting [junit] 2016-03-03 19:50:47,252 [myid:] - INFO [main:ZooKeeper@1110] - Session: 0x11fbb06e24f closed [junit] 2016-03-03 19:50:47,252 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@543] - EventThread shut down for session: 0x11fbb06e24f [junit] 2016-03-03 19:50:47,252 [myid:] - INFO [main:ClientBase@507] - STOPPING server [junit] 2016-03-03 19:50:47,252 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2016-03-03 19:50:47,252 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2016-03-03 19:50:47,252 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@219] - accept thread exitted run method [junit] 2016-03-03 19:50:47,252 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2016-03-03 19:50:47,253 [myid:] - INFO [main:ZooKeeperServer@498] - shut
[jira] [Commented] (ZOOKEEPER-2319) UnresolvedAddressException cause the QuorumCnxManager.Listener exit
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178396#comment-15178396
]
Rakesh R commented on ZOOKEEPER-2319:
-
I think this not critical, changing this to {{major}} priority. Please feel
free to change if anyone has different opinion.
> UnresolvedAddressException cause the QuorumCnxManager.Listener exit
> ---
>
> Key: ZOOKEEPER-2319
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2319
> Project: ZooKeeper
> Issue Type: Bug
>Affects Versions: 3.4.6
>Reporter: Zhaohui Yu
> Fix For: 3.4.9, 3.5.2, 3.6.0
>
>
> Given three nodes, the leader on 2, but some issue with this machine, so I
> shutdown this machine, and change the host name to another machine.
> Then I start the node in the new machine, but the new node can not join.
> I found the the 1 and 3's Listener thread exit.
> With the code of Listener's run method:
> I think we should catch UnresolvedAddressException to avoid the Listener exit.
> {noformat}
> @Override
> public void run() {
>
> while((!shutdown) && (numRetries < 3)){
> try {
>// bind and accept
> receiveConnection(client);
>
> } catch (IOException e) {
>
> }
> }
> //
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2319) UnresolvedAddressException cause the QuorumCnxManager.Listener exit
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated ZOOKEEPER-2319:
Priority: Major (was: Critical)
> UnresolvedAddressException cause the QuorumCnxManager.Listener exit
> ---
>
> Key: ZOOKEEPER-2319
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2319
> Project: ZooKeeper
> Issue Type: Bug
>Affects Versions: 3.4.6
>Reporter: Zhaohui Yu
> Fix For: 3.4.9, 3.5.2, 3.6.0
>
>
> Given three nodes, the leader on 2, but some issue with this machine, so I
> shutdown this machine, and change the host name to another machine.
> Then I start the node in the new machine, but the new node can not join.
> I found the the 1 and 3's Listener thread exit.
> With the code of Listener's run method:
> I think we should catch UnresolvedAddressException to avoid the Listener exit.
> {noformat}
> @Override
> public void run() {
>
> while((!shutdown) && (numRetries < 3)){
> try {
>// bind and accept
> receiveConnection(client);
>
> } catch (IOException e) {
>
> }
> }
> //
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
ZooKeeper-trunk - Build # 2839 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk/2839/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 2701 lines...] check-recipes: init: [echo] recipes: queue [mkdir] Created dir: /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/recipes/queue [mkdir] Created dir: /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/recipes/queue/classes [mkdir] Created dir: /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/recipes/queue/test init-recipes: compile: [echo] contrib: queue [javac] /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/src/recipes/build-recipes.xml:103: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Compiling 1 source file to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/recipes/queue/classes jar: [echo] recipes: queue [jar] Building jar: /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/recipes/queue/zookeeper-3.6.0-SNAPSHOT-recipes-queue.jar zookeeperbuildrecipes.package: [echo] recipes: queue [mkdir] Created dir: /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/zookeeper-3.6.0-SNAPSHOT/recipes/queue [copy] Copying 1 file to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/zookeeper-3.6.0-SNAPSHOT/recipes/queue package: [copy] Copying 1 file to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/zookeeper-3.6.0-SNAPSHOT/recipes/queue [mkdir] Created dir: /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/zookeeper-3.6.0-SNAPSHOT/recipes/queue/test [copy] Copying 1 file to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/zookeeper-3.6.0-SNAPSHOT/recipes/queue/test [mkdir] Created dir: /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/zookeeper-3.6.0-SNAPSHOT/recipes/queue/src [copy] Copying 16 files to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/zookeeper-3.6.0-SNAPSHOT/recipes/queue/src [copy] Copying 1 file to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/zookeeper-3.6.0-SNAPSHOT [mkdir] Created dir: /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/zookeeper-3.6.0-SNAPSHOT/dist-maven [copy] Copying 1 file to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/zookeeper-3.6.0-SNAPSHOT/dist-maven [copy] Copying 2 files to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/zookeeper-3.6.0-SNAPSHOT/dist-maven BUILD FAILED /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build.xml:757: impossible convert given ivy file to pom file: java.io.FileNotFoundException: /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/src/pom.template (No such file or directory) from=/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/ivy.xml to=/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/zookeeper-3.6.0-SNAPSHOT/dist-maven/zookeeper-3.6.0-SNAPSHOT.pom Total time: 53 seconds mv: cannot stat 'build/*.tar.gz': No such file or directory mv: cannot stat 'build/test/findbugs': No such file or directory Build Failed Build step 'Execute shell' marked build as failure [FINDBUGS] Skipping publisher since build result is FAILURE [WARNINGS] Skipping publisher since build result is FAILURE Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording fingerprints Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? Publishing Javadoc Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## No tests ran.
[jira] [Commented] (ZOOKEEPER-2379) recent commit broke findbugs qabot check
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178312#comment-15178312 ] Rakesh R commented on ZOOKEEPER-2379: - Thanks [~cnauroth] for the reviews. [~rgs], would be great to see your feedback, thanks! > recent commit broke findbugs qabot check > > > Key: ZOOKEEPER-2379 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2379 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.4.9, 3.5.2, 3.6.0 >Reporter: Patrick Hunt >Assignee: Rakesh R >Priority: Blocker > Fix For: 3.4.9, 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-2379.patch > > > A recent commit seems to have broken findbugs, looks like it's in > ZooKeeperSaslClient > see: > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3075//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: 3.5.2-alpha Release Planning
I forgot to mention that one issue I consider an absolute must is ZOOKEEPER-2342: ZooKeeper cannot write logs, because there is no SLF4J binding available on the runtime classpath. It won't be acceptable to produce a release where the server side doesn't produce any logging out of the box unless an admin deploys an extra SLF4J binding jar. The path forward is to migrate to Log4J 2, but I have not yet found a solution that perfectly replicates the behavior we had with Log4J 1. If this gets stuck too much longer, then I'm going to suggest reverting ZOOKEEPER-1371, which introduced the regression. ZOOKEEPER-2024 is in my review queue too for consideration of whether or not to include in 3.5.2-alpha. --Chris Nauroth On 3/3/16, 10:18 AM, "Patrick Hunt" wrote: >We have 5 PA blockers and 8 PA critical issues. Perhaps we can whittle >down all/most of these? >https://issues.apache.org/jira/issues/?filter=12334684 >Any in particular that folks feel strongly about? > >On the flip side it would be good to get a new release out into folks >hands. Unless we have a regression from 3.5.1 perhaps we should do >3.5.2 sooner rather than later? > >Alex also made a proposal recently around ZOOKEEPER-2024 that we >should make a call on. It would be good if the RM (and the rest of the >community) provided direction. > >Patrick > >On Thu, Mar 3, 2016 at 10:12 AM, Chris Nauroth >wrote: >> This link shows issues currently fixed for 3.5.2: >> >> https://s.apache.org/n2C6 >> >> This link shows issues still open targeted to 3.5.2: >> >> https://s.apache.org/nORc >> >> I had been planning to kick off the release process for a 3.5.2-alpha >> candidate right around now, but after reviewing these lists, I'm >>inclined >> to defer it a few more weeks while we work down more blockers. What do >> others think? >> >> On a related note, thank you to Patrick for the recent JIRA clean-up. >> >> --Chris Nauroth >> >
Re: 3.5.2-alpha Release Planning
We have 5 PA blockers and 8 PA critical issues. Perhaps we can whittle down all/most of these? https://issues.apache.org/jira/issues/?filter=12334684 Any in particular that folks feel strongly about? On the flip side it would be good to get a new release out into folks hands. Unless we have a regression from 3.5.1 perhaps we should do 3.5.2 sooner rather than later? Alex also made a proposal recently around ZOOKEEPER-2024 that we should make a call on. It would be good if the RM (and the rest of the community) provided direction. Patrick On Thu, Mar 3, 2016 at 10:12 AM, Chris Nauroth wrote: > This link shows issues currently fixed for 3.5.2: > > https://s.apache.org/n2C6 > > This link shows issues still open targeted to 3.5.2: > > https://s.apache.org/nORc > > I had been planning to kick off the release process for a 3.5.2-alpha > candidate right around now, but after reviewing these lists, I'm inclined > to defer it a few more weeks while we work down more blockers. What do > others think? > > On a related note, thank you to Patrick for the recent JIRA clean-up. > > --Chris Nauroth >
[jira] [Commented] (ZOOKEEPER-2378) upgrade ivy to recent version
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178289#comment-15178289 ] Hudson commented on ZOOKEEPER-2378: --- FAILURE: Integrated in ZooKeeper-trunk #2838 (See [https://builds.apache.org/job/ZooKeeper-trunk/2838/]) ZOOKEEPER-2378 upgrade ivy to recent version (phunt) (phunt: [http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1733505]) * trunk/build.xml > upgrade ivy to recent version > - > > Key: ZOOKEEPER-2378 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2378 > Project: ZooKeeper > Issue Type: Improvement > Components: build >Affects Versions: 3.4.8, 3.5.1, 3.6.0 >Reporter: Patrick Hunt >Assignee: Patrick Hunt >Priority: Critical > Fix For: 3.4.9, 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-2378.patch > > > 2.4.0 is the current version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2294) Ant target generate-clover-reports is broken
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178290#comment-15178290 ] Hudson commented on ZOOKEEPER-2294: --- FAILURE: Integrated in ZooKeeper-trunk #2838 (See [https://builds.apache.org/job/ZooKeeper-trunk/2838/]) ZOOKEEPER-2294 Ant target generate-clover-reports is broken (charlie via phunt) (phunt: [http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1733499]) * trunk/build.xml > Ant target generate-clover-reports is broken > > > Key: ZOOKEEPER-2294 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2294 > Project: ZooKeeper > Issue Type: Bug > Components: build >Reporter: Charlie Helin >Assignee: Charlie Helin > Fix For: 3.4.9, 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-2294.001.patch > > > It appears that the current implementation of 'generate-clover-reports' is > broken. > # It doesn't define the clover-report task > # The clover-report element is missing the proper clover db reference -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2373) Licenses section missing from pom file
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178291#comment-15178291
]
Hudson commented on ZOOKEEPER-2373:
---
FAILURE: Integrated in ZooKeeper-trunk #2838 (See
[https://builds.apache.org/job/ZooKeeper-trunk/2838/])
ZOOKEEPER-2373 Licenses section missing from pom file (phunt) (phunt:
[http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1733508])
* trunk/build.xml
> Licenses section missing from pom file
> --
>
> Key: ZOOKEEPER-2373
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2373
> Project: ZooKeeper
> Issue Type: Improvement
>Reporter: Flavio Junqueira
>Assignee: Patrick Hunt
>Priority: Blocker
> Fix For: 3.4.9, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2373.patch
>
>
> The pom file here:
> https://repo1.maven.org/maven2/org/apache/zookeeper/zookeeper/3.4.8/zookeeper-3.4.8.pom
> should have a section like this:
> {noformat}
>
>
> The Apache Software License, Version 2.0
> http://www.apache.org/licenses/LICENSE-2.0.txt
>
> repo
>
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
ZooKeeper-trunk - Build # 2838 - Failure
See https://builds.apache.org/job/ZooKeeper-trunk/2838/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 2703 lines...] init: [echo] recipes: queue [mkdir] Created dir: /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/recipes/queue [mkdir] Created dir: /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/recipes/queue/classes [mkdir] Created dir: /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/recipes/queue/test init-recipes: compile: [echo] contrib: queue [javac] /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/src/recipes/build-recipes.xml:103: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Compiling 1 source file to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/recipes/queue/classes jar: [echo] recipes: queue [jar] Building jar: /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/recipes/queue/zookeeper-3.6.0-SNAPSHOT-recipes-queue.jar zookeeperbuildrecipes.package: [echo] recipes: queue [mkdir] Created dir: /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/zookeeper-3.6.0-SNAPSHOT/recipes/queue [copy] Copying 1 file to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/zookeeper-3.6.0-SNAPSHOT/recipes/queue package: [copy] Copying 1 file to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/zookeeper-3.6.0-SNAPSHOT/recipes/queue [mkdir] Created dir: /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/zookeeper-3.6.0-SNAPSHOT/recipes/queue/test [copy] Copying 1 file to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/zookeeper-3.6.0-SNAPSHOT/recipes/queue/test [mkdir] Created dir: /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/zookeeper-3.6.0-SNAPSHOT/recipes/queue/src [copy] Copying 16 files to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/zookeeper-3.6.0-SNAPSHOT/recipes/queue/src [copy] Copying 1 file to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/zookeeper-3.6.0-SNAPSHOT [mkdir] Created dir: /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/zookeeper-3.6.0-SNAPSHOT/dist-maven [copy] Copying 1 file to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/zookeeper-3.6.0-SNAPSHOT/dist-maven [copy] Copying 2 files to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/zookeeper-3.6.0-SNAPSHOT/dist-maven BUILD FAILED /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build.xml:757: impossible convert given ivy file to pom file: java.io.FileNotFoundException: /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/src/pom.template (No such file or directory) from=/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/ivy.xml to=/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/zookeeper-3.6.0-SNAPSHOT/dist-maven/zookeeper-3.6.0-SNAPSHOT.pom Total time: 56 seconds mv: cannot stat 'build/*.tar.gz': No such file or directory mv: cannot stat 'build/test/findbugs': No such file or directory Build Failed Build step 'Execute shell' marked build as failure [FINDBUGS] Skipping publisher since build result is FAILURE [WARNINGS] Skipping publisher since build result is FAILURE Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording fingerprints Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Updating ZOOKEEPER-2378 Updating ZOOKEEPER-2294 Updating ZOOKEEPER-2373 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? Publishing Javadoc Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## No tests ran.
3.5.2-alpha Release Planning
This link shows issues currently fixed for 3.5.2: https://s.apache.org/n2C6 This link shows issues still open targeted to 3.5.2: https://s.apache.org/nORc I had been planning to kick off the release process for a 3.5.2-alpha candidate right around now, but after reviewing these lists, I'm inclined to defer it a few more weeks while we work down more blockers. What do others think? On a related note, thank you to Patrick for the recent JIRA clean-up. --Chris Nauroth
[jira] [Commented] (ZOOKEEPER-2379) recent commit broke findbugs qabot check
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178247#comment-15178247 ] Chris Nauroth commented on ZOOKEEPER-2379: -- Hi [~rakesh_r]. Thank you for the patch. +1 from me, but please also wait for feedback from [~rgs] before committing. > recent commit broke findbugs qabot check > > > Key: ZOOKEEPER-2379 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2379 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.4.9, 3.5.2, 3.6.0 >Reporter: Patrick Hunt >Assignee: Rakesh R >Priority: Blocker > Fix For: 3.4.9, 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-2379.patch > > > A recent commit seems to have broken findbugs, looks like it's in > ZooKeeperSaslClient > see: > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3075//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2373) Licenses section missing from pom file
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178233#comment-15178233
]
Chris Nauroth commented on ZOOKEEPER-2373:
--
I just saw Patrick already filed ZOOKEEPER-2379 for the Findbugs warning.
Thanks again.
> Licenses section missing from pom file
> --
>
> Key: ZOOKEEPER-2373
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2373
> Project: ZooKeeper
> Issue Type: Improvement
>Reporter: Flavio Junqueira
>Assignee: Patrick Hunt
>Priority: Blocker
> Fix For: 3.4.9, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2373.patch
>
>
> The pom file here:
> https://repo1.maven.org/maven2/org/apache/zookeeper/zookeeper/3.4.8/zookeeper-3.4.8.pom
> should have a section like this:
> {noformat}
>
>
> The Apache Software License, Version 2.0
> http://www.apache.org/licenses/LICENSE-2.0.txt
>
> repo
>
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2373) Licenses section missing from pom file
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178225#comment-15178225
]
Chris Nauroth commented on ZOOKEEPER-2373:
--
+1. Patrick, thank you for taking care of this.
> Licenses section missing from pom file
> --
>
> Key: ZOOKEEPER-2373
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2373
> Project: ZooKeeper
> Issue Type: Improvement
>Reporter: Flavio Junqueira
>Assignee: Patrick Hunt
>Priority: Blocker
> Fix For: 3.4.9, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2373.patch
>
>
> The pom file here:
> https://repo1.maven.org/maven2/org/apache/zookeeper/zookeeper/3.4.8/zookeeper-3.4.8.pom
> should have a section like this:
> {noformat}
>
>
> The Apache Software License, Version 2.0
> http://www.apache.org/licenses/LICENSE-2.0.txt
>
> repo
>
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2373) Licenses section missing from pom file
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178230#comment-15178230
]
Chris Nauroth commented on ZOOKEEPER-2373:
--
The Findbugs warning is unrelated to this patch, but worthy of follow-up. I'll
file a new JIRA if it's not already tracked.
> Licenses section missing from pom file
> --
>
> Key: ZOOKEEPER-2373
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2373
> Project: ZooKeeper
> Issue Type: Improvement
>Reporter: Flavio Junqueira
>Assignee: Patrick Hunt
>Priority: Blocker
> Fix For: 3.4.9, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2373.patch
>
>
> The pom file here:
> https://repo1.maven.org/maven2/org/apache/zookeeper/zookeeper/3.4.8/zookeeper-3.4.8.pom
> should have a section like this:
> {noformat}
>
>
> The Apache Software License, Version 2.0
> http://www.apache.org/licenses/LICENSE-2.0.txt
>
> repo
>
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2378) upgrade ivy to recent version
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178222#comment-15178222 ] Chris Nauroth commented on ZOOKEEPER-2378: -- +1. Thank you for the patch, Patrick. > upgrade ivy to recent version > - > > Key: ZOOKEEPER-2378 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2378 > Project: ZooKeeper > Issue Type: Improvement > Components: build >Affects Versions: 3.4.8, 3.5.1, 3.6.0 >Reporter: Patrick Hunt >Assignee: Patrick Hunt >Priority: Critical > Fix For: 3.4.9, 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-2378.patch > > > 2.4.0 is the current version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1604) remove rpm/deb/... packaging
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178220#comment-15178220 ] Chris Nauroth commented on ZOOKEEPER-1604: -- [~phunt], thank you for reviewing and committing. > remove rpm/deb/... packaging > > > Key: ZOOKEEPER-1604 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1604 > Project: ZooKeeper > Issue Type: Task > Components: build >Affects Versions: 3.3.0 >Reporter: Patrick Hunt >Assignee: Chris Nauroth > Fix For: 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-1604.001.patch, ZOOKEEPER-1604.patch > > > Remove rpm/deb/... packaging from our source repo. Now that BigTop is > available and fully supporting ZK it's no longer necessary for us to attempt > to include this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: ZOOKEEPER-2379 PreCommit Build #3080
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2379 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3080/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 382791 lines...] [exec] -1 tests included. The patch doesn't appear to include any new or modified tests. [exec] Please justify why no new tests are needed for this patch. [exec] Also please list what manual steps were performed to verify this patch. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] +1 findbugs. The patch does not introduce any new Findbugs (version 2.0.3) warnings. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. [exec] [exec] +1 core tests. The patch passed core unit tests. [exec] [exec] +1 contrib tests. The patch passed contrib unit tests. [exec] [exec] Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3080//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3080//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3080//console [exec] [exec] This message is automatically generated. [exec] [exec] [exec] == [exec] == [exec] Adding comment to Jira. [exec] == [exec] == [exec] [exec] [exec] Comment added. [exec] be3827f1225de257a0ac4dc68aea2017bdf064cf logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1642: exec returned: 1 Total time: 17 minutes 28 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-2379 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Commented] (ZOOKEEPER-2379) recent commit broke findbugs qabot check
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178177#comment-15178177 ] Hadoop QA commented on ZOOKEEPER-2379: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12791202/ZOOKEEPER-2379.patch against trunk revision 1733489. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 2.0.3) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3080//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3080//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3080//console This message is automatically generated. > recent commit broke findbugs qabot check > > > Key: ZOOKEEPER-2379 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2379 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.4.9, 3.5.2, 3.6.0 >Reporter: Patrick Hunt >Assignee: Rakesh R >Priority: Blocker > Fix For: 3.4.9, 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-2379.patch > > > A recent commit seems to have broken findbugs, looks like it's in > ZooKeeperSaslClient > see: > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3075//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2294) Ant target generate-clover-reports is broken
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2294: Fix Version/s: 3.6.0 3.5.2 3.4.9 > Ant target generate-clover-reports is broken > > > Key: ZOOKEEPER-2294 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2294 > Project: ZooKeeper > Issue Type: Bug > Components: build >Reporter: Charlie Helin >Assignee: Charlie Helin > Fix For: 3.4.9, 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-2294.001.patch > > > It appears that the current implementation of 'generate-clover-reports' is > broken. > # It doesn't define the clover-report task > # The clover-report element is missing the proper clover db reference -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2379) recent commit broke findbugs qabot check
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178144#comment-15178144 ] Patrick Hunt commented on ZOOKEEPER-2379: - No worries [~rakesh_r]. [~rgs] can you review this asap given you have context, having reviewed ZOOKEEPER-2375 > recent commit broke findbugs qabot check > > > Key: ZOOKEEPER-2379 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2379 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.4.9, 3.5.2, 3.6.0 >Reporter: Patrick Hunt >Assignee: Rakesh R >Priority: Blocker > Fix For: 3.4.9, 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-2379.patch > > > A recent commit seems to have broken findbugs, looks like it's in > ZooKeeperSaslClient > see: > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3075//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: qabot findbugs check failing
oops, this occurred due to recent checkins. Yes, I'm assigning and working to fix this. Regards, Rakesh On Thu, Mar 3, 2016 at 8:54 PM, Patrick Hunt wrote: > Can someone take a look at this asap? > https://issues.apache.org/jira/browse/ZOOKEEPER-2379 > > qabot is failing all the patches due to this. Looks like it slipped in > recently. > > Patrick >
[jira] [Commented] (ZOOKEEPER-2379) recent commit broke findbugs qabot check
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178125#comment-15178125 ] Rakesh R commented on ZOOKEEPER-2379: - oops, attached a patch to fix it. Thanks a lot [~phunt] for pointing out this. > recent commit broke findbugs qabot check > > > Key: ZOOKEEPER-2379 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2379 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.4.9, 3.5.2, 3.6.0 >Reporter: Patrick Hunt >Assignee: Rakesh R >Priority: Blocker > Fix For: 3.4.9, 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-2379.patch > > > A recent commit seems to have broken findbugs, looks like it's in > ZooKeeperSaslClient > see: > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3075//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2379) recent commit broke findbugs qabot check
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R updated ZOOKEEPER-2379: Attachment: ZOOKEEPER-2379.patch > recent commit broke findbugs qabot check > > > Key: ZOOKEEPER-2379 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2379 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.4.9, 3.5.2, 3.6.0 >Reporter: Patrick Hunt >Assignee: Rakesh R >Priority: Blocker > Fix For: 3.4.9, 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-2379.patch > > > A recent commit seems to have broken findbugs, looks like it's in > ZooKeeperSaslClient > see: > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3075//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1604) remove rpm/deb/... packaging
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178069#comment-15178069 ] Hudson commented on ZOOKEEPER-1604: --- FAILURE: Integrated in ZooKeeper-trunk #2836 (See [https://builds.apache.org/job/ZooKeeper-trunk/2836/]) ZOOKEEPER-1604 remove rpm/deb/... packaging (cnauroth via phunt) (phunt: [http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1733489]) * trunk/README_packaging.txt * trunk/build.xml * trunk/ivy.xml * trunk/src/contrib/build-contrib.xml * trunk/src/contrib/build.xml * trunk/src/contrib/zkpython/build.xml * trunk/src/contrib/zkpython/ivy.xml * trunk/src/contrib/zkpython/src/packages * trunk/src/packages * trunk/src/recipes/build-recipes.xml * trunk/src/recipes/build.xml > remove rpm/deb/... packaging > > > Key: ZOOKEEPER-1604 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1604 > Project: ZooKeeper > Issue Type: Task > Components: build >Affects Versions: 3.3.0 >Reporter: Patrick Hunt >Assignee: Chris Nauroth > Fix For: 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-1604.001.patch, ZOOKEEPER-1604.patch > > > Remove rpm/deb/... packaging from our source repo. Now that BigTop is > available and fully supporting ZK it's no longer necessary for us to attempt > to include this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
ZooKeeper-trunk - Build # 2836 - Failure
See https://builds.apache.org/job/ZooKeeper-trunk/2836/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 384332 lines...] [exec] Log Message Received: [2016-03-03 16:34:16,685:10180(0x2ae62767a540):ZOO_INFO@log_env@1040: Client environment:os.version=#63-Ubuntu SMP PREEMPT Wed Sep 3 21:56:12 UTC 2014] [exec] Log Message Received: [2016-03-03 16:34:16,685:10180(0x2ae62767a540):ZOO_INFO@log_env@1048: Client environment:user.name=jenkins] [exec] Log Message Received: [2016-03-03 16:34:16,685:10180(0x2ae62767a540):ZOO_INFO@log_env@1056: Client environment:user.home=/home/jenkins] [exec] Log Message Received: [2016-03-03 16:34:16,685:10180(0x2ae62767a540):ZOO_INFO@log_env@1068: Client environment:user.dir=/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/test/test-cppunit] [exec] Log Message Received: [2016-03-03 16:34:16,685:10180(0x2ae62767a540):ZOO_INFO@zookeeper_init_internal@: Initiating client connection, host=127.0.0.1:22181 sessionTimeout=1 watcher=0x45d2a0 sessionId=0 sessionPasswd= context=0x7fff685e9900 flags=0] [exec] Log Message Received: [2016-03-03 16:34:16,685:10180(0x2ae629d09700):ZOO_INFO@check_events@2357: initiated connection to server [127.0.0.1:22181]] [exec] Log Message Received: [2016-03-03 16:34:16,701:10180(0x2ae629d09700):ZOO_INFO@check_events@2409: session establishment complete on server [127.0.0.1:22181], sessionId=0x100232092a70010, negotiated timeout=1 ] [exec] : elapsed 1001 : OK [exec] Zookeeper_simpleSystem::testAsyncWatcherAutoReset ZooKeeper server started : elapsed 10043 : OK [exec] Zookeeper_simpleSystem::testDeserializeString : elapsed 0 : OK [exec] Zookeeper_simpleSystem::testFirstServerDown : elapsed 1001 : OK [exec] Zookeeper_simpleSystem::testNullData : elapsed 1049 : OK [exec] Zookeeper_simpleSystem::testIPV6 : elapsed 1012 : OK [exec] Zookeeper_simpleSystem::testCreate : elapsed 1016 : OK [exec] Zookeeper_simpleSystem::testPath : elapsed 1049 : OK [exec] Zookeeper_simpleSystem::testPathValidation : elapsed 1141 : OK [exec] Zookeeper_simpleSystem::testPing : elapsed 17585 : OK [exec] Zookeeper_simpleSystem::testAcl : elapsed 1023 : OK [exec] Zookeeper_simpleSystem::testChroot : elapsed 3083 : OK [exec] Zookeeper_simpleSystem::testAuth ZooKeeper server started ZooKeeper server started : elapsed 30187 : OK [exec] Zookeeper_simpleSystem::testHangingClient : elapsed 1043 : OK [exec] Zookeeper_simpleSystem::testWatcherAutoResetWithGlobal ZooKeeper server started ZooKeeper server started ZooKeeper server started : elapsed 14288 : OK [exec] Zookeeper_simpleSystem::testWatcherAutoResetWithLocal ZooKeeper server started ZooKeeper server started ZooKeeper server started : elapsed 14316 : OK [exec] Zookeeper_simpleSystem::testGetChildren2 : elapsed 1060 : OK [exec] Zookeeper_simpleSystem::testLastZxid : elapsed 4538 : OK [exec] Zookeeper_simpleSystem::testRemoveWatchers ZooKeeper server started : elapsed 4102 : OK [exec] Zookeeper_readOnly::testReadOnly : elapsed 4190 : OK [exec] OK (72) [exec] PASS: zktest-mt [exec] == [exec] 1 of 2 tests failed [exec] Please report to u...@zookeeper.apache.org [exec] == [exec] make[1]: Leaving directory `/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/test/test-cppunit' [exec] make[1]: *** [check-TESTS] Error 1 [exec] make: *** [check-am] Error 2 BUILD FAILED /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build.xml:1359: The following error occurred while executing this line: /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build.xml:1319: The following error occurred while executing this line: /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build.xml:1329: exec returned: 2 Total time: 14 minutes 26 seconds Build step 'Execute shell' marked build as failure [FINDBUGS] Skipping publisher since build result is FAILURE [WARNINGS] Skipping publisher since build result is FAILURE Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording fingerprints Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Updating ZOOKEEPER-1604 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Publishing Javadoc Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.mod
[jira] [Commented] (ZOOKEEPER-2319) UnresolvedAddressException cause the QuorumCnxManager.Listener exit
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178050#comment-15178050
]
Rakesh R commented on ZOOKEEPER-2319:
-
Presently Listener thread will log WARNING message and exit on
{{ava.nio.channels.UnresolvedAddressException}}, which is not a subclass of
IOException. I also feel we could improve by catching this exception and
continue listening.
> UnresolvedAddressException cause the QuorumCnxManager.Listener exit
> ---
>
> Key: ZOOKEEPER-2319
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2319
> Project: ZooKeeper
> Issue Type: Bug
>Affects Versions: 3.4.6
>Reporter: Zhaohui Yu
>Priority: Critical
> Fix For: 3.4.9, 3.5.2, 3.6.0
>
>
> Given three nodes, the leader on 2, but some issue with this machine, so I
> shutdown this machine, and change the host name to another machine.
> Then I start the node in the new machine, but the new node can not join.
> I found the the 1 and 3's Listener thread exit.
> With the code of Listener's run method:
> I think we should catch UnresolvedAddressException to avoid the Listener exit.
> {noformat}
> @Override
> public void run() {
>
> while((!shutdown) && (numRetries < 3)){
> try {
>// bind and accept
> receiveConnection(client);
>
> } catch (IOException e) {
>
> }
> }
> //
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (ZOOKEEPER-2061) Zookeeper needs an official RPM package. I am happy to build and submit one.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt resolved ZOOKEEPER-2061. - Resolution: Won't Fix Given the packaging has been removed as of ZOOKEEPER-1604 I'm closing this. Please use Bigtop for ZK packaging. > Zookeeper needs an official RPM package. I am happy to build and submit one. > > > Key: ZOOKEEPER-2061 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2061 > Project: ZooKeeper > Issue Type: Wish > Components: build >Reporter: Brian Weber > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1604) remove rpm/deb/... packaging
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178045#comment-15178045 ] Hadoop QA commented on ZOOKEEPER-1604: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12791195/ZOOKEEPER-1604.patch against trunk revision 1733348. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 1 new Findbugs (version 2.0.3) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3079//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3079//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3079//console This message is automatically generated. > remove rpm/deb/... packaging > > > Key: ZOOKEEPER-1604 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1604 > Project: ZooKeeper > Issue Type: Task > Components: build >Affects Versions: 3.3.0 >Reporter: Patrick Hunt >Assignee: Chris Nauroth > Fix For: 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-1604.001.patch, ZOOKEEPER-1604.patch > > > Remove rpm/deb/... packaging from our source repo. Now that BigTop is > available and fully supporting ZK it's no longer necessary for us to attempt > to include this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: ZOOKEEPER-1604 PreCommit Build #3079
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1604 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3079/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 377586 lines...] [exec] -1 tests included. The patch doesn't appear to include any new or modified tests. [exec] Please justify why no new tests are needed for this patch. [exec] Also please list what manual steps were performed to verify this patch. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] -1 findbugs. The patch appears to introduce 1 new Findbugs (version 2.0.3) warnings. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. [exec] [exec] +1 core tests. The patch passed core unit tests. [exec] [exec] +1 contrib tests. The patch passed contrib unit tests. [exec] [exec] Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3079//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3079//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3079//console [exec] [exec] This message is automatically generated. [exec] [exec] [exec] == [exec] == [exec] Adding comment to Jira. [exec] == [exec] == [exec] [exec] [exec] Comment added. [exec] 18178a8528d900af0dfb2c871a83f2567f439a3a logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1816: exec returned: 2 Total time: 14 minutes 34 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-1604 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Resolved] (ZOOKEEPER-1649) Build RPM Package Error on CentOS 5
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt resolved ZOOKEEPER-1649. - Resolution: Won't Fix Given the packaging has been removed as of ZOOKEEPER-1604 I'm closing this. Please use Bigtop for ZK packaging. > Build RPM Package Error on CentOS 5 > --- > > Key: ZOOKEEPER-1649 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1649 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.4.5 > Environment: CentOS 5.8 x86_64 > JDK 1.6.0_21-b06 >Reporter: Shining > > ant rpm > > rpm: > [copy] Copying 1 file to /tmp/zkpython_build_nshi/SOURCES > [rpm] Building the RPM based on the zkpython.spec file > [rpm] Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.62078 > [rpm] Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.62078 > [rpm] Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.62078 > [rpm] > [rpm] > [rpm] RPM build errors: > [rpm] + umask 022 > [rpm] + cd /tmp/zkpython_build_nshi/BUILD > [rpm] + LANG=C > [rpm] + export LANG > [rpm] + unset DISPLAY > [rpm] + tar fxz > /tmp/zkpython_build_nshi/SOURCES/ZooKeeper-0.4.linux-x86_64.tar.gz -C > /tmp/zkpython_build_nshi/BUILD > [rpm] + exit 0 > [rpm] + umask 022 > [rpm] + cd /tmp/zkpython_build_nshi/BUILD > [rpm] + LANG=C > [rpm] + export LANG > [rpm] + unset DISPLAY > [rpm] + exit 0 > [rpm] + umask 022 > [rpm] + cd /tmp/zkpython_build_nshi/BUILD > [rpm] + LANG=C > [rpm] + export LANG > [rpm] + unset DISPLAY > [rpm] + /bin/mv /tmp/zkpython_build_nshi/BUILD/usr > /tmp/zkpython_build_nshi/BUILD > [rpm] /bin/mv: `/tmp/zkpython_build_nshi/BUILD/usr' and > `/tmp/zkpython_build_nshi/BUILD/usr' are the same file > [rpm] error: Bad exit status from /var/tmp/rpm-tmp.62078 (%install) > [rpm] Bad exit status from /var/tmp/rpm-tmp.62078 (%install) > BUILD FAILED > /home/nshi/workspace/zookeeper-3.4.5/build.xml:955: The following error > occurred while executing this line: > /home/nshi/workspace/zookeeper-3.4.5/src/contrib/build.xml:75: The following > error occurred while executing this line: > /home/nshi/workspace/zookeeper-3.4.5/src/contrib/zkpython/build.xml:144: > '/usr/bin/rpmbuild' failed with exit code 1 > - -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ZOOKEEPER-1187) remove jdk dependency from the rpm spec
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt resolved ZOOKEEPER-1187. - Resolution: Won't Fix Given the packaging has been removed as of ZOOKEEPER-1604 I'm closing this. Please use Bigtop for ZK packaging. > remove jdk dependency from the rpm spec > --- > > Key: ZOOKEEPER-1187 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1187 > Project: ZooKeeper > Issue Type: Improvement >Reporter: Giridharan Kesavan >Assignee: Giridharan Kesavan > Attachments: zk-1187.patch > > > remove jdk dependency from the rpm spec -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ZOOKEEPER-2352) rpm build broke
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt resolved ZOOKEEPER-2352. - Resolution: Won't Fix Fix Version/s: (was: 3.5.1) Given the packaging has been removed as of ZOOKEEPER-1604 I'm closing this. Please use Bigtop for ZK packaging. > rpm build broke > --- > > Key: ZOOKEEPER-2352 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2352 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.5.1 > Environment: ubuntu 15.10 >Reporter: Wenjie Ding > Attachments: rpm-tmp.G8hNUf > > Original Estimate: 10h > Remaining Estimate: 10h > > rpm ‘cd’ to the BUILD directory, delete the directory it just ‘cd’ to. What > was going on from that point was that it called some script which was loading > /bin/bash and crashed since ‘getcwd’ cannot access the parent directory which > had been deleted. > build output messages; > ... > [rpm] + cd /tmp/zkpython_build_root/BUILD > [rpm] + '[' /tmp/zkpython_build_root/BUILD '!=' / ']' > [rpm] + rm -rf /tmp/zkpython_build_root/BUILD > [rpm] ++ dirname /tmp/zkpython_build_root/BUILD > [rpm] + mkdir -p /tmp/zkpython_build_root > [rpm] + mkdir /tmp/zkpython_build_root/BUILD > [rpm] + /usr/lib/rpm/check-buildroot > [rpm] shell-init: error retrieving current directory: getcwd: cannot > access parent directories: No such file or directory > [rpm] + /usr/lib/rpm/redhat/brp-compress > [rpm] shell-init: error retrieving current directory: getcwd: cannot > access parent directories: No such file or directory > [rpm] chdir: error retrieving current directory: getcwd: cannot access > parent directories: No such file or directory > [rpm] + /usr/lib/rpm/redhat/brp-strip /usr/bin/strip > [rpm] shell-init: error retrieving current directory: getcwd: cannot > access parent directories: No such file or directory > [rpm] + /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip > [rpm] shell-init: error retrieving current directory: getcwd: cannot > access parent directories: No such file or directory > [rpm] + /usr/lib/rpm/redhat/brp-strip-comment-note /usr/bin/strip > /usr/bin/objdump > [rpm] shell-init: error retrieving current directory: getcwd: cannot > access parent directories: No such file or directory > [rpm] + /usr/lib/rpm/brp-python-bytecompile > [rpm] shell-init: error retrieving current directory: getcwd: cannot > access parent directories: No such file or directory -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ZOOKEEPER-1129) Add RPM/Debian packages to Jenkins
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt resolved ZOOKEEPER-1129. - Resolution: Won't Fix Given the packaging has been removed as of ZOOKEEPER-1604 I'm closing this. Please use Bigtop for ZK packaging. > Add RPM/Debian packages to Jenkins > -- > > Key: ZOOKEEPER-1129 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1129 > Project: ZooKeeper > Issue Type: Task >Reporter: Eric Yang > > For taking advantage of packages generated by ZOOKEEPER-999. It would be > nice to setup rpm/debian package build on Jenkins. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1604) remove rpm/deb/... packaging
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178018#comment-15178018 ] Hadoop QA commented on ZOOKEEPER-1604: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12791195/ZOOKEEPER-1604.patch against trunk revision 1733348. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 1 new Findbugs (version 2.0.3) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3078//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3078//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3078//console This message is automatically generated. > remove rpm/deb/... packaging > > > Key: ZOOKEEPER-1604 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1604 > Project: ZooKeeper > Issue Type: Task > Components: build >Affects Versions: 3.3.0 >Reporter: Patrick Hunt >Assignee: Chris Nauroth > Fix For: 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-1604.001.patch, ZOOKEEPER-1604.patch > > > Remove rpm/deb/... packaging from our source repo. Now that BigTop is > available and fully supporting ZK it's no longer necessary for us to attempt > to include this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: ZOOKEEPER-1604 PreCommit Build #3078
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1604 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3078/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 380526 lines...] [exec] -1 tests included. The patch doesn't appear to include any new or modified tests. [exec] Please justify why no new tests are needed for this patch. [exec] Also please list what manual steps were performed to verify this patch. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] -1 findbugs. The patch appears to introduce 1 new Findbugs (version 2.0.3) warnings. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. [exec] [exec] +1 core tests. The patch passed core unit tests. [exec] [exec] +1 contrib tests. The patch passed contrib unit tests. [exec] [exec] Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3078//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3078//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3078//console [exec] [exec] This message is automatically generated. [exec] [exec] [exec] == [exec] == [exec] Adding comment to Jira. [exec] == [exec] == [exec] [exec] [exec] Comment added. [exec] 4cfcb0b2fa55b61879ffb51664ba683b9e8e8f0c logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1816: exec returned: 2 Total time: 14 minutes 25 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-1604 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Updated] (ZOOKEEPER-1604) remove rpm/deb/... packaging
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-1604: Attachment: ZOOKEEPER-1604.patch Updated the original patch to apply cleanly. Removed debian target as well. > remove rpm/deb/... packaging > > > Key: ZOOKEEPER-1604 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1604 > Project: ZooKeeper > Issue Type: Task > Components: build >Affects Versions: 3.3.0 >Reporter: Patrick Hunt >Assignee: Chris Nauroth > Fix For: 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-1604.001.patch, ZOOKEEPER-1604.patch > > > Remove rpm/deb/... packaging from our source repo. Now that BigTop is > available and fully supporting ZK it's no longer necessary for us to attempt > to include this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
qabot findbugs check failing
Can someone take a look at this asap? https://issues.apache.org/jira/browse/ZOOKEEPER-2379 qabot is failing all the patches due to this. Looks like it slipped in recently. Patrick
[jira] [Assigned] (ZOOKEEPER-2379) recent commit broke findbugs qabot check
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt reassigned ZOOKEEPER-2379: --- Assignee: Rakesh R [~rakesh_r] can you take a look at this? > recent commit broke findbugs qabot check > > > Key: ZOOKEEPER-2379 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2379 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.4.9, 3.5.2, 3.6.0 >Reporter: Patrick Hunt >Assignee: Rakesh R >Priority: Blocker > Fix For: 3.4.9, 3.5.2, 3.6.0 > > > A recent commit seems to have broken findbugs, looks like it's in > ZooKeeperSaslClient > see: > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3075//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2379) recent commit broke findbugs qabot check
Patrick Hunt created ZOOKEEPER-2379: --- Summary: recent commit broke findbugs qabot check Key: ZOOKEEPER-2379 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2379 Project: ZooKeeper Issue Type: Bug Components: build Affects Versions: 3.4.9, 3.5.2, 3.6.0 Reporter: Patrick Hunt Priority: Blocker Fix For: 3.4.9, 3.5.2, 3.6.0 A recent commit seems to have broken findbugs, looks like it's in ZooKeeperSaslClient see: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3075//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1604) remove rpm/deb/... packaging
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177450#comment-15177450 ] Hadoop QA commented on ZOOKEEPER-1604: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12726926/ZOOKEEPER-1604.001.patch against trunk revision 1733348. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. -1 patch. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3077//console This message is automatically generated. > remove rpm/deb/... packaging > > > Key: ZOOKEEPER-1604 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1604 > Project: ZooKeeper > Issue Type: Task > Components: build >Affects Versions: 3.3.0 >Reporter: Patrick Hunt >Assignee: Chris Nauroth > Fix For: 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-1604.001.patch > > > Remove rpm/deb/... packaging from our source repo. Now that BigTop is > available and fully supporting ZK it's no longer necessary for us to attempt > to include this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
