date:20170928

ZooKeeper-trunk-openjdk7 - Build # 1639 - Still Failing

2017-09-28 Thread Apache Jenkins Server

See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1639/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 65.52 MB...]
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)
[junit] at 
org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
[junit] at 
org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
[junit] at 
org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
[junit] at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
[junit] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
[junit] at java.lang.Thread.run(Thread.java:748)
[junit] 2017-09-29 04:28:53,874 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 155515
[junit] 2017-09-29 04:28:53,874 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 1648
[junit] 2017-09-29 04:28:53,874 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2017-09-29 04:28:53,875 [myid:] - INFO  [main:ClientBase@601] - 
tearDown starting
[junit] 2017-09-29 04:28:53,875 [myid:] - INFO  [main:ClientBase@571] - 
STOPPING server
[junit] 2017-09-29 04:28:53,875 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:19547
[junit] 2017-09-29 04:28:53,881 [myid:] - INFO  [main:ZooKeeperServer@545] 
- shutting down
[junit] 2017-09-29 04:28:53,881 [myid:] - ERROR [main:ZooKeeperServer@509] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-09-29 04:28:53,881 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2017-09-29 04:28:53,881 [myid:] - INFO  
[main:PrepRequestProcessor@1010] - Shutting down
[junit] 2017-09-29 04:28:53,882 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2017-09-29 04:28:53,882 [myid:] - INFO  [ProcessThread(sid:0 
cport:19547)::PrepRequestProcessor@155] - PrepRequestProcessor exited loop!
[junit] 2017-09-29 04:28:53,882 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited!
[junit] 2017-09-29 04:28:53,882 [myid:] - INFO  
[main:FinalRequestProcessor@481] - shutdown of request processor complete
[junit] 2017-09-29 04:28:53,882 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port19547,name1=InMemoryDataTree]
[junit] 2017-09-29 04:28:53,882 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port19547]
[junit] 2017-09-29 04:28:53,882 [myid:] - INFO  
[main:FourLetterWordMain@87] - connecting to 127.0.0.1 19547
[junit] 2017-09-29 04:28:53,883 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2017-09-29 04:28:53,888 [myid:] - INFO  [main:ClientBase@626] - 
fdcount after test is: 4850 at start it was 4850
[junit] 2017-09-29 04:28:53,889 [myid:] - INFO  [main:ZKTestCase$1@68] - 
SUCCEEDED testWatcherAutoResetWithLocal
[junit] 2017-09-29 04:28:53,906 [myid:] - INFO  [main:ZKTestCase$1@63] - 
FINISHED testWatcherAutoResetWithLocal
[junit] Tests run: 105, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
403.922 sec, Thread: 4, Class: org.apache.zookeeper.test.NioNettySuiteTest
[junit] 2017-09-29 04:28:54,080 [myid:127.0.0.1:19350] - INFO  
[main-SendThread(127.0.0.1:19350):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:19350. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-09-29 04:28:54,081 [myid:127.0.0.1:19350] - WARN  
[main-SendThread(127.0.0.1:19350):ClientCnxn$SendThread@1235] - Session 
0x101b1ef2a3d0001 for server 127.0.0.1/127.0.0.1:19350, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-09-29 04:28:54,156 [myid:] - INFO  
[SessionTracker:SessionTrackerImpl@158] - SessionTrackerImpl exited loop!
[junit] 2

ZooKeeper-trunk-openjdk7 - Build # 1638 - Still Failing

2017-09-28 Thread Apache Jenkins Server

See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1638/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 2.95 KB...]
MAIL=/var/mail/jenkins
PATH=/usr/lib/jvm/java-7-openjdk-amd64//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/home/jenkins/.rvm/bin
RUN_DISPLAY_URL=https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1638/display/redirect
_=/usr/bin/env
BUILD_CAUSE_MANUALTRIGGER=true
GIT_COMMITTER_EMAIL=bui...@apache.org
PWD=/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7
JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64/
HUDSON_URL=https://builds.apache.org/
LANG=en_US
JOB_NAME=ZooKeeper-trunk-openjdk7
XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt
BUILD_DISPLAY_NAME=#1638
BUILD_CAUSE=MANUALTRIGGER
BUILD_ID=1638
JENKINS_URL=https://builds.apache.org/
JOB_BASE_NAME=ZooKeeper-trunk-openjdk7
GIT_PREVIOUS_SUCCESSFUL_COMMIT=f33a75db1cc18124b6d0a4ee15967901fa6ec493
HOME=/home/jenkins
SHLVL=2
GIT_BRANCH=origin/master
EXECUTOR_NUMBER=1
JENKINS_SERVER_COOKIE=f4ebd1e6b0d976e8
GIT_URL=git://git.apache.org/zookeeper.git
NODE_LABELS=trusty ubuntu ubuntu-1
LOGNAME=jenkins
SSH_CONNECTION=62.210.60.235 45864 67.195.81.190 22
HUDSON_HOME=/x1/jenkins/jenkins-home
NODE_NAME=ubuntu-1
BUILD_NUMBER=1638
JOB_DISPLAY_URL=https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/display/redirect
XDG_RUNTIME_DIR=/run/user/2395
ROOT_BUILD_CAUSE_MANUALTRIGGER=true
HUDSON_COOKIE=ec789cff-bc4f-4968-8374-dce9a5627cb5
GIT_AUTHOR_EMAIL=bui...@apache.org
+ java -version
java version "1.7.0_151"
OpenJDK Runtime Environment (IcedTea 2.6.11) (7u151-2.6.11-0ubuntu1.14.04.1)
OpenJDK 64-Bit Server VM (build 24.151-b01, mixed mode)
[ZooKeeper-trunk-openjdk7] $ /home/jenkins/tools/ant/latest/bin/ant 
-Dtest.output=yes -Dtest.junit.threads=8 -Dtest.junit.output.format=xml 
-Djavac.target=1.7 clean test-core-java
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:803)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:442)
at java.net.URLClassLoader.access$100(URLClassLoader.java:64)
at java.net.URLClassLoader$1.run(URLClassLoader.java:354)
at java.net.URLClassLoader$1.run(URLClassLoader.java:348)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:347)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:312)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
Build step 'Invoke Ant' marked build as failure
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
No tests ran.

ZooKeeper-trunk-openjdk7 - Build # 1637 - Still Failing

2017-09-28 Thread Apache Jenkins Server

See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1637/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 995 B...]
 > git clean -fdx # timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
 > git --version # timeout=10
 > git fetch --tags --progress git://git.apache.org/zookeeper.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 086359a6945df3ea5548c7a65730294cf612ce66 
(refs/remotes/origin/master)
Commit message: "ZOOKEEPER-2887: define dependency versions in build.xml to be 
easily overridden in build.properties"
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 086359a6945df3ea5548c7a65730294cf612ce66
 > git rev-list 086359a6945df3ea5548c7a65730294cf612ce66 # timeout=10
No emails were triggered.
FATAL: Unable to produce a script file
java.io.IOException: No space left on device
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:326)
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
at sun.nio.cs.StreamEncoder.implClose(StreamEncoder.java:316)
at sun.nio.cs.StreamEncoder.close(StreamEncoder.java:149)
at java.io.OutputStreamWriter.close(OutputStreamWriter.java:233)
at hudson.FilePath$17.invoke(FilePath.java:1380)
at hudson.FilePath$17.invoke(FilePath.java:1363)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2739)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:336)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
at ..remote call to qnode3(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1545)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel.call(Channel.java:830)
at hudson.FilePath.act(FilePath.java:986)
Caused: java.io.IOException: remote file operation failed: 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7 at 
hudson.remoting.Channel@247bd887:qnode3
at hudson.FilePath.act(FilePath.java:993)
at hudson.FilePath.act(FilePath.java:975)
at hudson.FilePath.createTextTempFile(FilePath.java:1363)
Caused: java.io.IOException: Failed to create a temp file on 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7
at hudson.FilePath.createTextTempFile(FilePath.java:1386)
at 
hudson.tasks.CommandInterpreter.createScriptFile(CommandInterpreter.java:162)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:94)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:735)
at hudson.model.Build$BuildExecution.build(Build.java:206)
at hudson.model.Build$BuildExecution.doRun(Build.java:163)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:490)
at hudson.model.Run.execute(Run.java:1735)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:405)
Build step 'Execute shell' marked build as failure
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files 
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
No tests ran.

ZooKeeper-trunk-openjdk7 - Build # 1636 - Still Failing

2017-09-28 Thread Apache Jenkins Server

See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1636/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 995 B...]
 > git clean -fdx # timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
 > git --version # timeout=10
 > git fetch --tags --progress git://git.apache.org/zookeeper.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 086359a6945df3ea5548c7a65730294cf612ce66 
(refs/remotes/origin/master)
Commit message: "ZOOKEEPER-2887: define dependency versions in build.xml to be 
easily overridden in build.properties"
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 086359a6945df3ea5548c7a65730294cf612ce66
 > git rev-list 086359a6945df3ea5548c7a65730294cf612ce66 # timeout=10
No emails were triggered.
FATAL: Unable to produce a script file
java.io.IOException: No space left on device
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:326)
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
at sun.nio.cs.StreamEncoder.implClose(StreamEncoder.java:316)
at sun.nio.cs.StreamEncoder.close(StreamEncoder.java:149)
at java.io.OutputStreamWriter.close(OutputStreamWriter.java:233)
at hudson.FilePath$17.invoke(FilePath.java:1380)
at hudson.FilePath$17.invoke(FilePath.java:1363)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2739)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:336)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
at ..remote call to qnode3(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1545)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel.call(Channel.java:830)
at hudson.FilePath.act(FilePath.java:986)
Caused: java.io.IOException: remote file operation failed: 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7 at 
hudson.remoting.Channel@247bd887:qnode3
at hudson.FilePath.act(FilePath.java:993)
at hudson.FilePath.act(FilePath.java:975)
at hudson.FilePath.createTextTempFile(FilePath.java:1363)
Caused: java.io.IOException: Failed to create a temp file on 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7
at hudson.FilePath.createTextTempFile(FilePath.java:1386)
at 
hudson.tasks.CommandInterpreter.createScriptFile(CommandInterpreter.java:162)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:94)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:735)
at hudson.model.Build$BuildExecution.build(Build.java:206)
at hudson.model.Build$BuildExecution.doRun(Build.java:163)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:490)
at hudson.model.Run.execute(Run.java:1735)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:405)
Build step 'Execute shell' marked build as failure
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files 
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
No tests ran.

ZooKeeper-trunk-openjdk7 - Build # 1635 - Still Failing

2017-09-28 Thread Apache Jenkins Server

See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1635/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1.84 KB...]
No valid HEAD. Skipping the resetting
 > git clean -fdx # timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
 > git fetch --tags --progress git://git.apache.org/zookeeper.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 086359a6945df3ea5548c7a65730294cf612ce66 
(refs/remotes/origin/master)
Commit message: "ZOOKEEPER-2887: define dependency versions in build.xml to be 
easily overridden in build.properties"
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 086359a6945df3ea5548c7a65730294cf612ce66
 > git rev-list f33a75db1cc18124b6d0a4ee15967901fa6ec493 # timeout=10
