ZooKeeper-trunk-solaris - Build # 1491 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper-trunk-solaris/1491/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 466795 lines...]
[junit] 2017-02-05 08:27:04,629 [myid:] - INFO  [main:ClientBase@401] - 
CREATING server instance 127.0.0.1:11222
[junit] 2017-02-05 08:27:04,629 [myid:] - INFO  
[main:NIOServerCnxnFactory@673] - Configuring NIO connection handler with 10s 
sessionless connection timeout, 2 selector thread(s), 16 worker threads, and 64 
kB direct buffers.
[junit] 2017-02-05 08:27:04,629 [myid:] - INFO  
[main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222
[junit] 2017-02-05 08:27:04,630 [myid:] - INFO  [main:ClientBase@376] - 
STARTING server instance 127.0.0.1:11222
[junit] 2017-02-05 08:27:04,630 [myid:] - INFO  [main:ZooKeeperServer@894] 
- minSessionTimeout set to 6000
[junit] 2017-02-05 08:27:04,631 [myid:] - INFO  [main:ZooKeeperServer@903] 
- maxSessionTimeout set to 6
[junit] 2017-02-05 08:27:04,631 [myid:] - INFO  [main:ZooKeeperServer@160] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test5661521666102281196.junit.dir/version-2
 snapdir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test5661521666102281196.junit.dir/version-2
[junit] 2017-02-05 08:27:04,631 [myid:] - INFO  [main:FileSnap@83] - 
Reading snapshot 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test5661521666102281196.junit.dir/version-2/snapshot.b
[junit] 2017-02-05 08:27:04,633 [myid:] - INFO  [main:FileTxnSnapLog@346] - 
Snapshotting: 0xb to 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test5661521666102281196.junit.dir/version-2/snapshot.b
[junit] 2017-02-05 08:27:04,635 [myid:] - ERROR [main:ZooKeeperServer@506] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-02-05 08:27:04,635 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2017-02-05 08:27:04,635 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:52338
[junit] 2017-02-05 08:27:04,636 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from 
/127.0.0.1:52338
[junit] 2017-02-05 08:27:04,636 [myid:] - INFO  
[NIOWorkerThread-1:StatCommand@49] - Stat command output
[junit] 2017-02-05 08:27:04,636 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@614] - Closed socket connection for client 
/127.0.0.1:52338 (no session established for client)
[junit] 2017-02-05 08:27:04,637 [myid:] - INFO  [main:JMXEnv@228] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2017-02-05 08:27:04,638 [myid:] - INFO  [main:JMXEnv@245] - 
expect:InMemoryDataTree
[junit] 2017-02-05 08:27:04,638 [myid:] - INFO  [main:JMXEnv@249] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree
[junit] 2017-02-05 08:27:04,638 [myid:] - INFO  [main:JMXEnv@245] - 
expect:StandaloneServer_port
[junit] 2017-02-05 08:27:04,638 [myid:] - INFO  [main:JMXEnv@249] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222
[junit] 2017-02-05 08:27:04,639 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17909
[junit] 2017-02-05 08:27:04,639 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24
[junit] 2017-02-05 08:27:04,639 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testQuota
[junit] 2017-02-05 08:27:04,639 [myid:] - INFO  [main:ClientBase@558] - 
tearDown starting
[junit] 2017-02-05 08:27:04,712 [myid:] - INFO  [main:ZooKeeper@1324] - 
Session: 0x1268a5b4b92 closed
[junit] 2017-02-05 08:27:04,712 [myid:] - INFO  [main:ClientBase@528] - 
STOPPING server
[junit] 2017-02-05 08:27:04,712 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x1268a5b4b92
[junit] 2017-02-05 08:27:04,712 [myid:] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread interrupted
[junit] 2017-02-05 08:27:04,712 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2017-02-05 08:27:04,712 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] 
- 

Failed: ZOOKEEPER- PreCommit Build #276

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 24 lines...]
  Getting sizes
Done: 18
  Compressing objects
Done: 0
  Writing objects
Done: 19
  remote: Updating references
Merging refs/tags/changes/276
 > git rev-parse refs/tags/changes/276^{commit} # timeout=10
 > git merge 8b9721b69497adf1de9a6a741a44cf11c5d5f986 # timeout=10
 > git rev-parse branch-3.5^{commit} # timeout=10
Checking out Revision 8b9721b69497adf1de9a6a741a44cf11c5d5f986 (branch-3.5)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 8b9721b69497adf1de9a6a741a44cf11c5d5f986
 > git rev-parse origin/branch-3.5^{commit} # timeout=10
 > git rev-list c84a61134f3d1d27ec8269eddc4e110e5e41c536 # timeout=10
No emails were triggered.
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[PreCommit-ZOOKEEPER-github-pr-build] $ /bin/bash 
/tmp/hudson6091494904452256356.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) 386178
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
Buildfile: 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml

BUILD FAILED
Target "qa-test-pullrequest" does not exist in the project "ZooKeeper". 

Total time: 0 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?
[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) 
##
No tests ran.

Failed: ZOOKEEPER- PreCommit Build #277

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 24 lines...]
  Getting sizes
Done: 18
  Compressing objects
Done: 0
  Writing objects
Done: 19
  remote: Updating references
