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

See https://builds.apache.org/job/ZooKeeper-trunk-solaris/1465/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 462715 lines...] [junit] 2017-01-14

ZooKeeper-trunk - Build # 3237 - Still Failing

See https://builds.apache.org/job/ZooKeeper-trunk/3237/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 494979 lines...] [exec] Log Message Received:

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

See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/900/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 485580 lines...] [junit] 2017-01-14 06:13:28,277

[jira] [Commented] (ZOOKEEPER-261) Reinitialized servers should not participate in leader election

[ https://issues.apache.org/jira/browse/ZOOKEEPER-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822700#comment-15822700 ] ASF GitHub Bot commented on ZOOKEEPER-261: -- Github user hanm commented on the issue:

[GitHub] zookeeper issue #120: ZOOKEEPER-261

Github user hanm commented on the issue: https://github.com/apache/zookeeper/pull/120 As a side effect of a new commit (https://github.com/apache/zookeeper/commit/42c75b5f2457f8ea5b4106ce5dc1c34c330361c0) that triggers git mirror sync, this PR is closed :) --- If your project is

[GitHub] zookeeper issue #149: ZOOKEEPER-2664: ClientPortBindTest#testBindByAddress m...

Github user hanm commented on the issue: https://github.com/apache/zookeeper/pull/149 LGTM, merged. Thanks a lot @tedyu for your contribution to fix this test, that is much appreciated! Thanks @eribeiro for reviewing the patch as well. --- If your project is set up for it, you

[jira] [Commented] (ZOOKEEPER-2664) ClientPortBindTest#testBindByAddress may fail due to "No such device" exception

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822699#comment-15822699 ] ASF GitHub Bot commented on ZOOKEEPER-2664: --- Github user hanm commented on the issue:

Re: zookeeper git not getting bridged to github

I just made another commit to master, and that commit somehow triggers the mirror and apache git sync. Ben's commit is now appearing on github mirror: https://github.com/apache/zookeeper/commit/8773ecb78a4bbd5ed066493a09adf7f1a73fa74e On Fri, Jan 13, 2017 at 7:29 PM, Benjamin Reed

[jira] [Commented] (ZOOKEEPER-2664) ClientPortBindTest#testBindByAddress may fail due to "No such device" exception

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822696#comment-15822696 ] ASF GitHub Bot commented on ZOOKEEPER-2664: --- Github user asfgit closed the pull request at:

[jira] [Commented] (ZOOKEEPER-261) Reinitialized servers should not participate in leader election

[ https://issues.apache.org/jira/browse/ZOOKEEPER-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822695#comment-15822695 ] ASF GitHub Bot commented on ZOOKEEPER-261: -- Github user asfgit closed the pull request at:

[GitHub] zookeeper pull request #120: ZOOKEEPER-261

Github user asfgit closed the pull request at: https://github.com/apache/zookeeper/pull/120 --- 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

[GitHub] zookeeper pull request #149: ZOOKEEPER-2664: ClientPortBindTest#testBindByAd...

Github user asfgit closed the pull request at: https://github.com/apache/zookeeper/pull/149 --- 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

ZooKeeper-trunk-WinVS2008 - Build # 2430 - Still Failing

See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/2430/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 121 lines...] [javacc] File

ZooKeeper-trunk-WinVS2008 - Build # 2429 - Still Failing

See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/2429/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 125 lines...] [javacc] File

Failed: ZOOKEEPER- PreCommit Build #212

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/212/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 453970 lines...] [exec]

Re: zookeeper git not getting bridged to github

ok created https://issues.apache.org/jira/browse/INFRA-13331 On Fri, Jan 13, 2017 at 5:44 PM, Michael Han wrote: > Other Apache mirrors work fine (checked HBase, Kafka, some others), so it > is unlikely a foundational infrastructure issue - might be ZK specific. > > On Fri,

Re: zookeeper git not getting bridged to github