No emails were triggered.
FATAL: Unable to produce a script file
java.io.IOException: No space left on device
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:326)
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
at sun.nio.cs.StreamEncoder.implClose(StreamEncoder.java:316)
at sun.nio.cs.StreamEncoder.close(StreamEncoder.java:149)
at java.io.OutputStreamWriter.close(OutputStreamWriter.java:233)
at hudson.FilePath$17.invoke(FilePath.java:1380)
at hudson.FilePath$17.invoke(FilePath.java:1363)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2739)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:336)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
at ..remote call to qnode3(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1545)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel.call(Channel.java:830)
at hudson.FilePath.act(FilePath.java:986)
Caused: java.io.IOException: remote file operation failed: 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7 at 
hudson.remoting.Channel@247bd887:qnode3
at hudson.FilePath.act(FilePath.java:993)
at hudson.FilePath.act(FilePath.java:975)
at hudson.FilePath.createTextTempFile(FilePath.java:1363)
Caused: java.io.IOException: Failed to create a temp file on 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7
at hudson.FilePath.createTextTempFile(FilePath.java:1386)
at 
hudson.tasks.CommandInterpreter.createScriptFile(CommandInterpreter.java:162)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:94)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:735)
at hudson.model.Build$BuildExecution.build(Build.java:206)
at hudson.model.Build$BuildExecution.doRun(Build.java:163)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:490)
at hudson.model.Run.execute(Run.java:1735)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:405)
Build step 'Execute shell' marked build as failure
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files 
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
No tests ran.

ZooKeeper_branch34_jdk7 - Build # 1669 - Failure

2017-09-28 Thread Apache Jenkins Server

See https://builds.apache.org/job/ZooKeeper_branch34_jdk7/1669/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 27.57 MB...]
[junit] 2017-09-29 02:56:31,259 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2017-09-29 02:56:31,262 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@144] - PrepRequestProcessor exited loop!
[junit] 2017-09-29 02:56:31,274 [myid:] - INFO  
[SessionTracker:SessionTrackerImpl@163] - SessionTrackerImpl exited loop!
[junit] 2017-09-29 02:56:31,274 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2017-09-29 02:56:31,278 [myid:] - INFO  
[main:FinalRequestProcessor@403] - shutdown of request processor complete
[junit] 2017-09-29 02:56:31,279 [myid:] - INFO  
[main:FourLetterWordMain@65] - connecting to 127.0.0.1 11221
[junit] 2017-09-29 02:56:31,279 [myid:] - INFO  [main:JMXEnv@147] - 
ensureOnly:[]
[junit] 2017-09-29 02:56:31,281 [myid:] - INFO  [main:ClientBase@489] - 
STARTING server
[junit] 2017-09-29 02:56:31,281 [myid:] - INFO  [main:ClientBase@410] - 
CREATING server instance 127.0.0.1:11221
[junit] 2017-09-29 02:56:31,281 [myid:] - INFO  
[main:ServerCnxnFactory@116] - Using 
org.apache.zookeeper.server.NIOServerCnxnFactory as server connection factory
[junit] 2017-09-29 02:56:31,281 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2017-09-29 02:56:31,282 [myid:] - INFO  [main:ClientBase@385] - 
STARTING server instance 127.0.0.1:11221
[junit] 2017-09-29 02:56:31,282 [myid:] - INFO  [main:ZooKeeperServer@173] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/build/test/tmp/test2196498954352487544.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/build/test/tmp/test2196498954352487544.junit.dir/version-2
[junit] 2017-09-29 02:56:31,294 [myid:] - ERROR [main:ZooKeeperServer@468] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-09-29 02:56:31,295 [myid:] - INFO  
[main:FourLetterWordMain@65] - connecting to 127.0.0.1 11221
[junit] 2017-09-29 02:56:31,298 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@215] - 
Accepted socket connection from /127.0.0.1:60983
[junit] 2017-09-29 02:56:31,298 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@892] - Processing 
stat command from /127.0.0.1:60983
[junit] 2017-09-29 02:56:31,302 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@683] - Stat command output
[junit] 2017-09-29 02:56:31,302 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1040] - Closed socket connection for client 
/127.0.0.1:60983 (no session established for client)
[junit] 2017-09-29 02:56:31,303 [myid:] - INFO  [main:JMXEnv@230] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2017-09-29 02:56:31,305 [myid:] - INFO  [main:JMXEnv@247] - 
expect:InMemoryDataTree
[junit] 2017-09-29 02:56:31,305 [myid:] - INFO  [main:JMXEnv@251] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2017-09-29 02:56:31,305 [myid:] - INFO  [main:JMXEnv@247] - 
expect:StandaloneServer_port
[junit] 2017-09-29 02:56:31,305 [myid:] - INFO  [main:JMXEnv@251] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2017-09-29 02:56:31,306 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 37012
[junit] 2017-09-29 02:56:31,306 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 19
[junit] 2017-09-29 02:56:31,306 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2017-09-29 02:56:31,307 [myid:] - INFO  [main:ClientBase@566] - 
tearDown starting
[junit] 2017-09-29 02:56:31,483 [myid:] - INFO  [main:ZooKeeper@687] - 
Session: 0x1006904418c closed
[junit] 2017-09-29 02:56:31,483 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@520] - EventThread shut down for 
session: 0x1006904418c
[junit] 2017-09-29 02:56:31,483 [myid:] - INFO  [main:ClientBase@536] - 
STOPPING server
[junit] 2017-09-29 02:56:31,484 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@242] - 
NIOServerCnxn factory exited run method
[junit] 2017-09-29 02:56:31,484 [myid:] - INFO  [main:ZooKeeperServer@501] 
- shutting down
[junit] 2017-09-29 02:56:31,484 [myid:] - ERROR [main:ZooKeeperServer@468] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't ta

Failed: ZOOKEEPER-1816 PreCommit Build #3648

2017-09-28 Thread Apache Jenkins Server

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1816
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3648/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 889 B...]
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 086359a6945df3ea5548c7a65730294cf612ce66 
(refs/remotes/origin/master)
Commit message: "ZOOKEEPER-2887: define dependency versions in build.xml to be 
easily overridden in build.properties"
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 086359a6945df3ea5548c7a65730294cf612ce66
 > git rev-list f33a75db1cc18124b6d0a4ee15967901fa6ec493 # timeout=10
No emails were triggered.
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[PreCommit-ZOOKEEPER-Build] $ /bin/bash /tmp/jenkins5260845521828070384.sh
/home/jenkins/tools/java/latest1.7/bin/java
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 386172
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 6
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 10240
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2887
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Assigned] (ZOOKEEPER-1816) ClientCnxn.close() should block until threads have died

2017-09-28 Thread wu wen (JIRA)


 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

wu wen reassigned ZOOKEEPER-1816:
-

Assignee: wu wen

> ClientCnxn.close() should block until threads have died
> ---
>
> Key: ZOOKEEPER-1816
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1816
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.3.6, 3.4.5
>Reporter: Jared Winick
>Assignee: wu wen
>Priority: Minor
> Fix For: 3.4.11
>
> Attachments: ZOOKEEPER-1816.patch
>
>
> In the testing of ACCUMULO-1379 and ACCUMULO-1858 it was seen that the 
> non-blocking behavior of ClientCnxn.close(), and therefore ZooKeeper.close(), 
> can cause a race condition when undeploying an application running in a Java 
> container such as JBoss or Tomcat. As the close() method returns without 
> joining on the sendThread and eventThread, those threads continue to 
> execute/cleanup while the container is cleaning up the application's 
> resources. If the container has unloaded classes by the time this code runs
> {code}
> ZooTrace.logTraceMessage(LOG, ZooTrace.getTextTraceLevel(), "SendThread 
> exitedloop.");
> {code}
> A "java.lang.NoClassDefFoundError: org/apache/zookeeper/server/ZooTrace" can 
> be seen. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Success: ZOOKEEPER- PreCommit Build #1072

2017-09-28 Thread Apache Jenkins Server

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1072/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 69.64 MB...]
 [exec]   
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] +0 tests included.  The patch appears to be a documentation 
patch that doesn't require 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 does not introduce any new Findbugs 
(version 3.0.1) 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-github-pr-build/1072//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1072//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1072//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Error: No value specified for option "issue"
 [exec] 284842df01c826102332560826737ee78fa09f33 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD SUCCESSFUL
Total time: 20 minutes 56 seconds
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2806
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Success
Sending email for trigger: Success
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

ZooKeeper_branch34 - Build # 2096 - Still Failing

2017-09-28 Thread Apache Jenkins Server

See https://builds.apache.org/job/ZooKeeper_branch34/2096/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 31.36 MB...]
[junit] 2017-09-29 00:20:21,573 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2017-09-29 00:20:21,573 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@144] - PrepRequestProcessor exited loop!
[junit] 2017-09-29 00:20:21,573 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2017-09-29 00:20:21,573 [myid:] - INFO  
[main:FinalRequestProcessor@403] - shutdown of request processor complete
[junit] 2017-09-29 00:20:21,574 [myid:] - INFO  
[main:FourLetterWordMain@65] - connecting to 127.0.0.1 11221
[junit] 2017-09-29 00:20:21,575 [myid:] - INFO  [main:JMXEnv@147] - 
ensureOnly:[]
[junit] 2017-09-29 00:20:21,576 [myid:] - INFO  [main:ClientBase@489] - 
STARTING server
[junit] 2017-09-29 00:20:21,576 [myid:] - INFO  [main:ClientBase@410] - 
CREATING server instance 127.0.0.1:11221
[junit] 2017-09-29 00:20:21,577 [myid:] - INFO  
[main:ServerCnxnFactory@116] - Using 
org.apache.zookeeper.server.NIOServerCnxnFactory as server connection factory
[junit] 2017-09-29 00:20:21,577 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2017-09-29 00:20:21,577 [myid:] - INFO  [main:ClientBase@385] - 
STARTING server instance 127.0.0.1:11221
[junit] 2017-09-29 00:20:21,578 [myid:] - INFO  [main:ZooKeeperServer@173] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build/test/tmp/test551611786687512.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build/test/tmp/test551611786687512.junit.dir/version-2
[junit] 2017-09-29 00:20:21,582 [myid:] - ERROR [main:ZooKeeperServer@468] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-09-29 00:20:21,582 [myid:] - INFO  
[main:FourLetterWordMain@65] - connecting to 127.0.0.1 11221
[junit] 2017-09-29 00:20:21,583 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@215] - 
Accepted socket connection from /127.0.0.1:53430
[junit] 2017-09-29 00:20:21,583 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@892] - Processing 
stat command from /127.0.0.1:53430
[junit] 2017-09-29 00:20:21,584 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@683] - Stat command output
[junit] 2017-09-29 00:20:21,584 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1040] - Closed socket connection for client 
/127.0.0.1:53430 (no session established for client)
[junit] 2017-09-29 00:20:21,584 [myid:] - INFO  [main:JMXEnv@230] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2017-09-29 00:20:21,587 [myid:] - INFO  [main:JMXEnv@247] - 
expect:InMemoryDataTree
[junit] 2017-09-29 00:20:21,587 [myid:] - INFO  [main:JMXEnv@251] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2017-09-29 00:20:21,587 [myid:] - INFO  [main:JMXEnv@247] - 
expect:StandaloneServer_port
[junit] 2017-09-29 00:20:21,587 [myid:] - INFO  [main:JMXEnv@251] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2017-09-29 00:20:21,588 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 35696
[junit] 2017-09-29 00:20:21,588 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2017-09-29 00:20:21,588 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2017-09-29 00:20:21,588 [myid:] - INFO  [main:ClientBase@566] - 
tearDown starting
[junit] 2017-09-29 00:20:21,654 [myid:] - INFO  [main:ZooKeeper@687] - 
Session: 0x101b7a44ca2 closed
[junit] 2017-09-29 00:20:21,654 [myid:] - INFO  [main:ClientBase@536] - 
STOPPING server
[junit] 2017-09-29 00:20:21,654 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@520] - EventThread shut down for 
session: 0x101b7a44ca2
[junit] 2017-09-29 00:20:21,654 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@242] - 
NIOServerCnxn factory exited run method
[junit] 2017-09-29 00:20:21,654 [myid:] - INFO  [main:ZooKeeperServer@501] 
- shutting down
[junit] 2017-09-29 00:20:21,655 [myid:] - ERROR [main:ZooKeeperServer@468] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-09-29 00:20:21,655 [myid:] - INFO  
[main:SessionTrackerImpl@226] -