Merging refs/tags/changes/277
 > git rev-parse refs/tags/changes/277^{commit} # timeout=10
 > git merge 30c1d1bc89ed142975205ca7d75cd71a077b7f72 # timeout=10
 > git rev-parse branch-3.4^{commit} # timeout=10
Checking out Revision 30c1d1bc89ed142975205ca7d75cd71a077b7f72 (branch-3.4)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 30c1d1bc89ed142975205ca7d75cd71a077b7f72
 > git rev-parse origin/branch-3.4^{commit} # timeout=10
 > git rev-list 4b9fe5ea71d73ba26ca722e3919b8d0afe84ab86 # timeout=10
No emails were triggered.
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[PreCommit-ZOOKEEPER-github-pr-build] $ /bin/bash 
/tmp/hudson1220380519304375521.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) 386178
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
Buildfile: 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml

BUILD FAILED
Target "qa-test-pullrequest" does not exist in the project "ZooKeeper". 

Total time: 0 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?
[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) 
##
No tests ran.

[jira] [Commented] (ZOOKEEPER-2680) Correct DataNode.getChildren() inconsistent behaviour.

[ASF GitHub Bot (JIRA)]

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

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

Github user arshadmohammad commented on the issue:

https://github.com/apache/zookeeper/pull/162
  
CI failure is because of qa-test-pullrequest is not present in branch-3.4


> Correct DataNode.getChildren() inconsistent behaviour.
> --
>
> Key: ZOOKEEPER-2680
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2680
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.9, 3.5.1
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2680-01.patch
>
>
> DataNode.getChildren() API returns null and empty set if there are no 
> children in it depending on when the API is called. DataNode.getChildren() 
> API behavior should be changed and it should always return empty set if the 
> node does not have any child
> *DataNode.getChildren() API Current Behavior:*
> # returns null initially
> When DataNode is created and no children are added yet, 
> DataNode.getChildren() returns null
> # returns empty set after all the children are deleted:
> created a Node
> add a child
> delete the child
> DataNode.getChildren() returns empty set.
> After fix DataNode.getChildren() should return empty set in all the above 
> cases.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #161: ZOOKEEPER-2680: Correct DataNode.getChildren() inconsi...

[arshadmohammad]

Github user arshadmohammad commented on the issue:

https://github.com/apache/zookeeper/pull/161
  
CI failure is because of qa-test-pullrequest is not present in branch-3.5


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zookeeper issue #162: ZOOKEEPER-2680: Correct DataNode.getChildren() inconsi...

[arshadmohammad]

Github user arshadmohammad commented on the issue:

https://github.com/apache/zookeeper/pull/162
  
CI failure is because of qa-test-pullrequest is not present in branch-3.4


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ZOOKEEPER-2680) Correct DataNode.getChildren() inconsistent behaviour.

[ASF GitHub Bot (JIRA)]

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

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

Github user arshadmohammad commented on the issue:

https://github.com/apache/zookeeper/pull/161
  
CI failure is because of qa-test-pullrequest is not present in branch-3.5


> Correct DataNode.getChildren() inconsistent behaviour.
> --
>
> Key: ZOOKEEPER-2680
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2680
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.9, 3.5.1
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2680-01.patch
>
>
> DataNode.getChildren() API returns null and empty set if there are no 
> children in it depending on when the API is called. DataNode.getChildren() 
> API behavior should be changed and it should always return empty set if the 
> node does not have any child
> *DataNode.getChildren() API Current Behavior:*
> # returns null initially
> When DataNode is created and no children are added yet, 
> DataNode.getChildren() returns null
> # returns empty set after all the children are deleted:
> created a Node
> add a child
> delete the child
> DataNode.getChildren() returns empty set.
> After fix DataNode.getChildren() should return empty set in all the above 
> cases.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ZOOKEEPER-2680) Correct DataNode.getChildren() inconsistent behaviour.

[ASF GitHub Bot (JIRA)]

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

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

GitHub user arshadmohammad opened a pull request:

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

ZOOKEEPER-2680: Correct DataNode.getChildren() inconsistent behaviour. 
:branch-3.4



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

$ git pull https://github.com/arshadmohammad/zookeeper ZOOKEEPER-2680-br-3.4

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

https://github.com/apache/zookeeper/pull/162.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 #162


commit 30c1d1bc89ed142975205ca7d75cd71a077b7f72
Author: Mohammad Arshad 
Date:   2017-02-05T08:10:03Z

ZOOKEEPER-2680: Correct DataNode.getChildren() inconsistent behaviour.




> Correct DataNode.getChildren() inconsistent behaviour.
> --
>
> Key: ZOOKEEPER-2680
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2680
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.9, 3.5.1
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2680-01.patch
>
>
> DataNode.getChildren() API returns null and empty set if there are no 
> children in it depending on when the API is called. DataNode.getChildren() 
> API behavior should be changed and it should always return empty set if the 
> node does not have any child
> *DataNode.getChildren() API Current Behavior:*
> # returns null initially
> When DataNode is created and no children are added yet, 
> DataNode.getChildren() returns null
> # returns empty set after all the children are deleted:
> created a Node
> add a child
> delete the child
> DataNode.getChildren() returns empty set.
> After fix DataNode.getChildren() should return empty set in all the above 
> cases.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper pull request #162: ZOOKEEPER-2680: Correct DataNode.getChildren() ...

[arshadmohammad]

GitHub user arshadmohammad opened a pull request:

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