Other Apache mirrors work fine (checked HBase, Kafka, some others), so it is unlikely a foundational infrastructure issue - might be ZK specific. On Fri, Jan 13, 2017 at 3:47 PM, Benjamin Reed wrote: > i committed ZOOKEEPER-261 pull request to apache git using the perl >

zookeeper git not getting bridged to github

i committed ZOOKEEPER-261 pull request to apache git using the perl script. my .netrc wasn't setup properly and then i had a problem trying to rerun with the failed branches in place. then i started getting very weird errors at the last step of the script and realized that the patch had already

ZooKeeper-trunk - Build # 3236 - Still Failing

See https://builds.apache.org/job/ZooKeeper-trunk/3236/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 481837 lines...] [junit] at

[jira] [Commented] (ZOOKEEPER-261) Reinitialized servers should not participate in leader election

[ https://issues.apache.org/jira/browse/ZOOKEEPER-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822481#comment-15822481 ] ASF GitHub Bot commented on ZOOKEEPER-261: -- Github user hanm commented on the issue:

[GitHub] zookeeper issue #120: ZOOKEEPER-261

Github user hanm commented on the issue: https://github.com/apache/zookeeper/pull/120 Right, it is committed, confirmed. I was only checking the apache mirror on git (https://github.com/apache/zookeeper), instead of the apache git directly. I suspect there is some infra

[jira] [Commented] (ZOOKEEPER-261) Reinitialized servers should not participate in leader election

[ https://issues.apache.org/jira/browse/ZOOKEEPER-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822476#comment-15822476 ] ASF GitHub Bot commented on ZOOKEEPER-261: -- Github user breed commented on the issue:

[GitHub] zookeeper issue #120: ZOOKEEPER-261

Github user breed commented on the issue: https://github.com/apache/zookeeper/pull/120 it shows up in https://git-wip-us.apache.org/repos/asf?p=zookeeper.git --- 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

[jira] [Commented] (ZOOKEEPER-261) Reinitialized servers should not participate in leader election

[ https://issues.apache.org/jira/browse/ZOOKEEPER-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822467#comment-15822467 ] ASF GitHub Bot commented on ZOOKEEPER-261: -- Github user breed commented on the issue:

[GitHub] zookeeper issue #120: ZOOKEEPER-261

Github user breed commented on the issue: https://github.com/apache/zookeeper/pull/120 hmm, perhaps you are right. i don't think the script is working for me properly... checking. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub

[jira] [Commented] (ZOOKEEPER-261) Reinitialized servers should not participate in leader election

[ https://issues.apache.org/jira/browse/ZOOKEEPER-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822464#comment-15822464 ] ASF GitHub Bot commented on ZOOKEEPER-261: -- Github user hanm commented on the issue:

[GitHub] zookeeper issue #120: ZOOKEEPER-261

Github user hanm commented on the issue: https://github.com/apache/zookeeper/pull/120 Also https://issues.apache.org/jira/browse/ZOOKEEPER-261 does not have Fixed Version set, which implies that the JIRA was resolved manually (my guess) instead of automatically as part of commit flow

[jira] [Commented] (ZOOKEEPER-261) Reinitialized servers should not participate in leader election

[ https://issues.apache.org/jira/browse/ZOOKEEPER-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822461#comment-15822461 ] ASF GitHub Bot commented on ZOOKEEPER-261: -- Github user hanm commented on the issue:

[GitHub] zookeeper issue #120: ZOOKEEPER-261

Github user hanm commented on the issue: https://github.com/apache/zookeeper/pull/120 I don't see this is committed in master. No commit log from git, no notification emails. @breed Are you sure this is committed (and pushed to apache git)? --- If your project is set up for it, you

[jira] [Commented] (ZOOKEEPER-261) Reinitialized servers should not participate in leader election

[ https://issues.apache.org/jira/browse/ZOOKEEPER-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822389#comment-15822389 ] ASF GitHub Bot commented on ZOOKEEPER-261: -- Github user breed commented on the issue:

[GitHub] zookeeper issue #120: ZOOKEEPER-261

Github user breed commented on the issue: https://github.com/apache/zookeeper/pull/120 hmm this is committed. anyone understands why it doesn't autoclose? --- 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

[jira] [Commented] (ZOOKEEPER-261) Reinitialized servers should not participate in leader election

[ https://issues.apache.org/jira/browse/ZOOKEEPER-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822369#comment-15822369 ] ASF GitHub Bot commented on ZOOKEEPER-261: -- Github user breed commented on the issue:

[GitHub] zookeeper issue #120: ZOOKEEPER-261

Github user breed commented on the issue: https://github.com/apache/zookeeper/pull/120 commited. thanx everyone for reviewing and brian for your contribution. --- 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

[jira] [Resolved] (ZOOKEEPER-261) Reinitialized servers should not participate in leader election

[ https://issues.apache.org/jira/browse/ZOOKEEPER-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed resolved ZOOKEEPER-261. - Resolution: Fixed committed to master > Reinitialized servers should not participate

Failed: ZOOKEEPER- PreCommit Build #211

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/211/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 467658 lines...] [exec]

Success: ZOOKEEPER- PreCommit Build #210

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/210/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 475154 lines...] [exec]

[jira] [Commented] (ZOOKEEPER-2664) ClientPortBindTest#testBindByAddress may fail due to "No such device" exception

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822029#comment-15822029 ] Ted Yu commented on ZOOKEEPER-2664: --- [~praste]: Looks like you mistakenly entered ZOOKEEPER-2664

[jira] [Commented] (ZOOKEEPER-2664) ClientPortBindTest#testBindByAddress may fail due to "No such device" exception

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822028#comment-15822028 ] Ted Yu commented on ZOOKEEPER-2664: --- https://github.com/apache/zookeeper/pull/149 >

[jira] [Issue Comment Deleted] (ZOOKEEPER-2664) ClientPortBindTest#testBindByAddress may fail due to "No such device" exception

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated ZOOKEEPER-2664: -- Comment: was deleted (was: https://github.com/apache/zookeeper/pull/149) >

[jira] [Commented] (ZOOKEEPER-2664) ClientPortBindTest#testBindByAddress may fail due to "No such device" exception

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822026#comment-15822026 ] ASF GitHub Bot commented on ZOOKEEPER-2664: --- GitHub user tedyu opened a pull request:

[GitHub] zookeeper pull request #149: ZOOKEEPER-2664: ClientPortBindTest#testBindByAd...

GitHub user tedyu opened a pull request: https://github.com/apache/zookeeper/pull/149 ZOOKEEPER-2664: ClientPortBindTest#testBindByAddress may fail due to "No such device" exception The following stack trace was observed intermittently: ``` Stacktrace

ZooKeeper_branch35_solaris - Build # 395 - Failure

See https://builds.apache.org/job/ZooKeeper_branch35_solaris/395/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 44 lines...] [junit] 2017-01-13

Failed: ZOOKEEPER- PreCommit Build #209

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/209/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 75 lines...] [exec] Pull

[jira] [Commented] (ZOOKEEPER-2664) ClientPortBindTest#testBindByAddress may fail due to "No such device" exception

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821981#comment-15821981 ] ASF GitHub Bot commented on ZOOKEEPER-2664: --- GitHub user praste opened a pull request:

[GitHub] zookeeper pull request #148: ZOOKEEPER-2664 Log4j2 migration

GitHub user praste opened a pull request: https://github.com/apache/zookeeper/pull/148 ZOOKEEPER-2664 Log4j2 migration You can merge this pull request into a Git repository by running: $ git pull https://github.com/praste/zookeeper log4j2-migration Alternatively you can

[jira] [Commented] (ZOOKEEPER-2664) ClientPortBindTest#testBindByAddress may fail due to "No such device" exception

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821881#comment-15821881 ] Ted Yu commented on ZOOKEEPER-2664: --- Since ZOOKEEPER-2395 didn't propose patch, I think we can

[jira] [Commented] (ZOOKEEPER-261) Reinitialized servers should not participate in leader election

[ https://issues.apache.org/jira/browse/ZOOKEEPER-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821844#comment-15821844 ] ASF GitHub Bot commented on ZOOKEEPER-261: -- Github user eribeiro commented on the issue:

[GitHub] zookeeper issue #120: ZOOKEEPER-261

Github user eribeiro commented on the issue: https://github.com/apache/zookeeper/pull/120 @enixon Thank you very much for the explanation! Makes sense, sorry for my misunderstanding. @breed Yep, agree. Let's push it forward. :+1: --- If your project is set up for it, you

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

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821839#comment-15821839 ] Edward Ribeiro commented on ZOOKEEPER-2659: --- Thanks for taking a stab at this issue,

[jira] [Commented] (ZOOKEEPER-2664) ClientPortBindTest#testBindByAddress may fail due to "No such device" exception

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821830#comment-15821830 ] Edward Ribeiro commented on ZOOKEEPER-2664: --- Hi [~tedyu], Thanks for the patch! :) The ZK

Re: ZooKeeper 3.4.10 release discussion

Hi Rakesh, Thansk for stepping up to this task! Pretty cool! :) Do you think https://issues.apache.org/jira/browse/ZOOKEEPER-2573 is worth targeting 3.4.10 too? Edward On Fri, Jan 13, 2017 at 7:56 AM, Rakesh Radhakrishnan wrote: > Hi All, > > I hope to cut an RC in a

ZooKeeper_branch34_solaris - Build # 1430 - Still Failing

See https://builds.apache.org/job/ZooKeeper_branch34_solaris/1430/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 187981 lines...] [junit] 2017-01-13

[jira] [Issue Comment Deleted] (ZOOKEEPER-2664) ClientPortBindTest#testBindByAddress may fail due to "No such device" exception

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Ribeiro updated ZOOKEEPER-2664: -- Comment: was deleted (was: Hi [~ted_yu] ) > ClientPortBindTest#testBindByAddress

[jira] [Commented] (ZOOKEEPER-2664) ClientPortBindTest#testBindByAddress may fail due to "No such device" exception

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821789#comment-15821789 ] Edward Ribeiro commented on ZOOKEEPER-2664: --- Hi [~ted_yu] >

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

See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/899/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 504643 lines...] [junit] 2017-01-13 12:00:01,693

Failed: ZOOKEEPER-2664 PreCommit Build #3561

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2664 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3561/ ### ## LAST 60 LINES OF THE CONSOLE ###

[jira] [Assigned] (ZOOKEEPER-2664) ClientPortBindTest#testBindByAddress may fail due to "No such device" exception

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu reassigned ZOOKEEPER-2664: - Assignee: Ted Yu > ClientPortBindTest#testBindByAddress may fail due to "No such device" >

[jira] [Updated] (ZOOKEEPER-2664) ClientPortBindTest#testBindByAddress may fail due to "No such device" exception

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated ZOOKEEPER-2664: -- Attachment: ZOOKEEPER-2664.v1.txt > ClientPortBindTest#testBindByAddress may fail due to "No such

[jira] [Created] (ZOOKEEPER-2664) ClientPortBindTest#testBindByAddress may fail due to "No such device" exception

Ted Yu created ZOOKEEPER-2664: - Summary: ClientPortBindTest#testBindByAddress may fail due to "No such device" exception Key: ZOOKEEPER-2664 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2664

Re: ZooKeeper 3.4.10 release discussion

Hi All, I hope to cut an RC in a week - giving some more time for your favorite outstanding blocker/critical issues. Will start moving out any tickets that are not blockers and/or won’t fit the timeline - there are 1 blocker, 5 critical, 15 major, 7 minor tickets outstanding as of now. Appreciate