Success: ZOOKEEPER- PreCommit Build #1069

2017-09-28 Thread Apache Jenkins Server

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1069/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 67.32 MB...]
 [exec]   
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] +0 tests included.  The patch appears to be a documentation 
patch that doesn't require 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 does not introduce any new Findbugs 
(version 3.0.1) 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-github-pr-build/1069//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1069//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1069//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Error: No value specified for option "issue"
 [exec] 38fd7ee5967371ef81746495cf45bb6ef2541636 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
‘/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess’
 and 
‘/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess’
 are the same file

BUILD SUCCESSFUL
Total time: 17 minutes 21 seconds
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2807
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Success
Sending email for trigger: Success
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

Failed: ZOOKEEPER- PreCommit Build #1070

2017-09-28 Thread Apache Jenkins Server

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1070/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 5.95 KB...]
 [exec] Pull request id: 385
 [exec]   % Total% Received % Xferd  Average Speed   TimeTime 
Time  Current
 [exec]  Dload  Upload   Total   Spent
Left  Speed
 [exec] 
 [exec] Pull request title: ZOOKEEPER-2906: The OWASP dependency check jar 
should not be included?
 [exec] Defect number: ZOOKEEPER-2906
 [exec] - Parsed args, going to checkout -
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Testing patch for pull request 385.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] 
 [exec]   0 00 00 0  0  0 --:--:-- --:--:-- 
--:--:-- 0100   1410   1410 0443  0 --:--:-- --:--:-- 
--:--:--   444
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec]  Pre-build trunk to verify trunk stability and javac warnings
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] /home/jenkins/tools/ant/apache-ant-1.9.9/bin/ant  
-Djavac.args=-Xlint -Xmaxwarns 1000 
-Djava5.home=/home/jenkins/tools/java5/latest 
-Dforrest.home=/home/jenkins/tools/forrest/latest -DZookeeperPatchProcess= 
clean tar > 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess/trunkJavacWarnings.txt
 2>&1
 [exec] Trunk compilation is broken?
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec]   0 00 00 0  0  0 --:--:-- --:--:-- 
--:--:-- 0100  63360  63360 0   8149  0 --:--:-- --:--:-- 
--:--:-- 6187kmv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml:1737:
 exec returned: 1

Total time: 33 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2906
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
No tests ran.

Success: ZOOKEEPER- PreCommit Build #1066

2017-09-28 Thread Apache Jenkins Server

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1066/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 34.37 MB...]
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] +1 tests included.  The patch appears to include 1 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 does not introduce any new Findbugs 
(version 3.0.1) 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-github-pr-build/1066//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1066//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1066//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] 4e7ffc1230b9e5991f1cb8ad3fc149b3b583f8f1 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD SUCCESSFUL
Total time: 35 minutes 49 seconds
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2906
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Success
Sending email for trigger: Success
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

[jira] [Commented] (ZOOKEEPER-2906) The OWASP dependency check jar should not be included in the default classpath

2017-09-28 Thread Hadoop QA (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185107#comment-16185107
 ] 

Hadoop QA commented on ZOOKEEPER-2906:
--

+1 overall.  GitHub Pull Request  Build
  

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 1 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 does not introduce any new Findbugs (version 3.0.1) 
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-github-pr-build/1066//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1066//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1066//console

This message is automatically generated.

> The OWASP dependency check jar should not be included in the default classpath
> --
>
> Key: ZOOKEEPER-2906
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2906
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.5.4, 3.6.0, 3.4.11
>Reporter: Abraham Fine
>Assignee: Abraham Fine
>
> The owasp dependency-check-ant jar that we use contains a SLF4J binding that 
> can break logging. We should move it into a separate classpath. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Failed: ZOOKEEPER- PreCommit Build #1065

2017-09-28 Thread Apache Jenkins Server

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1065/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 72.34 MB...]
 [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 3.0.1) 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-github-pr-build/1065//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1065//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1065//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] 8353ff3e3741477e6b17816c2a86aa1b0656a57a logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml:1704:
 exec returned: 1

Total time: 13 minutes 5 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[Fast Archiver] Compressed 575.04 KB of artifacts by 33.4% relative to #1061
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2906
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
1 tests failed.
FAILED:  org.apache.zookeeper.test.FLETest.testTripleElection

Error Message:
Fewer than a a majority has joined

Stack Trace:
junit.framework.AssertionFailedError: Fewer than a a majority has joined
at org.apache.zookeeper.test.FLETest.runElection(FLETest.java:362)
at 
org.apache.zookeeper.test.FLETest.testTripleElection(FLETest.java:287)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)

[jira] [Commented] (ZOOKEEPER-2906) The OWASP dependency check jar should not be included in the default classpath

2017-09-28 Thread Hadoop QA (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185079#comment-16185079
 ] 

Hadoop QA commented on ZOOKEEPER-2906:
--

-1 overall.  GitHub Pull Request  Build
  

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 1 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 does not introduce any new Findbugs (version 3.0.1) 
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-github-pr-build/1065//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1065//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1065//console

This message is automatically generated.

> The OWASP dependency check jar should not be included in the default classpath
> --
>
> Key: ZOOKEEPER-2906
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2906
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.5.4, 3.6.0, 3.4.11
>Reporter: Abraham Fine
>Assignee: Abraham Fine
>
> The owasp dependency-check-ant jar that we use contains a SLF4J binding that 
> can break logging. We should move it into a separate classpath. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ZOOKEEPER-1363) Categorise unit tests by 'test-commit', 'full-test' etc

2017-09-28 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185071#comment-16185071
 ] 

ASF GitHub Bot commented on ZOOKEEPER-1363:
---

Github user afine commented on the issue:

https://github.com/apache/zookeeper/pull/375
  
verified that jenkins is running the same number of tests with this patch 
as it did before. The list of slow tests also appears to be reasonable. 

small nitpick, wouldn't it make more sense to have a test category called 
"fast" and use an exclusion list rather than include special logic for "slow"?


> Categorise unit tests by 'test-commit', 'full-test' etc
> ---
>
> Key: ZOOKEEPER-1363
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1363
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: build, tests
>Reporter: Henry Robinson
>Assignee: Mark Fenes
>  Labels: newbie
>
> As discussed on the list, it would be good to split the Java test suite into 
> categories so that it's easy to run a small set of unit tests against a 
> patch, and to leave Jenkins to run the full suite of stress tests etc. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] zookeeper issue #375: ZOOKEEPER-1363: Categorise unit tests by 'test-commit'...

2017-09-28 Thread afine

Github user afine commented on the issue:

https://github.com/apache/zookeeper/pull/375
  
verified that jenkins is running the same number of tests with this patch 
as it did before. The list of slow tests also appears to be reasonable. 

small nitpick, wouldn't it make more sense to have a test category called 
"fast" and use an exclusion list rather than include special logic for "slow"?


---

[jira] [Commented] (ZOOKEEPER-2906) The OWASP dependency check jar should not be included in the default classpath

2017-09-28 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184978#comment-16184978
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2906:
---

Github user afine commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/384#discussion_r141748009
  
--- Diff: build.xml ---
@@ -121,6 +121,7 @@ xmlns:cs="antlib:com.puppycrawl.tools.checkstyle.ant">
 
 
 
+
--- End diff --

the reports are output to build/test/owasp/ in order to match what we do 
with clover
so i felt it was best to follow convention rather than drop the actual 
report in with the dependencies


> The OWASP dependency check jar should not be included in the default classpath
> --
>
> Key: ZOOKEEPER-2906
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2906
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.5.4, 3.6.0, 3.4.11
>Reporter: Abraham Fine
>Assignee: Abraham Fine
>
> The owasp dependency-check-ant jar that we use contains a SLF4J binding that 
> can break logging. We should move it into a separate classpath. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] zookeeper pull request #384: ZOOKEEPER-2906: The OWASP dependency check jar ...

2017-09-28 Thread afine

Github user afine commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/384#discussion_r141748009
  
--- Diff: build.xml ---
@@ -121,6 +121,7 @@ xmlns:cs="antlib:com.puppycrawl.tools.checkstyle.ant">
 
 
 
+
--- End diff --

the reports are output to build/test/owasp/ in order to match what we do 
with clover
so i felt it was best to follow convention rather than drop the actual 
report in with the dependencies


---

[GitHub] zookeeper pull request #384: ZOOKEEPER-2906: The OWASP dependency check jar ...

2017-09-28 Thread afine

Github user afine commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/384#discussion_r141748582
  
--- Diff: build.xml ---
@@ -1558,8 +1565,8 @@ xmlns:cs="antlib:com.puppycrawl.tools.checkstyle.ant">
classpathref="releaseaudit-classpath"/>
 
 
-
--- End diff --

+1


---

[jira] [Commented] (ZOOKEEPER-2906) The OWASP dependency check jar should not be included in the default classpath

2017-09-28 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184981#comment-16184981
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2906:
---

Github user afine commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/384#discussion_r141748582
  
--- Diff: build.xml ---
@@ -1558,8 +1565,8 @@ xmlns:cs="antlib:com.puppycrawl.tools.checkstyle.ant">
classpathref="releaseaudit-classpath"/>
 
 
-
--- End diff --

+1


> The OWASP dependency check jar should not be included in the default classpath
> --
>
> Key: ZOOKEEPER-2906
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2906
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.5.4, 3.6.0, 3.4.11
>Reporter: Abraham Fine
>Assignee: Abraham Fine
>
> The owasp dependency-check-ant jar that we use contains a SLF4J binding that 
> can break logging. We should move it into a separate classpath. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Failed: ZOOKEEPER- PreCommit Build #1064

2017-09-28 Thread Apache Jenkins Server

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1064/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1.64 MB...]
 [exec] +0 tests included.  The patch appears to be a documentation 
patch that doesn't require 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 does not introduce any new Findbugs 
(version 3.0.1) 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-github-pr-build/1064//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1064//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1064//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Error: No value specified for option "issue"
 [exec] c366c1c29caf14bcc170b6ec646bcd848cbedbe1 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