ZOOKEEPER-2680: Correct DataNode.getChildren() inconsistent behaviour. 
:branch-3.4



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

$ git pull https://github.com/arshadmohammad/zookeeper ZOOKEEPER-2680-br-3.4

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

https://github.com/apache/zookeeper/pull/162.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 #162


commit 30c1d1bc89ed142975205ca7d75cd71a077b7f72
Author: Mohammad Arshad 
Date:   2017-02-05T08:10:03Z

ZOOKEEPER-2680: Correct DataNode.getChildren() inconsistent behaviour.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (ZOOKEEPER-2682) Make it optional to fail build on test failure.

[Mohammad Arshad (JIRA)]

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

Mohammad Arshad updated ZOOKEEPER-2682:
---
Attachment: ZOOKEEPER-2682-01.patch

added new paratermeter test.junit.failbuild.ontestfailure
Give -Dtest.junit.failbuild.ontestfailure=false along with other junit test 
parameters to pass the build even if some tests are failed.
By defautl test.junit.failbuild.ontestfailure is true so default is behavior is 
unchanged.

> Make it optional to fail build on test failure.
> ---
>
> Key: ZOOKEEPER-2682
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2682
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: build, tests
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Minor
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2682-01.patch
>
>
> Currently if there is a test failure, build is marked as failed and exits.
> I want to rerun the failed test cases instead of exiting.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ZOOKEEPER-2682) Make it optional to fail build on test failure.

[Mohammad Arshad (JIRA)]

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

Mohammad Arshad updated ZOOKEEPER-2682:
---
Attachment: ZOOKEEPER-2682-02.patch

Generated patch with --no-prefix option. It was missed in earlier patch

> Make it optional to fail build on test failure.
> ---
>
> Key: ZOOKEEPER-2682
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2682
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: build, tests
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Minor
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2682-01.patch, ZOOKEEPER-2682-02.patch
>
>
> Currently if there is a test failure, build is marked as failed and exits.
> I want to rerun the failed test cases instead of exiting.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

ZooKeeper_branch35_openjdk7 - Build # 400 - Still Failing

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 439544 lines...]
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-02-05 10:11:26,791 [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-02-05 10:11:26,791 [myid:127.0.0.1:14038] - WARN  
[main-SendThread(127.0.0.1:14038):ClientCnxn$SendThread@1235] - Session 
0x101cde93460 for server 127.0.0.1/127.0.0.1:14038, 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:739)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-02-05 10:11:26,825 [myid:] - INFO  
[SessionTracker:SessionTrackerImpl@158] - SessionTrackerImpl exited loop!
[junit] 2017-02-05 10:11:26,885 [myid:] - INFO  [ProcessThread(sid:0 
cport:14161)::PrepRequestProcessor@656] - Processed session termination for 
sessionid: 0x101cdec7ccf
[junit] 2017-02-05 10:11:26,888 [myid:] - INFO  [main:ZooKeeper@1322] - 
Session: 0x101cdec7ccf closed
[junit] 2017-02-05 10:11:26,888 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x101cdec7ccf
[junit] 2017-02-05 10:11:26,888 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 54897
[junit] 2017-02-05 10:11:26,889 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 467
[junit] 2017-02-05 10:11:26,889 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2017-02-05 10:11:26,889 [myid:] - INFO  [main:ClientBase@543] - 
tearDown starting
[junit] 2017-02-05 10:11:26,889 [myid:] - INFO  [main:ClientBase@513] - 
STOPPING server
[junit] 2017-02-05 10:11:26,889 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:14161
[junit] 2017-02-05 10:11:26,889 [myid:] - INFO  [New I/O worker 
#1829:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port14161,name1=Connections,name2=127.0.0.1,name3=0x101cdec7ccf]
[junit] 2017-02-05 10:11:26,896 [myid:] - INFO  [main:ZooKeeperServer@533] 
- shutting down
[junit] 2017-02-05 10:11:26,896 [myid:] - ERROR [main:ZooKeeperServer@505] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-02-05 10:11:26,896 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2017-02-05 10:11:26,896 [myid:] - INFO  
[main:PrepRequestProcessor@974] - Shutting down
[junit] 2017-02-05 10:11:26,896 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2017-02-05 10:11:26,896 [myid:] - INFO  [ProcessThread(sid:0 
cport:14161)::PrepRequestProcessor@154] - PrepRequestProcessor exited loop!
[junit] 2017-02-05 10:11:26,897 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited!
[junit] 2017-02-05 10:11:26,897 [myid:] - INFO  
[main:FinalRequestProcessor@479] - shutdown of request processor complete
[junit] 2017-02-05 10:11:26,898 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port14161,name1=InMemoryDataTree]
[junit] 2017-02-05 10:11:26,898 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port14161]
[junit] 2017-02-05 10:11:26,898 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 14161
[junit] 2017-02-05 10:11:26,899 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2017-02-05 10:11:26,902 [myid:127.0.0.1:14044] - INFO  
[main-SendThread(127.0.0.1:14044):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:14044. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-02-05 10:11:26,902 [myid:127.0.0.1:14044] - WARN  
[main-SendThread(127.0.0.1:14044):ClientCnxn$SendThread@1235] - Session 
0x301cde93472 for server 127.0.0.1/127.0.0.1:14044, unexpected error, 
closing socket connection and attempting reconnect
  

[jira] [Updated] (ZOOKEEPER-2682) Make it optional to fail build on test failure.

[Mohammad Arshad (JIRA)]

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

Mohammad Arshad updated ZOOKEEPER-2682:
---
Description: 
Currently if there is a test failure, build is marked as failed and exits.
I want to rerun the failed test cases instead of exiting.

  was:
Currently if there is a test failure, build is marked as failed and exits.
I want to rerun the failed test cases instead of existing.


> Make it optional to fail build on test failure.
> ---
>
> Key: ZOOKEEPER-2682
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2682
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: build, tests
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Minor
>
> Currently if there is a test failure, build is marked as failed and exits.
> I want to rerun the failed test cases instead of exiting.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

ZooKeeper_branch35_jdk8 - Build # 403 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_jdk8/403/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 449128 lines...]
[junit] 2017-02-05 12:21:54,812 [myid:] - INFO  [New I/O worker 
#1829:ZooKeeperServer@713] - Established session 0x10354084e03 with 
negotiated timeout 6000 for client /127.0.0.1:35848
[junit] 2017-02-05 12:21:54,812 [myid:127.0.0.1:27626] - INFO  
[main-SendThread(127.0.0.1:27626):ClientCnxn$SendThread@1381] - Session 
establishment complete on server 127.0.0.1/127.0.0.1:27626, sessionid = 
0x10354084e03, negotiated timeout = 6000
[junit] 2017-02-05 12:21:54,817 [myid:] - INFO  
[SyncThread:0:FileTxnLog@204] - Creating new log file: log.7
[junit] 2017-02-05 12:21:54,820 [myid:127.0.0.1:27506] - INFO  
[main-SendThread(127.0.0.1:27506):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:27506. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-02-05 12:21:54,821 [myid:127.0.0.1:27506] - WARN  
[main-SendThread(127.0.0.1:27506):ClientCnxn$SendThread@1235] - Session 
0x2035404f32a for server 127.0.0.1/127.0.0.1:27506, 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:717)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-02-05 12:21:55,238 [myid:127.0.0.1:27503] - INFO  
[main-SendThread(127.0.0.1:27503):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:27503. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-02-05 12:21:55,239 [myid:127.0.0.1:27503] - WARN  
[main-SendThread(127.0.0.1:27503):ClientCnxn$SendThread@1235] - Session 
0x1035404f37a for server 127.0.0.1/127.0.0.1:27503, 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:717)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-02-05 12:21:55,744 [myid:127.0.0.1:27380] - INFO  
[main-SendThread(127.0.0.1:27380):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:27380. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-02-05 12:21:55,745 [myid:127.0.0.1:27380] - WARN  
[main-SendThread(127.0.0.1:27380):ClientCnxn$SendThread@1235] - Session 
0x103540046d7 for server 127.0.0.1/127.0.0.1:27380, 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:717)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-02-05 12:21:55,825 [myid:] - INFO  [ProcessThread(sid:0 
cport:27626)::PrepRequestProcessor@656] - Processed session termination for 
sessionid: 0x10354084e03
[junit] 2017-02-05 12:21:55,827 [myid:] - INFO  [main:ZooKeeper@1322] - 
Session: 0x10354084e03 closed
[junit] 2017-02-05 12:21:55,827 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x10354084e03
[junit] 2017-02-05 12:21:55,827 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 60443
[junit] 2017-02-05 12:21:55,827 [myid:] - INFO  [New I/O worker 
#1829:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port27626,name1=Connections,name2=127.0.0.1,name3=0x10354084e03]
[junit] 2017-02-05 12:21:55,827 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 468
[junit] 2017-02-05 12:21:55,828 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2017-02-05 12:21:55,828 [myid:] - INFO  [main:ClientBase@543] - 
tearDown starting
[junit] 2017-02-05 12:21:55,828 [myid:] - INFO  [main:ClientBase@513] - 
STOPPING server
[junit] 2017-02-05 12:21:55,828 [myid:] - INFO  

Failed: ZOOKEEPER-2682 PreCommit Build #3573

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 116 lines...]
 [exec] PATCH APPLICATION FAILED
 [exec] 
 [exec] 
 [exec] 
 [exec] 
 [exec] -1 overall.  Here are the results of testing the latest attachment 
 [exec]   
http://issues.apache.org/jira/secure/attachment/12851072/ZOOKEEPER-2682-01.patch
 [exec]   against trunk revision 26aee2228451257f3b0b5093bc0c101822e06bc8.
 [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 patch.  The patch command could not apply the patch.
 [exec] 
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3573//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] 710a3d14d3b5ea1e2d3d51464ca6f0ef00567f3d logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/patchprocess' 
and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/patchprocess' 
are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/build.xml:1609: 
exec returned: 1

Total time: 55 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-2682
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.

ZooKeeper_branch34_openjdk7 - Build # 1377 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/1377/

###
## LAST 60 LINES OF THE CONSOLE 
###
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H13 (ubuntu) in workspace 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_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
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > git://git.apache.org/zookeeper.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/branch-3.4^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/branch-3.4^{commit} # timeout=10
Checking out Revision 4b9fe5ea71d73ba26ca722e3919b8d0afe84ab86 
(refs/remotes/origin/branch-3.4)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 4b9fe5ea71d73ba26ca722e3919b8d0afe84ab86
 > git rev-list 4b9fe5ea71d73ba26ca722e3919b8d0afe84ab86 # timeout=10
No emails were triggered.
[ZooKeeper_branch34_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
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
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.

[jira] [Created] (ZOOKEEPER-2682) Make it optional to fail build on test failure.

[Mohammad Arshad (JIRA)]

Mohammad Arshad created ZOOKEEPER-2682:
--

 Summary: Make it optional to fail build on test failure.
 Key: ZOOKEEPER-2682
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2682
 Project: ZooKeeper
  Issue Type: Improvement
  Components: build, tests
Reporter: Mohammad Arshad
Assignee: Mohammad Arshad
Priority: Minor


Currently if there is a test failure, build is marked as failed and exits.
I want to rerun the failed test cases instead of existing.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ZOOKEEPER-2682) Make it optional to fail build on test failure.

[Hadoop QA (JIRA)]

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

Hadoop QA commented on ZOOKEEPER-2682:
--

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12851072/ZOOKEEPER-2682-01.patch
  against trunk revision 26aee2228451257f3b0b5093bc0c101822e06bc8.

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

+1 tests included.  The patch appears to include 1 new or modified tests.

-1 patch.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3573//console

This message is automatically generated.

> Make it optional to fail build on test failure.
> ---
>
> Key: ZOOKEEPER-2682
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2682
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: build, tests
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Minor
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2682-01.patch
>
>
> Currently if there is a test failure, build is marked as failed and exits.
> I want to rerun the failed test cases instead of exiting.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

ZooKeeper-trunk-jdk8 - Build # 927 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/927/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 446032 lines...]
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-02-05 12:07:59,868 [myid:127.0.0.1:19355] - INFO  
[main-SendThread(127.0.0.1:19355):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:19355. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-02-05 12:07:59,869 [myid:127.0.0.1:19355] - WARN  
[main-SendThread(127.0.0.1:19355):ClientCnxn$SendThread@1235] - Session 
0x30225ac0fcb for server 127.0.0.1/127.0.0.1:19355, 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:717)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-02-05 12:07:59,945 [myid:127.0.0.1:19349] - INFO  
[main-SendThread(127.0.0.1:19349):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:19349. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-02-05 12:07:59,945 [myid:127.0.0.1:19349] - WARN  
[main-SendThread(127.0.0.1:19349):ClientCnxn$SendThread@1235] - Session 
0x10225ac0f83 for server 127.0.0.1/127.0.0.1:19349, 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:717)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-02-05 12:08:00,137 [myid:127.0.0.1:19352] - INFO  
[main-SendThread(127.0.0.1:19352):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:19352. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-02-05 12:08:00,137 [myid:127.0.0.1:19352] - WARN  
[main-SendThread(127.0.0.1:19352):ClientCnxn$SendThread@1235] - Session 
0x20225ac0f83 for server 127.0.0.1/127.0.0.1:19352, 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:717)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-02-05 12:08:01,107 [myid:127.0.0.1:19349] - INFO  
[main-SendThread(127.0.0.1:19349):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:19349. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-02-05 12:08:01,107 [myid:127.0.0.1:19349] - WARN  
[main-SendThread(127.0.0.1:19349):ClientCnxn$SendThread@1235] - Session 
0x10225ac0f83 for server 127.0.0.1/127.0.0.1:19349, 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:717)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-02-05 12:08:01,539 [myid:127.0.0.1:19355] - INFO  
[main-SendThread(127.0.0.1:19355):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:19355. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-02-05 12:08:01,539 [myid:127.0.0.1:19355] - WARN  
[main-SendThread(127.0.0.1:19355):ClientCnxn$SendThread@1235] - Session 
0x30225ac0fcb for server 127.0.0.1/127.0.0.1:19355, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at 

[jira] [Commented] (ZOOKEEPER-2682) Make it optional to fail build on test failure.

[Hadoop QA (JIRA)]

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

Hadoop QA commented on ZOOKEEPER-2682:
--

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12851082/ZOOKEEPER-2682-02.patch
  against trunk revision 26aee2228451257f3b0b5093bc0c101822e06bc8.

+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-Build/3574//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3574//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3574//console

This message is automatically generated.

> Make it optional to fail build on test failure.
> ---
>
> Key: ZOOKEEPER-2682
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2682
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: build, tests
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Minor
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2682-01.patch, ZOOKEEPER-2682-02.patch
>
>
> Currently if there is a test failure, build is marked as failed and exits.
> I want to rerun the failed test cases instead of exiting.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ZOOKEEPER-2672) Remove CHANGE.txt

[Rakesh R (JIRA)]

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

Rakesh R commented on ZOOKEEPER-2672:
-

Thanks [~elyograg] for your comments. How about recommending users/devs to 
refer [ZK project release 
notes|http://zookeeper.apache.org/releases.html#releasenotes], which has the 
details of resolved jira issues in that released version. IIUC, all the 
committed jira details will be mentioning in the version release note and also 
in CHANGE.txt file, which is again a kind of duplicate information ?

> Remove CHANGE.txt
> -
>
> Key: ZOOKEEPER-2672
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2672
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
>
> The CHANGE.txt is already not the source of truth of what's changed after we 
> migrating to git - most of the git commits in recent couple of months don't 
> update CHANGE.txt. The option of updating CHANGE.txt during commit flow 
> automatically is none trivial, and do that manually is cumbersome and error 
> prone.
> The consensus is we would rely on source control revision logs instead of 
> CHANGE.txt moving forward; see 
> https://www.mail-archive.com/dev@zookeeper.apache.org/msg37108.html for more 
> details.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ZOOKEEPER-2659) Use log4j2 as a logging framework as log4j 1.X is now deprecated

[ASF GitHub Bot (JIRA)]

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

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

Github user praste commented on the issue:

https://github.com/apache/zookeeper/pull/148
  
can this be merged ?


> Use log4j2 as a logging framework as log4j 1.X is now deprecated
> 
>
> Key: ZOOKEEPER-2659
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2659
> Project: ZooKeeper
>  Issue Type: Wish
>Reporter: Pushkar Raste
>Assignee: Pushkar Raste
>Priority: Minor
> Attachments: zk_log4j2_migration.patch
>
>
> Zookeeper currently uses {{log4j 1.X}} as the default logging framework. 
> {{log4j 1.X}} is now deprecated http://logging.apache.org/log4j/1.2/
> This ticket is to track efforts to move zookeeper to {{log4j2}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #148: ZOOKEEPER-2659 Log4j 2 migration

[praste]

Github user praste commented on the issue:

https://github.com/apache/zookeeper/pull/148
  
can this be merged ?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

ZooKeeper-trunk - Build # 3264 - Still Failing

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 479412 lines...]
[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-02-05 23:27:50,109 [myid:] - INFO  
[SyncThread:0:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port27626,name1=Connections,name2=127.0.0.1,name3=0x1005df776eb]
[junit] 2017-02-05 23:27:50,209 [myid:] - INFO  [main:ZooKeeper@1324] - 
Session: 0x1005df776eb closed
[junit] 2017-02-05 23:27:50,210 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x1005df776eb
[junit] 2017-02-05 23:27:50,210 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 174544
[junit] 2017-02-05 23:27:50,210 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 1643
[junit] 2017-02-05 23:27:50,210 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2017-02-05 23:27:50,210 [myid:] - INFO  [main:ClientBase@558] - 
tearDown starting
[junit] 2017-02-05 23:27:50,210 [myid:] - INFO  [main:ClientBase@528] - 
STOPPING server
[junit] 2017-02-05 23:27:50,210 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:27626
[junit] 2017-02-05 23:27:50,217 [myid:] - INFO  [main:ZooKeeperServer@534] 
- shutting down
[junit] 2017-02-05 23:27:50,217 [myid:] - ERROR [main:ZooKeeperServer@506] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-02-05 23:27:50,217 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2017-02-05 23:27:50,218 [myid:] - INFO  
[main:PrepRequestProcessor@1008] - Shutting down
[junit] 2017-02-05 23:27:50,218 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2017-02-05 23:27:50,218 [myid:] - INFO  [ProcessThread(sid:0 
cport:27626)::PrepRequestProcessor@157] - PrepRequestProcessor exited loop!
[junit] 2017-02-05 23:27:50,218 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited!
[junit] 2017-02-05 23:27:50,218 [myid:] - INFO  
[main:FinalRequestProcessor@481] - shutdown of request processor complete
[junit] 2017-02-05 23:27:50,219 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port27626,name1=InMemoryDataTree]
[junit] 2017-02-05 23:27:50,219 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port27626]
[junit] 2017-02-05 23:27:50,219 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 27626
[junit] 2017-02-05 23:27:50,220 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2017-02-05 23:27:50,226 [myid:] - INFO  [main:ClientBase@583] - 
fdcount after test is: 4825 at start it was 4825
[junit] 2017-02-05 23:27:50,226 [myid:] - INFO  [main:ZKTestCase$1@65] - 
SUCCEEDED testWatcherAutoResetWithLocal
[junit] 2017-02-05 23:27:50,226 [myid:] - INFO  [main:ZKTestCase$1@60] - 
FINISHED testWatcherAutoResetWithLocal
[junit] Tests run: 103, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
472.955 sec, Thread: 7, Class: org.apache.zookeeper.test.NioNettySuiteTest
[junit] 2017-02-05 23:27:50,283 [myid:127.0.0.1:27509] - INFO  
[main-SendThread(127.0.0.1:27509):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:27509. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-02-05 23:27:50,283 [myid:127.0.0.1:27509] - WARN  
[main-SendThread(127.0.0.1:27509):ClientCnxn$SendThread@1235] - Session 
0x3005df42ffe for server 127.0.0.1/127.0.0.1:27509, 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)

BUILD FAILED

[jira] [Commented] (ZOOKEEPER-2682) Make it optional to fail build on test failure.

[Rakesh R (JIRA)]

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

Rakesh R commented on ZOOKEEPER-2682:
-

Thanks [~arshad.mohammad] for the patch. Please create a PR for the same, I'll 
merge it.

> Make it optional to fail build on test failure.
> ---
>
> Key: ZOOKEEPER-2682
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2682
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: build, tests
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Minor
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2682-01.patch, ZOOKEEPER-2682-02.patch
>
>
> Currently if there is a test failure, build is marked as failed and exits.
> I want to rerun the failed test cases instead of exiting.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Failed: ZOOKEEPER-2682 PreCommit Build #3574

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 422610 lines...]
 [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-Build/3574//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3574//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3574//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] 7360a3689e3cea390ab03df5524e0ad5684248f6 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
‘/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/patchprocess’ 
and 
‘/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/patchprocess’ 
are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/build.xml:1609: 
exec returned: 1

Total time: 15 minutes 35 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Compressed 557.26 KB of artifacts by 45.9% relative to #3571
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-2682
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) 
##
2 tests failed.
FAILED:  org.apache.zookeeper.test.FourLetterWordsQuorumTest.testFourLetterWords

Error Message:
Exception while executing four letter word: cons

Stack Trace:
java.io.IOException: Exception while executing four letter word: cons
at 
org.apache.zookeeper.client.FourLetterWordMain.send4LetterWord(FourLetterWordMain.java:124)
at 
org.apache.zookeeper.client.FourLetterWordMain.send4LetterWord(FourLetterWordMain.java:54)
at 
org.apache.zookeeper.test.FourLetterWordsQuorumTest.verify(FourLetterWordsQuorumTest.java:109)
at 
org.apache.zookeeper.test.FourLetterWordsQuorumTest.testFourLetterWords(FourLetterWordsQuorumTest.java:87)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:152)
at java.net.SocketInputStream.read(SocketInputStream.java:122)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:283)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:325)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:177)
at java.io.InputStreamReader.read(InputStreamReader.java:184)
at 