‘/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess’
 and 
‘/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess’
 are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml:1696:
 exec returned: 1

Total time: 12 minutes 8 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[Fast Archiver] Compressed 576.26 KB of artifacts by 33.3% relative to #1061
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2887
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
6 tests failed.
FAILED:  
org.apache.zookeeper.server.quorum.Zab1_0Test.testNormalFollowerRunWithDiff

Error Message:
expected:<4294967298> but was:<0>

Stack Trace:
junit.framework.AssertionFailedError: expected:<4294967298> but was:<0>
at 
org.apache.zookeeper.server.quorum.Zab1_0Test$5.converseWithFollower(Zab1_0Test.java:869)
at 
org.apache.zookeeper.server.quorum.Zab1_0Test.testFollowerConversation(Zab1_0Test.java:517)
at 
org.apache.zookeeper.server.quorum.Zab1_0Test.testNormalFollowerRunWithDiff(Zab1_0Test.java:784)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)


FAILED:  
org.apache.zookeeper.test.WatchEventWhenAutoResetTest.testNodeDataChanged

Error Message:
expected: but was:

Stack Trace:
junit.framework.AssertionFailedError: expected: but 
was:
at 
org.apache.zookeeper.test.WatchEventWhenAutoResetTest$EventsWatcher.assertEvent(WatchEventWhenAutoResetTest.java:67)
at 
org.apache.zookeeper.test.WatchEventWhenAutoResetTest.testNodeDataChanged(WatchEventWhenAutoResetTest.java:126)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)


FAILED:  
org.apache.zookeepe

[jira] [Updated] (ZOOKEEPER-2907) Logged request buffer isn't useful

2017-09-28 Thread Jordan Zimmerman (JIRA)


 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jordan Zimmerman updated ZOOKEEPER-2907:

Description: 
There are two places in the server code that log request errors with a message 
ala "Dumping request buffer..." followed by a hex dump of the request buffer. 
There are 2 major problems with this output:

# The request type is not output
# The byte-to-hex inline code doesn't pad numbers < 16

These two combine to make the output data nearly useless.

PrepRequestProcessor#pRequest() and FinalRequestProcessor#processRequest()

  was:
There are two places in the server code that log request errors with a message 
ala "Dumping request buffer..." followed by a hex dump of the request buffer. 
There are 2 major problems with this output:

# The request type is not output
# The byte-to-hex inline code doesn't pad numbers < 16

These two combine to make the output data nearly useless.


> Logged request buffer isn't useful
> --
>
> Key: ZOOKEEPER-2907
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2907
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Affects Versions: 3.4.10, 3.5.3
>Reporter: Jordan Zimmerman
>Priority: Minor
>
> There are two places in the server code that log request errors with a 
> message ala "Dumping request buffer..." followed by a hex dump of the request 
> buffer. There are 2 major problems with this output:
> # The request type is not output
> # The byte-to-hex inline code doesn't pad numbers < 16
> These two combine to make the output data nearly useless.
> PrepRequestProcessor#pRequest() and FinalRequestProcessor#processRequest()



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ZOOKEEPER-2907) Logged request buffer isn't useful

2017-09-28 Thread Jordan Zimmerman (JIRA)

Jordan Zimmerman created ZOOKEEPER-2907:
---

 Summary: Logged request buffer isn't useful
 Key: ZOOKEEPER-2907
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2907
 Project: ZooKeeper
  Issue Type: Improvement
  Components: server
Affects Versions: 3.5.3, 3.4.10
Reporter: Jordan Zimmerman
Priority: Minor


There are two places in the server code that log request errors with a message 
ala "Dumping request buffer..." followed by a hex dump of the request buffer. 
There are 2 major problems with this output:

# The request type is not output
# The byte-to-hex inline code doesn't pad numbers < 16

These two combine to make the output data nearly useless.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] zookeeper issue #386: Cmake fixes

2017-09-28 Thread phunt

Github user phunt commented on the issue:

https://github.com/apache/zookeeper/pull/386
  
@proller minor issue but please update this PR summary/description to be 
consistent with our policies (take a look at most of the other PRs) - also see 
"generate a pr" here 
https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToContribute


---

[GitHub] zookeeper pull request #386: Cmake fixes

2017-09-28 Thread phunt

Github user phunt commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/386#discussion_r141674581
  
--- Diff: src/c/CMakeLists.txt ---
@@ -14,14 +14,13 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-cmake_minimum_required(VERSION 3.6)
+cmake_minimum_required(VERSION 3.5)
 
 project(zookeeper VERSION 3.5.3)
--- End diff --

@andschwa - please note, this is a separate issue from this patch, but 
something we need to address. Notice that the version is incorrect here - it 
should be 3.6.0 for master. 

Which brings up another issue - version updates in our source files is 
currently a manual process, see "update the version" references here: 
https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToRelease+using+git I 
believe we will need to add cmake to this list as well.

I also see that at some point the version has not been updated properly. 
iirc all of the versions should be the upcoming release, not the last one.

Andrew would you mind creating a JIRA/patch to address all of these? 
Alternately the cmake at a minimum. If anyone has ideas how to do a better job 
on this perhaps we should consider that as well.


---

Failed: ZOOKEEPER- PreCommit Build #1063

2017-09-28 Thread Apache Jenkins Server

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1063/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1.61 MB...]
 [exec] +1 tests included.  The patch appears to include 2 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 does not introduce any new Findbugs 
(version 3.0.1) 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-github-pr-build/1063//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1063//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1063//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Error: No value specified for option "issue"
 [exec] 76080c42586f5080b0e14bdc061a14dde265330f logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml:1696:
 exec returned: 1

Total time: 12 minutes 4 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[Fast Archiver] Compressed 576.27 KB of artifacts by 33.3% relative to #1061
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Could not determine description.
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
4 tests failed.
FAILED:  
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testInconsistentPeerType

Error Message:
Should warn about inconsistent peer type

Stack Trace:
junit.framework.AssertionFailedError: Should warn about inconsistent peer type
at 
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testInconsistentPeerType(QuorumPeerMainTest.java:551)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)


FAILED:  
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testQuorumDefaults

Error Message:
fastleaderelection used

Stack Trace:
junit.framework.AssertionFailedError: fastleaderelection used
at 
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testQuorumDefaults(QuorumPeerMainTest.java:674)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)


FAILED:  
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testBadPeerAddressInQuorum

Error Message:
complains about host

Stack Trace:
junit.framework.AssertionFailedError: complains about host
at 
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testBadPeerAddressInQuorum(QuorumPeerMainTest.java:464)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvo

[GitHub] zookeeper issue #386: Cmake fixes

2017-09-28 Thread phunt

Github user phunt commented on the issue:

https://github.com/apache/zookeeper/pull/386
  
Tried it on ubuntu 15.04 (via docker run) and it looks like it fails. Min 
of 3.5 seems reasonable to me unless someone else wants to do more legwork. 
Thanks!

$ cmake --version
cmake version 3.0.2

[ 33%] Building C object CMakeFiles/cli.dir/src/cli.c.o
Linking C executable cli
/usr/bin/ld: cannot find -lThreads::Threads
collect2: error: ld returned 1 exit status
CMakeFiles/cli.dir/build.make:87: recipe for target 'cli' failed
make[2]: *** [cli] Error 1
CMakeFiles/Makefile2:61: recipe for target 'CMakeFiles/cli.dir/all' failed
make[1]: *** [CMakeFiles/cli.dir/all] Error 2
Makefile:86: recipe for target 'all' failed
make: *** [all] Error 2
$ 


---

[GitHub] zookeeper issue #386: Cmake fixes

2017-09-28 Thread phunt

Github user phunt commented on the issue:

https://github.com/apache/zookeeper/pull/386
  
> someone's gonna complain eventually

to be fair that's probably going to happen regardless given new (followon I 
mean) patches are unlikely to verify all the versions, esp the old ones that 
are hard to come by.


---

[GitHub] zookeeper issue #386: Cmake fixes

2017-09-28 Thread phunt

Github user phunt commented on the issue:

https://github.com/apache/zookeeper/pull/386
  
FYI - this is me:

$ cmake --version
cmake version 3.7.2


---

Success: ZOOKEEPER- PreCommit Build #1061

2017-09-28 Thread Apache Jenkins Server

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1061/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 72.00 MB...]
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] +1 tests included.  The patch appears to include 7 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 does not introduce any new Findbugs 
(version 3.0.1) 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-github-pr-build/1061//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1061//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1061//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] c0b7c424b8be80678fb60cd4762347c6494263bb logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
‘/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess’
 and 
‘/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess’
 are the same file

BUILD SUCCESSFUL
Total time: 18 minutes 1 second
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2901
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Success
Sending email for trigger: Success
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

[jira] [Commented] (ZOOKEEPER-2901) Session ID that is negative causes mis-calculation of Ephemeral Type

2017-09-28 Thread Hadoop QA (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184384#comment-16184384
 ] 

Hadoop QA commented on ZOOKEEPER-2901:
--

+1 overall.  GitHub Pull Request  Build
  

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 7 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 does not introduce any new Findbugs (version 3.0.1) 
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-github-pr-build/1061//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1061//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1061//console

This message is automatically generated.

> Session ID that is negative causes mis-calculation of Ephemeral Type
> 
>
> Key: ZOOKEEPER-2901
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2901
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.5.3
> Environment: Running 3.5.3-beta in Docker container
>Reporter: Mark Johnson
>Assignee: Jordan Zimmerman
>Priority: Blocker
>
> In the code that determines the EphemeralType it is looking at the owner 
> (which is the client ID or connection ID):
> EphemeralType.java:
>public static EphemeralType get(long ephemeralOwner) {
>if (ephemeralOwner == CONTAINER_EPHEMERAL_OWNER) {
>return CONTAINER;
>}
>if (ephemeralOwner < 0) {
>return TTL;
>}
>return (ephemeralOwner == 0) ? VOID : NORMAL;
>}
> However my connection ID is:
> header.getClientId(): -720548323429908480
> This causes the code to think this is a TTL Ephemeral node instead of a
> NORMAL Ephemeral node.
> This also explains why this is random - if my client ID is non-negative
> then the node gets added correctly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ZOOKEEPER-2901) Session ID that is negative causes mis-calculation of Ephemeral Type

2017-09-28 Thread Hadoop QA (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184381#comment-16184381
 ] 

Hadoop QA commented on ZOOKEEPER-2901:
--

-1 overall.  GitHub Pull Request  Build
  

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 7 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 does not introduce any new Findbugs (version 3.0.1) 
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-github-pr-build/1062//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1062//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1062//console

This message is automatically generated.

> Session ID that is negative causes mis-calculation of Ephemeral Type
> 
>
> Key: ZOOKEEPER-2901
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2901
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.5.3
> Environment: Running 3.5.3-beta in Docker container
>Reporter: Mark Johnson
>Assignee: Jordan Zimmerman
>Priority: Blocker
>
> In the code that determines the EphemeralType it is looking at the owner 
> (which is the client ID or connection ID):
> EphemeralType.java:
>public static EphemeralType get(long ephemeralOwner) {
>if (ephemeralOwner == CONTAINER_EPHEMERAL_OWNER) {
>return CONTAINER;
>}
>if (ephemeralOwner < 0) {
>return TTL;
>}
>return (ephemeralOwner == 0) ? VOID : NORMAL;
>}
> However my connection ID is:
> header.getClientId(): -720548323429908480
> This causes the code to think this is a TTL Ephemeral node instead of a
> NORMAL Ephemeral node.
> This also explains why this is random - if my client ID is non-negative
> then the node gets added correctly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Failed: ZOOKEEPER- PreCommit Build #1062