ZooKeeper_branch34_jdk7 - Build # 1394 - Still Failing

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 240874 lines...]
[junit] 2017-02-06 03:23:44,736 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2017-02-06 03:23:44,737 [myid:] - INFO  [main:ZooKeeperServer@497] 
- shutting down
[junit] 2017-02-06 03:23:44,737 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-02-06 03:23:44,737 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2017-02-06 03:23:44,737 [myid:] - INFO  
[main:PrepRequestProcessor@765] - Shutting down
[junit] 2017-02-06 03:23:44,737 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2017-02-06 03:23:44,737 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2017-02-06 03:23:44,738 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2017-02-06 03:23:44,738 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2017-02-06 03:23:44,739 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-02-06 03:23:44,739 [myid:] - INFO  [main:JMXEnv@147] - 
ensureOnly:[]
[junit] 2017-02-06 03:23:44,741 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2017-02-06 03:23:44,741 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2017-02-06 03:23:44,741 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2017-02-06 03:23:44,741 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2017-02-06 03:23:44,742 [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/test8503236777307374818.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/build/test/tmp/test8503236777307374818.junit.dir/version-2
[junit] 2017-02-06 03:23:44,746 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-02-06 03:23:44,746 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-02-06 03:23:44,747 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:60126
[junit] 2017-02-06 03:23:44,747 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@838] - Processing 
stat command from /127.0.0.1:60126
[junit] 2017-02-06 03:23:44,748 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@674] - Stat command output
[junit] 2017-02-06 03:23:44,748 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1019] - Closed socket connection for client 
/127.0.0.1:60126 (no session established for client)
[junit] 2017-02-06 03:23:44,748 [myid:] - INFO  [main:JMXEnv@230] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2017-02-06 03:23:44,750 [myid:] - INFO  [main:JMXEnv@247] - 
expect:InMemoryDataTree
[junit] 2017-02-06 03:23:44,751 [myid:] - INFO  [main:JMXEnv@251] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2017-02-06 03:23:44,751 [myid:] - INFO  [main:JMXEnv@247] - 
expect:StandaloneServer_port
[junit] 2017-02-06 03:23:44,751 [myid:] - INFO  [main:JMXEnv@251] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2017-02-06 03:23:44,752 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 32680
[junit] 2017-02-06 03:23:44,752 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2017-02-06 03:23:44,752 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2017-02-06 03:23:44,752 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2017-02-06 03:23:44,814 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x15a1172dab2 closed
[junit] 2017-02-06 03:23:44,814 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2017-02-06 03:23:44,814 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x15a1172dab2
[junit] 2017-02-06 

[jira] [Commented] (ZOOKEEPER-2680) Correct DataNode.getChildren() inconsistent behaviour.

[Rakesh R (JIRA)]

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

Rakesh R commented on ZOOKEEPER-2680:
-

Thanks [~arshad.mohammad] for the code improvement. It would be good if you 
could run test cases locally against {{branch-3.4}}, {{branch-3.5}} and comment 
status here. I'm +1 for including this to 3.4.10 release as this task is almost 
completed.

> Correct DataNode.getChildren() inconsistent behaviour.
> --
>
> Key: ZOOKEEPER-2680
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2680
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.9, 3.5.1
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2680-01.patch
>
>
> DataNode.getChildren() API returns null and empty set if there are no 
> children in it depending on when the API is called. DataNode.getChildren() 
> API behavior should be changed and it should always return empty set if the 
> node does not have any child
> *DataNode.getChildren() API Current Behavior:*
> # returns null initially
> When DataNode is created and no children are added yet, 
> DataNode.getChildren() returns null
> # returns empty set after all the children are deleted:
> created a Node
> add a child
> delete the child
> DataNode.getChildren() returns empty set.
> After fix DataNode.getChildren() should return empty set in all the above 
> cases.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ZOOKEEPER-2184) Zookeeper Client should re-resolve hosts when connection attempts fail