2017-09-28 Thread Apache Jenkins Server

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1062/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 72.14 MB...]
 [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 3.0.1) 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-github-pr-build/1062//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1062//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1062//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] 8af1b5c96a33826c942eb1d40e5368819961a000 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml:1703:
 exec returned: 1

Total time: 15 minutes 16 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[Fast Archiver] Compressed 574.73 KB of artifacts by 61.2% relative to #1054
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2901
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
1 tests failed.
FAILED:  
org.apache.zookeeper.server.quorum.Zab1_0Test.testNormalFollowerRunWithDiff

Error Message:
expected:<4294967298> but was:<0>

Stack Trace:
junit.framework.AssertionFailedError: expected:<4294967298> but was:<0>
at 
org.apache.zookeeper.server.quorum.Zab1_0Test$5.converseWithFollower(Zab1_0Test.java:869)
at 
org.apache.zookeeper.server.quorum.Zab1_0Test.testFollowerConversation(Zab1_0Test.java:517)
at 
org.apache.zookeeper.server.quorum.Zab1_0Test.testNormalFollowerRunWithDiff(Zab1_0Test.java:784)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)

[GitHub] zookeeper issue #386: Cmake fixes

2017-09-28 Thread andschwa

Github user andschwa commented on the issue:

https://github.com/apache/zookeeper/pull/386
  
If you've only tested with 3.5, then this should be set to 3.5 until it's 
tested with lower.

CMake actually does add features in minor patches. It will _probably_ work, 
but if it doesn't, then someone's gonna complain eventually.


---

[GitHub] zookeeper issue #386: Cmake fixes

2017-09-28 Thread proller

Github user proller commented on the issue:

https://github.com/apache/zookeeper/pull/386
  
No. i only test with cmake version 3.5.1
but it should works even with cmake 2.8


---

[GitHub] zookeeper issue #386: Cmake fixes

2017-09-28 Thread phunt

Github user phunt commented on the issue:

https://github.com/apache/zookeeper/pull/386
  
+1, lgtm - tested on Ubuntu 17.04 and everything compiled fine (a number of 
warnings from the compiler but that might be new settings or more recent gcc?)

@andschwa - you've been working on the cmake support, any review comments?


---

Failed: ZOOKEEPER- PreCommit Build #1058

2017-09-28 Thread Apache Jenkins Server

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1058/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1.66 MB...]
 [exec] +1 tests included.  The patch appears to include 2 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 does not introduce any new Findbugs 
(version 3.0.1) 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-github-pr-build/1058//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1058//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1058//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Error: No value specified for option "issue"
 [exec] cc68f452af9ce4654ebb2126ba71e11d20157bfc logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml:1696:
 exec returned: 1

Total time: 11 minutes 39 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[Fast Archiver] Compressed 576.23 KB of artifacts by 50.0% relative to #1054
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Could not determine description.
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
4 tests failed.
FAILED:  
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testInconsistentPeerType

Error Message:
Should warn about inconsistent peer type

Stack Trace:
junit.framework.AssertionFailedError: Should warn about inconsistent peer type
at 
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testInconsistentPeerType(QuorumPeerMainTest.java:551)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)


FAILED:  
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testQuorumDefaults

Error Message:
fastleaderelection used

Stack Trace:
junit.framework.AssertionFailedError: fastleaderelection used
at 
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testQuorumDefaults(QuorumPeerMainTest.java:674)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)


FAILED:  
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testBadPeerAddressInQuorum

Error Message:
complains about host

Stack Trace:
junit.framework.AssertionFailedError: complains about host
at 
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testBadPeerAddressInQuorum(QuorumPeerMainTest.java:464)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInv

[GitHub] zookeeper pull request #386: Cmake fixes

2017-09-28 Thread proller

GitHub user proller opened a pull request:

https://github.com/apache/zookeeper/pull/386

Cmake fixes

1. decrease cmake version (to allow compile on some old systems)
2. do not use global include_directories (and auto include when linking to 
external projects)
3. replace CMAKE_SOURCE_DIR with CMAKE_CURRENT_SOURCE_DIR - it allow 
compile zookeper added to other project with add_subdirectory()

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ClickHouse-Extras/zookeeper clickhouse_cmake

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zookeeper/pull/386.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #386


commit a338479b84dd92c4858d47c5a3a09483abd427b4
Author: proller 
Date:   2017-09-28T14:40:38Z

Cmake fixes:
1. decrease cmake version (to allow compile on some old systems)
2. do not use global include_directories (and auto include when linking to 
external projects)
3. replace CMAKE_SOURCE_DIR with CMAKE_CURRENT_SOURCE_DIR - it allow 
compile zookeper added to other project with add_subdirectory()




---

[jira] [Commented] (ZOOKEEPER-2890) Local automatic variable is left uninitialized and then freed.

2017-09-28 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184235#comment-16184235
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2890:
---

Github user phunt commented on the issue:

https://github.com/apache/zookeeper/pull/359
  
Hi @xoiss please update this PR to follow the guidelines in "generate a 
pull request" here: 
https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToContribute - in 
particular wrt the summary and description text which really helps folks 
identifying which PRs to prioritize. Thanks!


> Local automatic variable is left uninitialized and then freed.
> --
>
> Key: ZOOKEEPER-2890
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2890
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: c client
>Affects Versions: 3.4.10
> Environment: Linux ubuntu 4.4.0-87-generic
> gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
> https://github.com/apache/zookeeper.git
> branch-3.4
>Reporter: Alexander A. Strelets
>Priority: Critical
>  Labels: easyfix
> Fix For: 3.4.10
>
>
> ZooKeeper C Client *+single thread+* build
> Function *_deserialize_response()_*, in _case COMPLETION_STRING_, uses local 
> automatic variable *_struct CreateResponse res_* which is +left 
> uninitialized+ and passed to the function _deserialize_GetACLResponse()_ and 
> then to _deallocate_GetACLResponse()_.
> The _deserialize_ function, which is called the first, is expected to assign 
> the _res_ variable with a value from the parsed _struct iarchive *ia_. But, 
> if _ia_ contains for example insufficient amount of bytes the 
> _deserialize_String()_ function refuses of assigning a value to _res_, and 
> _res_ stays uninitialized (the true case is described below). Then, the 
> _deallocate_ function calls _deallocate_String()_ passing uninitialized _res_ 
> with arguments. If incidentally the memory region in the program stack under 
> the _res_ was not equal to NULL, the last call +leads to _free()_ by invalid 
> address+.
> The true case: this happens when an active _multi_ request with _create_ 
> sub-request is completed on call to _zookeeper_close()_ with the so called 
> "Fake response" which is fabricated by the function _free_completions()_. 
> Such response includes only the header but +zero bytes for the body+. The 
> significant condition is that the _create_ request is not a stand-alone one, 
> but namely a sub-request within the _multi_ request. In this case the 
> _deserialize_response()_ is called recursively (for each sub-request), and 
> when it is called for the _create_ subrequest (from the nested 
> _deserialize_multi()_) the _failed_ parameter is assigned with false (0), so 
> the _if (failed)_ condition branches to the _else_ part. Note that in the 
> stand-alone create-request case this does not occur.
> *I suspect this may happen not only due to call to _zookeeper_close()_ but on 
> reception of a true multi-response from the server* containing insufficient 
> number of bytes (I'm not sure if it can be a proper response from the server 
> with an error overall status and empty or insufficient payload).
> This is a proposed fix: https://github.com/apache/zookeeper/pull/359



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ZOOKEEPER-2891) SIGABRT from assert during fake completion on zookeeper_close.

2017-09-28 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184236#comment-16184236
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2891:
---

Github user phunt commented on the issue:

https://github.com/apache/zookeeper/pull/360
  
Hi @xoiss please update this PR to follow the guidelines in "generate a 
pull request" here: 
https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToContribute - in 
particular wrt the summary and description text which really helps folks 
identifying which PRs to prioritize. Thanks!


> SIGABRT from assert during fake completion on zookeeper_close.
> --
>
> Key: ZOOKEEPER-2891
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2891
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: c client
>Affects Versions: 3.4.10
> Environment: Linux ubuntu 4.4.0-87-generic
> gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
> https://github.com/apache/zookeeper.git
> branch-3.4
>Reporter: Alexander A. Strelets
>Priority: Critical
>  Labels: easyfix
> Fix For: 3.4.10
>
>
> ZooKeeper C Client *+single thread+* build
> Function *_deserialize_multi()_* hits *_assert(entry)_* when called for the 
> so called "Fake response" which is fabricated by the function 
> _free_completions()_ for example when _zookeeper_close()_ is called while 
> there is a pending _multi_ request.
> Such fake response includes only the header but zero bytes for the body. Due 
> to this {{deserialize_MultiHeader(ia, "multiheader", &mhdr)}}, which is 
> called repeatedly for each {{completion_list_t *entry = 
> dequeue_completion(clist)}}, does not assign the _mhdr_ and keeps _mhdr.done 
> == 0_ as it was originally initialized. Consequently the _while (!mhdr.done)_ 
> does not ever end, and finally falls into the _assert(entry)_ with _entry == 
> NULL_ when all sub-requests are "completed". ~// Normally on my platform 
> assert raises SIGABRT.~
> I propose to instruct the _deserialize_multi()_ function to break the loop on 
> _entry == NULL_ if it was called for an unsuccessfull overal status of the 
> multi response, and in particular for the fake response having _ZCLOSING_ 
> (-116) status. I have introduced the _rc0_ parameter for this.
> *Another issue* with this function is that even if the while-loop exited 
> properly, this function returns _rc == 0_, and this return code +overrides+ 
> the true status value with {{rc = deserialize_multi(xid, cptr, ia, rc)}} in 
> the _deserialize_response()_ function. So, the _multi_ response callback 
> +handler would be called with _rc == ZOK_ instead of _rc == ZCLOSING_+ which 
> is strictly wrong.
> To fix this I propose initializing _rc_ with the introduced _rc0_ instead of 
> zero (which is _ZOK_ indeed).
> This is a proposed fix: https://github.com/apache/zookeeper/pull/360
> [upd]
> It looks like about the same problem is described in ZOOKEEPER-1636
> However, the patch proposed in this ticket also remedies the second linked 
> problem: reporting ZCLOSING status (as required) to the multi-request 
> completion handler.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ZOOKEEPER-2894) Memory and completions leak on zookeeper_close.

2017-09-28 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184237#comment-16184237
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2894:
---

Github user phunt commented on the issue:

https://github.com/apache/zookeeper/pull/363
  
Hi @xoiss please update this PR to follow the guidelines in "generate a 
pull request" here: 
https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToContribute - in 
particular wrt the summary and description text which really helps folks 
identifying which PRs to prioritize. Thanks!