[ASF GitHub Bot (JIRA)]

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

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

Github user rakeshadr commented on the issue:

https://github.com/apache/zookeeper/pull/150
  
Thanks everyone for the great effort & time in pushing this issue. I could 
see long discussions in the PR and I hope this work is nearing completion. 
Could you please update the progress and would like to know the chances of 
pushing this asap, thanks!.


> Zookeeper Client should re-resolve hosts when connection attempts fail
> --
>
> Key: ZOOKEEPER-2184
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2184
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.4.6, 3.5.0
> Environment: Ubuntu 14.04 host, Docker containers for Zookeeper & 
> Kafka
>Reporter: Robert P. Thille
>Assignee: Flavio Junqueira
>  Labels: easyfix, patch
> Fix For: 3.4.10, 3.5.3
>
> Attachments: ZOOKEEPER-2184.patch
>
>
> Testing in a Docker environment with a single Kafka instance using a single 
> Zookeeper instance. Restarting the Zookeeper container will cause it to 
> receive a new IP address. Kafka will never be able to reconnect to Zookeeper 
> and will hang indefinitely. Updating DNS or /etc/hosts with the new IP 
> address will not help the client to reconnect as the 
> zookeeper/client/StaticHostProvider resolves the connection string hosts at 
> creation time and never re-resolves.
> A solution would be for the client to notice that connection attempts fail 
> and attempt to re-resolve the hostnames in the connectString.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ZOOKEEPER-2682) Make it optional to fail build on test failure.