> Memory and completions leak on zookeeper_close.
> ---
>
> Key: ZOOKEEPER-2894
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2894
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: c client
>Affects Versions: 3.4.10
> Environment: Linux ubuntu 4.4.0-87-generic
> gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
> https://github.com/apache/zookeeper.git
> branch-3.4
>Reporter: Alexander A. Strelets
>Priority: Critical
>  Labels: easyfix
> Fix For: 3.4.10
>
> Attachments: zk-will-free-zh-and-lose-completions.png
>
>
> ZooKeeper C Client *+single thread+* build
> First of all, ZooKeeper C Client design allows calling _zookeeper_close()_ in 
> two ways:
> a) from a ZooKeeper callback handler (completion or watcher) which in turn is 
> called through _zookeeper_process()_
> b) and from other places -- i.e., when the call-stack does not pass through 
> any of zookeeper mechanics prior to enter into mentioned _zookeeper_close()_
> The issue described here below is +specific only to the case (b)+. So, it's 
> Ok with the case (a).
> When _zookeeper_close()_ is called in the (b) way, the following happens:
> 1. +If there are requests waiting for responses in _zh.sent_requests_ queue+, 
> they all are removed from this queue and each of them is "completed" with 
> personal fake response having status ZCLOSING. Such fake responses are put 
> into _zh.completions_to_process_ queue. It's Ok
> 2. But then, _zh.completions_to_process_ queue is left unhandled. +Neither 
> completion callbacks are called, nor dynamic memory allocated for fake 
> responses is freed+
> 3. Different structures within _zh_ are dismissed and finally _zh_ is freed
> This is illustrated on the screenshot attached to this ticket: you may see 
> that the next instruction to execute will be _free(zh)_ while 
> _zh.completions_to_process_ queue is not empty (see the "Variables" tab to 
> the right).
> Alternatively, the same situation but in the case (a) is handled properly -- 
> i.e., all completion callback handlers are truly called with ZCLOSING and the 
> memory is freed, both for subcases (a.1) when there is a failure like 
> connection-timeout, connection-closed, etc., or (a.2) there is not failure. 
> The reason is that any callback handler (completion or watcher) in the case 
> (a) is called from the _process_completions()_ function which runs in the 
> loop until _zh.completions_to_process_ queue gets empty. So, this function 
> guarantees this queue to be completely processed even if new completions 
> occur during reaction on previously queued completions.
> *Consequently:*
> 1. At least there is definitely the +memory leak+ in the case (b) -- all the 
> fake responses put into _zh.completions_to_process_ queue are lost after 
> _free(zh)_
> 2. And it looks like a great misbehavior not to call completions on sent 
> requests in the case (b) while they are called with ZCLOSING in the case (a) 
> -- so, I think it's not "by design" but a +completions leak+
> +To reproduce the case (b) do the following:+
> - open ZooKeeper session, connect to a server, receive and process 
> connected-watch, etc.
> - then somewhere +from the main events loop+ call for example _zoo_acreate()_ 
> with valid arguments -- it shall return ZOK
> - then, +immediately after it returned+, call _zookeeper_close()_
> - note that completion callback handler for _zoo_acreate()_ *will not be 
> called*
> +To reproduce the case (a) do the following:+
> - the same as above, open ZooKeeper session, connect to a server, receive and 
> process connected-watch, etc.
> - the same as above, somewhere from the main events loop call for example 
> _zoo_acreate()_ with valid arguments -- it shall return ZOK
> - but now don't call _zookeeper_close()_ immediately -- wait for completion 
> callback on the commenced request
> - when _zoo_acreate()_ completes, +from within its completion callback 
> handler+, call another _zoo_acreate()_ and immediately after it returned call 
> _zookeeper_close()_
> - note that completion callback handler for the second _zoo_acreate()_ *will 
> be called with ZCLOSING, unlike the case (b) described above*
> To fix this I prop

[GitHub] zookeeper issue #363: branch-3.4 -- bugfix -- ZOOKEEPER-2894

2017-09-28 Thread phunt

Github user phunt commented on the issue:

https://github.com/apache/zookeeper/pull/363
  
Hi @xoiss please update this PR to follow the guidelines in "generate a 
pull request" here: 
https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToContribute - in 
particular wrt the summary and description text which really helps folks 
identifying which PRs to prioritize. Thanks!


---

[GitHub] zookeeper issue #360: branch-3.4 -- bugfix -- ZOOKEEPER-2891

2017-09-28 Thread phunt

Github user phunt commented on the issue:

https://github.com/apache/zookeeper/pull/360
  
Hi @xoiss please update this PR to follow the guidelines in "generate a 
pull request" here: 
https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToContribute - in 
particular wrt the summary and description text which really helps folks 
identifying which PRs to prioritize. Thanks!


---

[GitHub] zookeeper issue #359: branch-3.4 -- bugfix -- ZOOKEEPER-2890

2017-09-28 Thread phunt

Github user phunt commented on the issue:

https://github.com/apache/zookeeper/pull/359
  
Hi @xoiss please update this PR to follow the guidelines in "generate a 
pull request" here: 
https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToContribute - in 
particular wrt the summary and description text which really helps folks 
identifying which PRs to prioritize. Thanks!


---

[jira] [Commented] (ZOOKEEPER-2901) Session ID that is negative causes mis-calculation of Ephemeral Type

2017-09-28 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184143#comment-16184143
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2901:
---

Github user Randgalt commented on the issue:

https://github.com/apache/zookeeper/pull/377
  
The integration above doesn't seem to update, but the build passes now.


> Session ID that is negative causes mis-calculation of Ephemeral Type
> 
>
> Key: ZOOKEEPER-2901
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2901
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.5.3
> Environment: Running 3.5.3-beta in Docker container
>Reporter: Mark Johnson
>Assignee: Jordan Zimmerman
>Priority: Blocker
>
> In the code that determines the EphemeralType it is looking at the owner 
> (which is the client ID or connection ID):
> EphemeralType.java:
>public static EphemeralType get(long ephemeralOwner) {
>if (ephemeralOwner == CONTAINER_EPHEMERAL_OWNER) {
>return CONTAINER;
>}
>if (ephemeralOwner < 0) {
>return TTL;
>}
>return (ephemeralOwner == 0) ? VOID : NORMAL;
>}
> However my connection ID is:
> header.getClientId(): -720548323429908480
> This causes the code to think this is a TTL Ephemeral node instead of a
> NORMAL Ephemeral node.
> This also explains why this is random - if my client ID is non-negative
> then the node gets added correctly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Major issue with Container Nodes/TTL nodes!!!

2017-09-28 Thread Jordan Zimmerman

I pulled in the build file changes and that fixed the tests - good news.

So, https://github.com/apache/zookeeper/pull/377 
 is ready.

-Jordan

> On Sep 27, 2017, at 11:07 PM, Jordan Zimmerman  
> wrote:
> 
> This is on Jenkins. 
> 
> https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1051/testReport/
>  
> 
> 
>> On Sep 27, 2017, at 11:06 PM, Patrick Hunt  wrote:
>> 
>> Check your classpath (typ the build/libs and build/test/libs directories) - 
>> how many log4j jar files do you have? Are there conflicting versions? (same 
>> jar diff versions I mean).
>> 
>> Patrick
>> 
>> On Wed, Sep 27, 2017 at 8:57 PM, Jordan Zimmerman 
>> mailto:jor...@jordanzimmerman.com>> wrote:
>> Now I'm getting a different error:
>> 
>> 2017-09-28 03:47:24,878 [myid:2] - ERROR [Thread-1:AppenderDynamicMBean@209] 
>> - Could not add DynamicLayoutMBean for 
>> [CONSOLE,layout=org.apache.log4j.PatternLayout].
>> javax.management.InstanceAlreadyExistsException: 
>> log4j:appender=CONSOLE,layout=org.apache.log4j.PatternLayout
>> 
>> 
>>> On Sep 27, 2017, at 1:17 PM, Jordan Zimmerman >> > wrote:
>>> 
>>> I didn't change anything. I branched from master. What should I do any 
>>> ideas?
>>> 
 On Sep 27, 2017, at 1:15 PM, Patrick Hunt >>> > wrote:
 
 Has the log4j configuration changed at all? iirc the console appender 
 needs to be setup for those tests to function.
 
 Patrick
 
 On Sat, Sep 23, 2017 at 8:01 AM, Jordan Zimmerman 
 mailto:jor...@jordanzimmerman.com>> wrote:
 There are 4 tests throwing NPEs in Jenkins due to:
 
 Layout layout = Logger.getRootLogger().getAppender("CONSOLE")
 .getLayout();
 
 Is this a known issue? Any workaround?
 
 -Jordan
 
> On Sep 21, 2017, at 9:17 AM, Jordan Zimmerman  > wrote:
> 
> In LeaderSessionTracker.java there is this bit of code:
> 
> if (!localSessionsEnabled
> || (getServerIdFromSessionId(sessionId) == serverId)) {
> throw new SessionExpiredException();
> }
> 
> "serverId" is a long. This can only work if Server IDs are 255 or less. I 
> realize this is in the docs. But is it enforced? See: 
> https://issues.apache.org/jira/browse/ZOOKEEPER-2503 
> 
> 
> 
> 
>> On Sep 20, 2017, at 3:10 PM, Raúl Gutiérrez Segalés 
>> mailto:r...@itevenworks.net>> wrote:
>> 
>> On 20 September 2017 at 12:54, Camille Fournier > > wrote:
>> Ok let's take this back to either public mailing list or jira. I'd write 
>> up
>> thoughts on jira and ask there+ml to look. I'll try to look tonight
>> 
>> Thanks Camille!
>> 
>> Also, I merged this originally so I will work with Jordan on getting 
>> this fixed. Let me know
>> when you have a write up of your proposed solution and I'll take a look. 
>> Thanks!
>> 
>> 
>> -rgs
>>  
>> 
>> 
>> On Sep 20, 2017 3:52 PM, "Jordan Zimmerman" > >
>> wrote:
>> 
>> > I'd like to fix it as my company and probably many others are now 
>> > using it
>> > in production. The question is how to fix it safely and correctly. Is 
>> > email
>> > the best way to discuss this? Jira? Something else?
>> >
>> > I must say that there appears to be a trivial fix but I need the ZK
>> > committers to think about this. In 
>> > SessionTrackerImpl#initializeNextSession()
>> > only some of the server ID bits are used. We could easily just mask 
>> > the 2
>> > high bits as well. But, what are the implications of this? Where is 
>> > this
>> > serverId byte used? What must be double checked?
>> >
>> > -Jordan
>> >
>> > On Sep 20, 2017, at 2:46 PM, Camille Fournier > > > wrote:
>> >
>> > Would you rather roll back the feature or put in a fix?
>> >
>> > On Sep 20, 2017 3:44 PM, "Jordan Zimmerman" 
>> > mailto:jor...@jordanzimmerman.com>>
>> > wrote:
>> >
>> >> Hey Folks,
>> >>
>> >> This is very serious. Please - let's discuss immediately. I'm not 
>> >> certain
>> >> how to fix this.
>> >>
>> >> -JZ
>> >>
>> >> On Sep 20, 2017, at 2:17 PM, Jordan Zimmerman 
>> >> mailto:jor...@jordanzimmerman.com>>
>> >> wrote:
>> >>
>> >> See: https://issues.apache.org/jira/browse/ZOOKEEPER-2901 
>> >> 
>> >>
>> >> It appears that the high order byte of a session ID is reserved for 
>> >> the
>> >> ServerID. I don't know how I cou

Success: ZOOKEEPER- PreCommit Build #1054

2017-09-28 Thread Apache Jenkins Server

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1054/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 71.11 MB...]
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] +1 tests included.  The patch appears to include 10 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 does not introduce any new Findbugs 
(version 3.0.1) 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-github-pr-build/1054//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1054//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1054//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] a93ac3d69efc2ab7472f4c0ca0b5fc89c1210172 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD SUCCESSFUL
Total time: 17 minutes 47 seconds
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2906
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Success
Sending email for trigger: Success
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

[GitHub] zookeeper issue #377: [ZOOKEEPER-2901] TTL Nodes don't work with Server IDs ...

2017-09-28 Thread Randgalt

Github user Randgalt commented on the issue:

https://github.com/apache/zookeeper/pull/377
  
The integration above doesn't seem to update, but the build passes now.


---

[jira] [Commented] (ZOOKEEPER-2901) Session ID that is negative causes mis-calculation of Ephemeral Type

2017-09-28 Thread Hadoop QA (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184138#comment-16184138
 ] 

Hadoop QA commented on ZOOKEEPER-2901:
--

+1 overall.  GitHub Pull Request  Build
  

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 10 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 does not introduce any new Findbugs (version 3.0.1) 
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-github-pr-build/1054//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1054//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1054//console

This message is automatically generated.

> Session ID that is negative causes mis-calculation of Ephemeral Type
> 
>
> Key: ZOOKEEPER-2901
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2901
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.5.3
> Environment: Running 3.5.3-beta in Docker container
>Reporter: Mark Johnson
>Assignee: Jordan Zimmerman
>Priority: Blocker
>
> In the code that determines the EphemeralType it is looking at the owner 
> (which is the client ID or connection ID):
> EphemeralType.java:
>public static EphemeralType get(long ephemeralOwner) {
>if (ephemeralOwner == CONTAINER_EPHEMERAL_OWNER) {
>return CONTAINER;
>}
>if (ephemeralOwner < 0) {
>return TTL;
>}
>return (ephemeralOwner == 0) ? VOID : NORMAL;
>}
> However my connection ID is:
> header.getClientId(): -720548323429908480
> This causes the code to think this is a TTL Ephemeral node instead of a
> NORMAL Ephemeral node.
> This also explains why this is random - if my client ID is non-negative
> then the node gets added correctly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

ZooKeeper_branch35_openjdk7 - Build # 684 - Still Failing

2017-09-28 Thread Apache Jenkins Server

See https://builds.apache.org/job/ZooKeeper_branch35_openjdk7/684/

###
## LAST 60 LINES OF THE CONSOLE 
###
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H16 (couchdbtest ubuntu xenial) in workspace 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_openjdk7
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url git://git.apache.org/zookeeper.git # timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
 > git --version # timeout=10
 > git fetch --tags --progress git://git.apache.org/zookeeper.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/branch-3.5^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/branch-3.5^{commit} # timeout=10
Checking out Revision 2b365357995eaba8950d2c294e87fd29bcd94423 
(refs/remotes/origin/branch-3.5)
Commit message: "ZOOKEEPER-2887: define dependency versions in build.xml to be 
easily overridden in build.properties"
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 2b365357995eaba8950d2c294e87fd29bcd94423
 > git rev-list 2b365357995eaba8950d2c294e87fd29bcd94423 # timeout=10
No emails were triggered.
Setting OPENJDK_7_ON_UBUNTU_ONLY__HOME=/usr/lib/jvm/java-7-openjdk-amd64/
[ZooKeeper_branch35_openjdk7] $ 
/home/jenkins/tools/ant/apache-ant-1.9.9/bin/ant -Dtest.output=yes 
-Dtest.junit.threads=8 -Dtest.junit.output.format=xml -Djavac.target=1.7 clean 
test-core-java
Error: JAVA_HOME is not defined correctly.
  We cannot execute /usr/lib/jvm/java-7-openjdk-amd64//bin/java
Build step 'Invoke Ant' marked build as failure
Recording test results
Setting OPENJDK_7_ON_UBUNTU_ONLY__HOME=/usr/lib/jvm/java-7-openjdk-amd64/
ERROR: Step ?Publish JUnit test result report? failed: Test reports were found 
but none of them are new. Did tests run? 
For example, 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_openjdk7/build/test/logs/TEST-org.apache.jute.BinaryInputArchiveTest.xml
 is 10 days old

Setting OPENJDK_7_ON_UBUNTU_ONLY__HOME=/usr/lib/jvm/java-7-openjdk-amd64/
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting OPENJDK_7_ON_UBUNTU_ONLY__HOME=/usr/lib/jvm/java-7-openjdk-amd64/
Setting OPENJDK_7_ON_UBUNTU_ONLY__HOME=/usr/lib/jvm/java-7-openjdk-amd64/



###
## FAILED TESTS (if any) 
##
No tests ran.

ZooKeeper_branch35_jdk7 - Build # 1126 - Still Failing

2017-09-28 Thread Apache Jenkins Server

See https://builds.apache.org/job/ZooKeeper_branch35_jdk7/1126/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 72.56 MB...]
[junit] 2017-09-28 08:50:18,307 [myid:] - WARN  [New I/O boss 
#3723:ClientCnxnSocketNetty$ZKClientHandler@439] - Exception caught: [id: 
0x98e2410b] EXCEPTION: java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:13979
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:13979
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
[junit] at 
org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
[junit] at 
org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
[junit] at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[junit] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[junit] at java.lang.Thread.run(Thread.java:745)
[junit] 2017-09-28 08:50:18,307 [myid:] - INFO  [New I/O boss 
#3723:ClientCnxnSocketNetty@208] - channel is told closing
[junit] 2017-09-28 08:50:18,307 [myid:127.0.0.1:13979] - INFO  
[main-SendThread(127.0.0.1:13979):ClientCnxn$SendThread@1231] - channel for 
sessionid 0x10641193c6c is lost, closing socket connection and attempting 
reconnect
[junit] 2017-09-28 08:50:18,593 [myid:127.0.0.1:14038] - INFO  
[main-SendThread(127.0.0.1:14038):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:14038. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-09-28 08:50:18,594 [myid:] - INFO  [New I/O boss 
#5219:ClientCnxnSocketNetty$1@127] - future isn't success, cause: {}
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:14038
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
[junit] at 
org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
[junit] at 
org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
[junit] at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[junit] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[junit] at java.lang.Thread.run(Thread.java:745)
[junit] 2017-09-28 08:50:18,594 [myid:] - WARN  [New I/O boss 
#5219:ClientCnxnSocketNetty$ZKClientHandler@439] - Exception caught: [id: 
0x6c44087e] EXCEPTION: java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:14038
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:14038
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
[junit] at 
org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
[junit] at 
org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
[junit] at 
java.util.concurrent.ThreadPoolExecutor

Success: ZOOKEEPER- PreCommit Build #1053

2017-09-28 Thread Apache Jenkins Server

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1053/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 33.15 MB...]
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] +1 tests included.  The patch appears to include 1 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 does not introduce any new Findbugs 
(version 3.0.1) 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-github-pr-build/1053//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1053//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1053//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] 4951c5eb2139eab7a0f5783fc71dca9fc8424bef logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
‘/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess’
 and 
‘/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess’
 are the same file

BUILD SUCCESSFUL
Total time: 36 minutes 17 seconds
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2906
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Success
Sending email for trigger: Success
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

[jira] [Commented] (ZOOKEEPER-2906) The OWASP dependency check jar should not be included in the default classpath

2017-09-28 Thread Hadoop QA (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16183849#comment-16183849
 ] 

Hadoop QA commented on ZOOKEEPER-2906:
--

+1 overall.  GitHub Pull Request  Build
  

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 1 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 does not introduce any new Findbugs (version 3.0.1) 
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-github-pr-build/1053//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1053//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1053//console

This message is automatically generated.

> The OWASP dependency check jar should not be included in the default classpath
> --
>
> Key: ZOOKEEPER-2906
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2906
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.5.4, 3.6.0, 3.4.11
>Reporter: Abraham Fine
>Assignee: Abraham Fine
>
> The owasp dependency-check-ant jar that we use contains a SLF4J binding that 
> can break logging. We should move it into a separate classpath. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Success: ZOOKEEPER- PreCommit Build #1052

2017-09-28 Thread Apache Jenkins Server

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1052/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 72.77 MB...]
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] +1 tests included.  The patch appears to include 1 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 does not introduce any new Findbugs 
(version 3.0.1) 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-github-pr-build/1052//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1052//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1052//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] a11ef864e63c3e3da2818506136117e85f326a4c logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD SUCCESSFUL
Total time: 19 minutes 36 seconds
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2906
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Success
Sending email for trigger: Success
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

Re: Major issue with Container Nodes/TTL nodes!!!

2017-09-28 Thread Abraham Fine

I submitted a JIRA (with patches) to resolve the OWASP related logging
issue here: https://issues.apache.org/jira/browse/ZOOKEEPER-2906
Thanks,
Abe