[Mohammad Arshad (JIRA)]

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

Mohammad Arshad commented on ZOOKEEPER-2682:


test failure are not related to this patch.

> Make it optional to fail build on test failure.
> ---
>
> Key: ZOOKEEPER-2682
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2682
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: build, tests
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Minor
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2682-01.patch, ZOOKEEPER-2682-02.patch
>
>
> Currently if there is a test failure, build is marked as failed and exits.
> I want to rerun the failed test cases instead of exiting.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ZOOKEEPER-2680) Correct DataNode.getChildren() inconsistent behaviour.

[Mohammad Arshad (JIRA)]

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

Mohammad Arshad commented on ZOOKEEPER-2680:


I wanted to run test cases in my local CI. I need one patch to be committed to 
complete my CI setup. Can you please have a look on ZOOKEEPER-2682 and commit 
it.

> Correct DataNode.getChildren() inconsistent behaviour.
> --
>
> Key: ZOOKEEPER-2680
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2680
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.9, 3.5.1
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2680-01.patch
>
>
> DataNode.getChildren() API returns null and empty set if there are no 
> children in it depending on when the API is called. DataNode.getChildren() 
> API behavior should be changed and it should always return empty set if the 
> node does not have any child
> *DataNode.getChildren() API Current Behavior:*
> # returns null initially
> When DataNode is created and no children are added yet, 
> DataNode.getChildren() returns null
> # returns empty set after all the children are deleted:
> created a Node
> add a child
> delete the child
> DataNode.getChildren() returns empty set.
> After fix DataNode.getChildren() should return empty set in all the above 
> cases.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #87: ZOOKEEPER-2617: correct a few spelling typos

[rakeshadr]

Github user rakeshadr commented on the issue:

https://github.com/apache/zookeeper/pull/87
  
@eribeiro sure, I will consider this to 3.4.10. Thanks @tmancill for the 
contribution. Sorry for the delay in looking at this jira, could you please 
create separate PR for {{master}} branch as the current PR_87 is not applying 
to {{branch-3.5}} and {{master}}.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ZOOKEEPER-2617) minor typos in the source

[ASF GitHub Bot (JIRA)]

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

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

Github user rakeshadr commented on the issue:

https://github.com/apache/zookeeper/pull/87
  
@eribeiro sure, I will consider this to 3.4.10. Thanks @tmancill for the 
contribution. Sorry for the delay in looking at this jira, could you please 
create separate PR for {{master}} branch as the current PR_87 is not applying 
to {{branch-3.5}} and {{master}}.


> minor typos in the source
> -
>
> Key: ZOOKEEPER-2617
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2617
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.4.9
>Reporter: tony mancill
>Priority: Trivial
>  Labels: newbie, patch
> Fix For: 3.4.10, 3.5.3
>
> Attachments: JIRA-ZOOKEEPER-2617.patch
>
>
> While working on the Debian packaging of ZooKeeper, some misspellings were 
> detected in the source that affect the documentation, logging, and program 
> output.
> There is a PR against github containing the patch here:  
> https://github.com/apache/zookeeper/pull/87



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #150: ZOOKEEPER-2184: Zookeeper Client should re-resolve hos...

[rakeshadr]

Github user rakeshadr commented on the issue:

https://github.com/apache/zookeeper/pull/150
  
Thanks everyone for the great effort & time in pushing this issue. I could 
see long discussions in the PR and I hope this work is nearing completion. 
Could you please update the progress and would like to know the chances of 
pushing this asap, thanks!.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ZOOKEEPER-2682) Make it optional to fail build on test failure.

[Mohammad Arshad (JIRA)]

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

Mohammad Arshad commented on ZOOKEEPER-2682:


I verified the patch on my local CI. I run the test cases of master branch. It 
works fine. 
This patch applies on master and branch-3.5, I will submit separate patch for 
branch-3.4


> Make it optional to fail build on test failure.
> ---
>
> Key: ZOOKEEPER-2682
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2682
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: build, tests
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Minor
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2682-01.patch, ZOOKEEPER-2682-02.patch
>
>
> Currently if there is a test failure, build is marked as failed and exits.
> I want to rerun the failed test cases instead of exiting.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)