On Wed, Sep 27, 2017, at 21:37, Patrick Hunt wrote:
> I looked at the console output for the job you linked and there
> are tons of> 
>  [exec] junit.run-concurrent:
>  [exec]  [echo] Running 8 concurrent JUnit processes.
>  [exec] [junit] SLF4J: Class path contains multiple SLF4J
>  bindings.>  [exec] [junit] SLF4J: Found binding in 
> [jar:file:/home/jenkins/jenkins-slave/workspace/PreCommit-
>  ZOOKEEPER-github-pr-build/build/lib/dependency-check-ant-
>  2.1.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]>  [exec] 
> [junit] SLF4J: Found binding in 
> [jar:file:/home/jenkins/jenkins-slave/workspace/PreCommit-
>  ZOOKEEPER-github-pr-build/build/lib/slf4j-log4j12-
>  1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]>  [exec] 
> [junit] SLF4J: See
>  http://www.slf4j.org/codes.html#multiple_bindings for an
>  explanation.>  [exec] [junit] SLF4J: Actual binding is of type
>  [org.owasp.dependencycheck.ant.logging.AntLoggerFactory]> 
> Looks like this is related to the owasp changes that were incorporated
> recently. Try stubbing that out of your patch (perhaps git revert it
> in your branch) and see if it resolves this from the console output
> and whether it helps at all with the issue you've been seeing in the
> test itself.> 
> Patrick
> 
> On Wed, Sep 27, 2017 at 9:07 PM, Jordan Zimmerman
>  wrote:>> This is on Jenkins.
>> 
>> https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1051/testReport/>>
>>  > On Sep 27, 2017, at 11:06 PM, Patrick Hunt 
>>  > wrote:
>>  >
>>  > Check your classpath (typ the build/libs and build/test/libs
>>  > directories) - how many log4j jar files do you have? Are there
>>  > conflicting versions? (same jar diff versions I mean).
>>  >
>>  > Patrick
>>  >
>> > On Wed, Sep 27, 2017 at 8:57 PM, Jordan Zimmerman
>> > mailto:jor...@jordanzimmerman.com>>
>> > wrote:
>>  > Now I'm getting a different error:
>>  >
>>  > 2017-09-28 03:47:24,878 [myid:2] - ERROR [Thread-
>>  > 1:AppenderDynamicMBean@209] - Could not add DynamicLayoutMBean for
>>  > [CONSOLE,layout=org.apache.log4j.PatternLayout].
>>  > javax.management.InstanceAlreadyExistsException:
>>  > log4j:appender=CONSOLE,layout=org.apache.log4j.PatternLayout
>>  >
>>  >
>> >> On Sep 27, 2017, at 1:17 PM, Jordan Zimmerman
>> >> mailto:jor...@jordanzimmerman.com>>
>> >> wrote:
>>  >>
>>  >> I didn't change anything. I branched from master. What should I
>>  >> do any ideas?
>>  >>
>> >>> On Sep 27, 2017, at 1:15 PM, Patrick Hunt > >>> > wrote:
>>  >>>
>>  >>> Has the log4j configuration changed at all? iirc the console
>>  >>> appender needs to be setup for those tests to function.
>>  >>>
>>  >>> Patrick
>>  >>>
>> >>> On Sat, Sep 23, 2017 at 8:01 AM, Jordan Zimmerman
>> >>> mailto:jor...@jordanzimmerman.com>>
>> >>> wrote:
>>  >>> There are 4 tests throwing NPEs in Jenkins due to:
>>  >>>
>>  >>> Layout layout = Logger.getRootLogger().getAppender("CONSOLE")
>>  >>> .getLayout();
>>  >>>
>>  >>> Is this a known issue? Any workaround?
>>  >>>
>>  >>> -Jordan
>>  >>>
>>  On Sep 21, 2017, at 9:17 AM, Jordan Zimmerman
>>  mailto:jor...@jordanzimmerman.com>>
>>  wrote:
>>  
>>   In LeaderSessionTracker.java there is this bit of code:
>>  
>>   if (!localSessionsEnabled
>>   || (getServerIdFromSessionId(sessionId) ==
>>   || serverId)) {
>>   throw new SessionExpiredException(); }
>>  
>>  "serverId" is a long. This can only work if Server IDs are 255
>>  or less. I realize this is in the docs. But is it enforced? See:
>>  https://issues.apache.org/jira/browse/ZOOKEEPER-2503
>>  >>  
>>  
>>  
>>  > On Sep 20, 2017, at 3:10 PM, Raúl Gutiérrez Segalés
>>  > mailto:r...@itevenworks.net>> wrote:>> >
>>  > On 20 September 2017 at 12:54, Camille Fournier
>>  > mailto:cami...@apache.org>> wrote: Ok
>>  > let's take this back to either public mailing list or jira.
>>  > I'd write up thoughts on jira and ask there+ml to look. I'll
>>  > try to look tonight
>>  >
>>  > Thanks Camille!
>>  >
>>  > Also, I merged this originally so I will work with Jordan on
>>  > getting this fixed. Let me know when you have a write up of
>>  > your proposed solution and I'll take a look. Thanks!
>>  >
>>  >
>>  > -rgs
>>  >
>>  >
>>  >
>> > On Sep 20, 2017 3:52 PM, "Jordan Zimmerman"
>> > > >  wrote:
>>  >
>>  > > I'd like to fix it as my company and probably many others
>>  > > are now using it in production. The question is how to fix
>>  > > it safely and correct

[jira] [Commented] (ZOOKEEPER-2906) The OWASP dependency check jar should not be included in the default classpath

2017-09-28 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16183816#comment-16183816
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2906:
---

GitHub user afine opened a pull request:

https://github.com/apache/zookeeper/pull/385

ZOOKEEPER-2906: The OWASP dependency check jar should not be included…

… in the default classpath

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/afine/zookeeper ZOOKEEPER-2906_3.4

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zookeeper/pull/385.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #385


commit 8124118a879318e8cb0c8420f2571493b5ffcc8a
Author: Abraham Fine 
Date:   2017-09-28T07:31:11Z

ZOOKEEPER-2906: The OWASP dependency check jar should not be included in 
the default classpath




> The OWASP dependency check jar should not be included in the default classpath
> --
>
> Key: ZOOKEEPER-2906
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2906
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.5.4, 3.6.0, 3.4.11
>Reporter: Abraham Fine
>Assignee: Abraham Fine
>
> The owasp dependency-check-ant jar that we use contains a SLF4J binding that 
> can break logging. We should move it into a separate classpath. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] zookeeper pull request #385: ZOOKEEPER-2906: The OWASP dependency check jar ...

2017-09-28 Thread afine

GitHub user afine opened a pull request:

https://github.com/apache/zookeeper/pull/385

ZOOKEEPER-2906: The OWASP dependency check jar should not be includedâ¦

â¦ in the default classpath

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/afine/zookeeper ZOOKEEPER-2906_3.4

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zookeeper/pull/385.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #385


commit 8124118a879318e8cb0c8420f2571493b5ffcc8a
Author: Abraham Fine 
Date:   2017-09-28T07:31:11Z

ZOOKEEPER-2906: The OWASP dependency check jar should not be included in 
the default classpath




---

[jira] [Commented] (ZOOKEEPER-2906) The OWASP dependency check jar should not be included in the default classpath

2017-09-28 Thread Hadoop QA (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16183815#comment-16183815
 ] 

Hadoop QA commented on ZOOKEEPER-2906:
--

+1 overall.  GitHub Pull Request  Build
  

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 1 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 does not introduce any new Findbugs (version 3.0.1) 
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-github-pr-build/1052//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1052//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1052//console

This message is automatically generated.

> The OWASP dependency check jar should not be included in the default classpath
> --
>
> Key: ZOOKEEPER-2906
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2906
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.5.4, 3.6.0, 3.4.11
>Reporter: Abraham Fine
>Assignee: Abraham Fine
>
> The owasp dependency-check-ant jar that we use contains a SLF4J binding that 
> can break logging. We should move it into a separate classpath. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] zookeeper pull request #384: ZOOKEEPER-2906: The OWASP dependency check jar ...

2017-09-28 Thread phunt

Github user phunt commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/384#discussion_r141546698
  
--- Diff: build.xml ---
@@ -121,6 +121,7 @@ xmlns:cs="antlib:com.puppycrawl.tools.checkstyle.ant">
 
 
 
+
--- End diff --

iirc the reports are output to build/test/owasp/ perhaps you should 
move them here as well rather than spreading around?


---

[jira] [Commented] (ZOOKEEPER-2906) The OWASP dependency check jar should not be included in the default classpath

2017-09-28 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16183806#comment-16183806
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2906:
---

Github user phunt commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/384#discussion_r141546115
  
--- Diff: build.xml ---
@@ -1558,8 +1565,8 @@ xmlns:cs="antlib:com.puppycrawl.tools.checkstyle.ant">
classpathref="releaseaudit-classpath"/>
 
 
-
--- End diff --

Notice that the release audit jars are being dumped into build/lib - I'd 
recommend we fix that as part of this patch as well.


> The OWASP dependency check jar should not be included in the default classpath
> --
>
> Key: ZOOKEEPER-2906
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2906
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.5.4, 3.6.0, 3.4.11
>Reporter: Abraham Fine
>Assignee: Abraham Fine
>
> The owasp dependency-check-ant jar that we use contains a SLF4J binding that 
> can break logging. We should move it into a separate classpath. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ZOOKEEPER-2906) The OWASP dependency check jar should not be included in the default classpath

2017-09-28 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16183805#comment-16183805
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2906:
---

Github user phunt commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/384#discussion_r141546698
  
--- Diff: build.xml ---
@@ -121,6 +121,7 @@ xmlns:cs="antlib:com.puppycrawl.tools.checkstyle.ant">
 
 
 
+
--- End diff --

iirc the reports are output to build/test/owasp/ perhaps you should 
move them here as well rather than spreading around?


> The OWASP dependency check jar should not be included in the default classpath
> --
>
> Key: ZOOKEEPER-2906
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2906
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.5.4, 3.6.0, 3.4.11
>Reporter: Abraham Fine
>Assignee: Abraham Fine
>
> The owasp dependency-check-ant jar that we use contains a SLF4J binding that 
> can break logging. We should move it into a separate classpath. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] zookeeper pull request #384: ZOOKEEPER-2906: The OWASP dependency check jar ...

2017-09-28 Thread phunt

Github user phunt commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/384#discussion_r141546115
  
--- Diff: build.xml ---
@@ -1558,8 +1565,8 @@ xmlns:cs="antlib:com.puppycrawl.tools.checkstyle.ant">
classpathref="releaseaudit-classpath"/>
 
 
-
--- End diff --

Notice that the release audit jars are being dumped into build/lib - I'd 
recommend we fix that as part of this patch as well.


---

[jira] [Commented] (ZOOKEEPER-2906) The OWASP dependency check jar should not be included in the default classpath

2017-09-28 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16183794#comment-16183794
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2906:
---

GitHub user afine opened a pull request:

https://github.com/apache/zookeeper/pull/384

ZOOKEEPER-2906: The OWASP dependency check jar should not be included…

… in the default classpath

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/afine/zookeeper ZOOKEEPER-2906

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zookeeper/pull/384.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #384


commit 241fbeb2b33bafb1ca79a3cd322ea04c24c2f755
Author: Abraham Fine 
Date:   2017-09-28T07:31:11Z

ZOOKEEPER-2906: The OWASP dependency check jar should not be included in 
the default classpath




> The OWASP dependency check jar should not be included in the default classpath
> --
>
> Key: ZOOKEEPER-2906
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2906
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.5.4, 3.6.0, 3.4.11
>Reporter: Abraham Fine
>Assignee: Abraham Fine
>
> The owasp dependency-check-ant jar that we use contains a SLF4J binding that 
> can break logging. We should move it into a separate classpath. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] zookeeper pull request #384: ZOOKEEPER-2906: The OWASP dependency check jar ...

2017-09-28 Thread afine

GitHub user afine opened a pull request:

https://github.com/apache/zookeeper/pull/384

ZOOKEEPER-2906: The OWASP dependency check jar should not be includedâ¦

â¦ in the default classpath

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/afine/zookeeper ZOOKEEPER-2906

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zookeeper/pull/384.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #384


commit 241fbeb2b33bafb1ca79a3cd322ea04c24c2f755
Author: Abraham Fine 
Date:   2017-09-28T07:31:11Z

ZOOKEEPER-2906: The OWASP dependency check jar should not be included in 
the default classpath




---

[jira] [Created] (ZOOKEEPER-2906) The OWASP dependency check jar should not be included in the default classpath

2017-09-28 Thread Abraham Fine (JIRA)

Abraham Fine created ZOOKEEPER-2906:
---

 Summary: The OWASP dependency check jar should not be included in 
the default classpath
 Key: ZOOKEEPER-2906
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2906
 Project: ZooKeeper
  Issue Type: Bug
Affects Versions: 3.5.4, 3.6.0, 3.4.11
Reporter: Abraham Fine
Assignee: Abraham Fine


The owasp dependency-check-ant jar that we use contains a SLF4J binding that 
can break logging. We should move it into a separate classpath. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

67 matches

Mail list logo