ZooKeeper_branch34_jdk7 - Build # 1940 - Failure
See https://builds.apache.org/job/ZooKeeper_branch34_jdk7/1940/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 39.83 KB...] [junit] Running org.apache.zookeeper.test.RepeatStartupTest [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.063 sec [junit] Running org.apache.zookeeper.test.RestoreCommittedLogTest [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 20.431 sec [junit] Running org.apache.zookeeper.test.SaslAuthDesignatedClientTest [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.828 sec [junit] Running org.apache.zookeeper.test.SaslAuthDesignatedServerTest [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.917 sec [junit] Running org.apache.zookeeper.test.SaslAuthFailDesignatedClientTest [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.444 sec [junit] Running org.apache.zookeeper.test.SaslAuthFailNotifyTest [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.675 sec [junit] Running org.apache.zookeeper.test.SaslAuthFailTest [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.667 sec [junit] Running org.apache.zookeeper.test.SaslAuthMissingClientConfigTest [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.511 sec [junit] Running org.apache.zookeeper.test.SaslClientTest [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.068 sec [junit] Running org.apache.zookeeper.test.SessionInvalidationTest [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.567 sec [junit] Running org.apache.zookeeper.test.SessionTest [junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.914 sec [junit] Running org.apache.zookeeper.test.SessionTimeoutTest [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.907 sec [junit] Running org.apache.zookeeper.test.StandaloneTest [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.858 sec [junit] Running org.apache.zookeeper.test.StatTest [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.043 sec [junit] Running org.apache.zookeeper.test.StaticHostProviderTest [junit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.998 sec [junit] Running org.apache.zookeeper.test.SyncCallTest [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.36 sec [junit] Running org.apache.zookeeper.test.TruncateTest [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.775 sec [junit] Running org.apache.zookeeper.test.UpgradeTest [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.279 sec [junit] Running org.apache.zookeeper.test.WatchedEventTest [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.074 sec [junit] Running org.apache.zookeeper.test.WatcherFuncTest [junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.297 sec [junit] Running org.apache.zookeeper.test.WatcherTest [junit] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 28.808 sec [junit] Running org.apache.zookeeper.test.ZkDatabaseCorruptionTest [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.005 sec [junit] Running org.apache.zookeeper.test.ZooKeeperQuotaTest [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.707 sec fail.build.on.test.failure: BUILD FAILED /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/build.xml:1386: The following error occurred while executing this line: /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/build.xml:1389: Tests failed! Total time: 41 minutes 52 seconds Build step 'Invoke Ant' marked build as failure Archiving artifacts Recording test results Email was triggered for: Failure - Any Sending email for trigger: Failure - Any ### ## FAILED TESTS (if any) ## 1 tests failed. FAILED: org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testFailedTxnAsPartOfQuorumLoss Error Message: expected:<1> but was:<2> Stack Trace: junit.framework.AssertionFailedError: expected:<1> but was:<2> at org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testFailedTxnAsPartOfQuorumLoss(QuorumPeerMainTest.java:1202) at org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:55)
[GitHub] zookeeper pull request #537: ZOOKEEPER-2920: Upgrade OWASP Dependency Check ...
Github user phunt closed the pull request at: https://github.com/apache/zookeeper/pull/537 ---
[GitHub] zookeeper issue #537: ZOOKEEPER-2920: Upgrade OWASP Dependency Check to 3.2....
Github user hanm commented on the issue: https://github.com/apache/zookeeper/pull/537 Merged, please close PR. ---
[jira] [Resolved] (ZOOKEEPER-2920) Upgrade OWASP Dependency Check to 3.2.1
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Han resolved ZOOKEEPER-2920. Resolution: Fixed > Upgrade OWASP Dependency Check to 3.2.1 > --- > > Key: ZOOKEEPER-2920 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2920 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.5.4, 3.6.0, 3.4.12 >Reporter: Abraham Fine >Assignee: Patrick Hunt >Priority: Major > Labels: newbie, pull-request-available > Fix For: 3.6.0, 3.4.13, 3.5.5 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] zookeeper issue #536: ZOOKEEPER-2920: Upgrade OWASP Dependency Check to 3.2....
Github user hanm commented on the issue: https://github.com/apache/zookeeper/pull/536 LGTM, merged to master and 3.5. ---
[GitHub] zookeeper pull request #536: ZOOKEEPER-2920: Upgrade OWASP Dependency Check ...
Github user asfgit closed the pull request at: https://github.com/apache/zookeeper/pull/536 ---
Success: ZOOKEEPER- PreCommit Build #1770
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1770/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 41.68 MB...] [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/1770//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1770//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1770//console [exec] [exec] This message is automatically generated. [exec] [exec] [exec] == [exec] == [exec] Adding comment to Jira. [exec] == [exec] == [exec] [exec] [exec] Comment with id 16495968 added to ZOOKEEPER-2920. [exec] Session logged out. Session was JSESSIONID=C3EC350DFF91D2E8B6C618B3A6DF8835. [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: 41 minutes 40 seconds Archiving artifacts Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Recording test results Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 [description-setter] Description set: ZOOKEEPER-2920 Putting comment on the pull request Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Email was triggered for: Success Sending email for trigger: Success Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Commented] (ZOOKEEPER-2920) Upgrade OWASP Dependency Check to 3.2.1
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495968#comment-16495968 ] Hadoop QA commented on ZOOKEEPER-2920: -- +1 overall. GitHub Pull Request Build +1 @author. The patch does not contain any @author tags. +0 tests included. The patch appears to be a documentation patch that doesn't require 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/1770//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1770//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1770//console This message is automatically generated. > Upgrade OWASP Dependency Check to 3.2.1 > --- > > Key: ZOOKEEPER-2920 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2920 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.5.4, 3.6.0, 3.4.12 >Reporter: Abraham Fine >Assignee: Patrick Hunt >Priority: Major > Labels: newbie, pull-request-available > Fix For: 3.6.0, 3.4.13, 3.5.5 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Failed: ZOOKEEPER- PreCommit Build #1768
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1768/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 85.45 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/1768//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1768//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1768//console [exec] [exec] This message is automatically generated. [exec] [exec] [exec] == [exec] == [exec] Adding comment to Jira. [exec] == [exec] == [exec] [exec] [exec] [exec] Error: No value specified for option "issue" [exec] Session logged out. Session was JSESSIONID=D6FD2D646E1FFED9D85F14736F3D63D1. [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:1751: exec returned: 1 Total time: 25 minutes 46 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Recording test results Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 [description-setter] Could not determine description. Putting comment on the pull request Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 ### ## FAILED TESTS (if any) ## 9 tests failed. FAILED: org.apache.zookeeper.SaslAuthTest.testAuth Error Message: KeeperErrorCode = ConnectionLoss for /path1 Stack Trace: org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /path1 at org.apache.zookeeper.KeeperException.create(KeeperException.java:102) at org.apache.zookeeper.KeeperException.create(KeeperException.java:54) at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1450) at org.apache.zookeeper.SaslAuthTest.testAuth(SaslAuthTest.java:117) at org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79) FAILED: org.apache.zookeeper.SaslAuthTest.testInvalidSaslIds Error Message: KeeperErrorCode = ConnectionLoss for /invalid0 Stack Trace: org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /invalid0 at org.apache.zookeeper.KeeperException.create(KeeperException.java:102) at org.apache.zookeeper.KeeperException.create(KeeperException.java:54) at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1450) at org.apache.zookeeper.SaslAuthTest.testInvalidSaslIds(SaslAuthTest.java:158) at org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79) FAILED:
Failed: ZOOKEEPER- PreCommit Build #1769
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1769/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 87.41 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/1769//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1769//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1769//console [exec] [exec] This message is automatically generated. [exec] [exec] [exec] == [exec] == [exec] Adding comment to Jira. [exec] == [exec] == [exec] [exec] [exec] Comment with id 16495951 added to ZOOKEEPER-2920. [exec] Session logged out. Session was JSESSIONID=B0A3963E39D249984BE8F4DD044198F1. [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:1751: exec returned: 1 Total time: 18 minutes 19 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Recording test results Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 [description-setter] Description set: ZOOKEEPER-2920 Putting comment on the pull request Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 ### ## FAILED TESTS (if any) ## 1 tests failed. FAILED: org.apache.zookeeper.test.DisconnectedWatcherTest.testManyChildWatchersAutoReset Error Message: test timed out after 60 milliseconds Stack Trace: org.junit.runners.model.TestTimedOutException: test timed out after 60 milliseconds at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:502) at org.apache.zookeeper.ClientCnxn.submitRequest(ClientCnxn.java:1499) at org.apache.zookeeper.ClientCnxn.submitRequest(ClientCnxn.java:1487) at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1444) at org.apache.zookeeper.test.DisconnectedWatcherTest.testManyChildWatchersAutoReset(DisconnectedWatcherTest.java:229) at org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.lang.Thread.run(Thread.java:748)
[jira] [Commented] (ZOOKEEPER-2920) Upgrade OWASP Dependency Check to 3.2.1
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495951#comment-16495951 ] Hadoop QA commented on ZOOKEEPER-2920: -- -1 overall. GitHub Pull Request Build +1 @author. The patch does not contain any @author tags. +0 tests included. The patch appears to be a documentation patch that doesn't require 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/1769//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1769//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1769//console This message is automatically generated. > Upgrade OWASP Dependency Check to 3.2.1 > --- > > Key: ZOOKEEPER-2920 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2920 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.5.4, 3.6.0, 3.4.12 >Reporter: Abraham Fine >Assignee: Patrick Hunt >Priority: Major > Labels: newbie, pull-request-available > Fix For: 3.6.0, 3.4.13, 3.5.5 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] zookeeper issue #537: ZOOKEEPER-2920: Upgrade OWASP Dependency Check to 3.2....
Github user phunt commented on the issue: https://github.com/apache/zookeeper/pull/537 This is specifically for 3.4 - see #536 for 3.5/master. ---
[GitHub] zookeeper issue #536: ZOOKEEPER-2920: Upgrade OWASP Dependency Check to 3.2....
Github user phunt commented on the issue: https://github.com/apache/zookeeper/pull/536 I'm afraid conflict on 3.4 (fine for 3.5 though) - see #537 for branch-3.4 PR ---
[GitHub] zookeeper pull request #537: ZOOKEEPER-2920: Upgrade OWASP Dependency Check ...
GitHub user phunt opened a pull request: https://github.com/apache/zookeeper/pull/537 ZOOKEEPER-2920: Upgrade OWASP Dependency Check to 3.2.1 Updated and verified on all the active branches. Change-Id: I750d7e576e8c731aab4cef26f6863eac6b1b8dc2 (cherry picked from commit d065898f77c9162faaffb9fa0dad543eb07771db) You can merge this pull request into a Git repository by running: $ git pull https://github.com/phunt/zookeeper ZOOKEEPER-2920-br34 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zookeeper/pull/537.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 #537 commit 37e4015ff07a96ce66dd8a3cf6c6df2004119d64 Author: Patrick Hunt Date: 2018-05-31T00:49:03Z ZOOKEEPER-2920: Upgrade OWASP Dependency Check to 3.2.1 Updated and verified on all the active branches. Change-Id: I750d7e576e8c731aab4cef26f6863eac6b1b8dc2 (cherry picked from commit d065898f77c9162faaffb9fa0dad543eb07771db) ---
[jira] [Updated] (ZOOKEEPER-2920) Upgrade OWASP Dependency Check to 3.2.1
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated ZOOKEEPER-2920: -- Labels: newbie pull-request-available (was: newbie) > Upgrade OWASP Dependency Check to 3.2.1 > --- > > Key: ZOOKEEPER-2920 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2920 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.5.4, 3.6.0, 3.4.12 >Reporter: Abraham Fine >Assignee: Patrick Hunt >Priority: Major > Labels: newbie, pull-request-available > Fix For: 3.6.0, 3.4.13, 3.5.5 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] zookeeper pull request #536: ZOOKEEPER-2920: Upgrade OWASP Dependency Check ...
GitHub user phunt opened a pull request: https://github.com/apache/zookeeper/pull/536 ZOOKEEPER-2920: Upgrade OWASP Dependency Check to 3.2.1 Updated and verified on all the active branches. Change-Id: I750d7e576e8c731aab4cef26f6863eac6b1b8dc2 You can merge this pull request into a Git repository by running: $ git pull https://github.com/phunt/zookeeper ZOOKEEPER-2920 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zookeeper/pull/536.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 #536 commit d065898f77c9162faaffb9fa0dad543eb07771db Author: Patrick Hunt Date: 2018-05-31T00:49:03Z ZOOKEEPER-2920: Upgrade OWASP Dependency Check to 3.2.1 Updated and verified on all the active branches. Change-Id: I750d7e576e8c731aab4cef26f6863eac6b1b8dc2 ---
[jira] [Updated] (ZOOKEEPER-2920) Upgrade OWASP Dependency Check to 3.2.1
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2920: Summary: Upgrade OWASP Dependency Check to 3.2.1 (was: Upgrade OWASP Dependency Check to 3.0) > Upgrade OWASP Dependency Check to 3.2.1 > --- > > Key: ZOOKEEPER-2920 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2920 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.5.4, 3.6.0, 3.4.12 >Reporter: Abraham Fine >Assignee: Patrick Hunt >Priority: Major > Labels: newbie > Fix For: 3.6.0, 3.4.13, 3.5.5 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ZOOKEEPER-2920) Upgrade OWASP Dependency Check to 3.2.1
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2920: Labels: newbie (was: ) > Upgrade OWASP Dependency Check to 3.2.1 > --- > > Key: ZOOKEEPER-2920 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2920 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.5.4, 3.6.0, 3.4.12 >Reporter: Abraham Fine >Assignee: Patrick Hunt >Priority: Major > Labels: newbie > Fix For: 3.6.0, 3.4.13, 3.5.5 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ZOOKEEPER-2920) Upgrade OWASP Dependency Check to 3.2.1
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2920: Affects Version/s: 3.6.0 3.5.4 3.4.12 > Upgrade OWASP Dependency Check to 3.2.1 > --- > > Key: ZOOKEEPER-2920 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2920 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.5.4, 3.6.0, 3.4.12 >Reporter: Abraham Fine >Assignee: Patrick Hunt >Priority: Major > Labels: newbie > Fix For: 3.6.0, 3.4.13, 3.5.5 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ZOOKEEPER-2920) Upgrade OWASP Dependency Check to 3.2.1
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2920: Fix Version/s: 3.5.5 3.4.13 3.6.0 > Upgrade OWASP Dependency Check to 3.2.1 > --- > > Key: ZOOKEEPER-2920 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2920 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.5.4, 3.6.0, 3.4.12 >Reporter: Abraham Fine >Assignee: Patrick Hunt >Priority: Major > Labels: newbie > Fix For: 3.6.0, 3.4.13, 3.5.5 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ZOOKEEPER-2920) Upgrade OWASP Dependency Check to 3.2.1
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2920: Component/s: build > Upgrade OWASP Dependency Check to 3.2.1 > --- > > Key: ZOOKEEPER-2920 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2920 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.5.4, 3.6.0, 3.4.12 >Reporter: Abraham Fine >Assignee: Patrick Hunt >Priority: Major > Labels: newbie > Fix For: 3.6.0, 3.4.13, 3.5.5 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ZOOKEEPER-2920) Upgrade OWASP Dependency Check to 3.0
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt reassigned ZOOKEEPER-2920: --- Assignee: Patrick Hunt (was: Abraham Fine) > Upgrade OWASP Dependency Check to 3.0 > - > > Key: ZOOKEEPER-2920 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2920 > Project: ZooKeeper > Issue Type: Bug >Reporter: Abraham Fine >Assignee: Patrick Hunt >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] zookeeper pull request #535: Feature/read comment
Github user DorgenJones closed the pull request at: https://github.com/apache/zookeeper/pull/535 ---
[GitHub] zookeeper pull request #535: Feature/read comment
GitHub user DorgenJones opened a pull request: https://github.com/apache/zookeeper/pull/535 Feature/read comment You can merge this pull request into a Git repository by running: $ git pull https://github.com/DorgenJones/zookeeper feature/read_comment Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zookeeper/pull/535.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 #535 commit cab47d2a8138dc69e9cd9a4955f0121ee31633a2 Author: dujiang02 Date: 2018-05-28T11:18:35Z é 读注é commit cdf43fdc77cbffa698630c67a8dc3a48287867bf Author: dujiang02 Date: 2018-05-31T00:43:41Z comment ---
[jira] [Commented] (ZOOKEEPER-3040) flaky test EphemeralNodeDeletionTest
[
https://issues.apache.org/jira/browse/ZOOKEEPER-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495927#comment-16495927
]
Michael Han commented on ZOOKEEPER-3040:
{quote}I ran the test 2.000 times, all success, so unfortunately I could not
reproduce the problem.
{quote}
A couple of flaky tests we saw and fixed can only be reproduced if we ran the
entire test suite. Maybe this test is one of them if running in isolation yield
a deterministic success yet jenkins still complains..
> flaky test EphemeralNodeDeletionTest
>
>
> Key: ZOOKEEPER-3040
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3040
> Project: ZooKeeper
> Issue Type: Bug
> Components: tests
>Affects Versions: 3.5.4, 3.6.0, 3.4.12
>Reporter: Patrick Hunt
>Assignee: Norbert Kalmar
>Priority: Major
> Labels: flaky
> Fix For: 3.6.0, 3.4.13, 3.5.5
>
>
> Flakey test EphemeralNodeDeletionTest
> {noformat}
> java.lang.AssertionError: After session close ephemeral node must be deleted
> expected null, but
> was:<4294967302,4294967302,1525988536834,1525988536834,0,0,0,144127862257483776,1,0,4294967302
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ZOOKEEPER-2684) Fix a crashing bug in the mixed workloads commit processor
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Han updated ZOOKEEPER-2684: --- Fix Version/s: 3.6.0 > Fix a crashing bug in the mixed workloads commit processor > -- > > Key: ZOOKEEPER-2684 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2684 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.6.0 > Environment: with pretty heavy load on a real cluster >Reporter: Ryan Zhang >Assignee: Kfir Lev-Ari >Priority: Blocker > Fix For: 3.6.0 > > Attachments: ZOOKEEPER-2684.patch > > > We deployed our build with ZOOKEEPER-2024 and it quickly started to crash > with the following error > atla-buh-05-sr1.prod.twttr.net: 2017-01-18 22:24:42,305 - ERROR > [CommitProcessor:2] > -org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:268) > – Got cxid 0x119fa expected 0x11fc5 for client session id 1009079ba470055 > atla-buh-05-sr1.prod.twttr.net: 2017-01-18 22:32:04,746 - ERROR > [CommitProcessor:2] > -org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:268) > – Got cxid 0x698 expected 0x928 for client session id 4002eeb3fd0009d > atla-buh-05-sr1.prod.twttr.net: 2017-01-18 22:34:46,648 - ERROR > [CommitProcessor:2] > -org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:268) > – Got cxid 0x8904 expected 0x8f34 for client session id 51b8905c90251 > atla-buh-05-sr1.prod.twttr.net: 2017-01-18 22:43:46,834 - ERROR > [CommitProcessor:2] > -org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:268) > – Got cxid 0x3a8d expected 0x3ebc for client session id 2051af11af900cc > clearly something is not right in the new commit processor per session queue > implementation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ZOOKEEPER-1237) ERRORs being logged when queued responses are sent after socket has closed.
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Han updated ZOOKEEPER-1237:
---
Fix Version/s: 3.4.10
> ERRORs being logged when queued responses are sent after socket has closed.
> ---
>
> Key: ZOOKEEPER-1237
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1237
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
>Affects Versions: 3.3.4, 3.4.0, 3.5.0
>Reporter: Patrick Hunt
>Priority: Major
> Fix For: 3.4.10
>
> Attachments: zookeeper-3.4.5-ZK1237.patch
>
>
> After applying ZOOKEEPER-1049 to 3.3.3 (I believe the same problem exists in
> 3.4/3.5 but haven't tested this) I'm seeing the following exception more
> frequently:
> {noformat}
> Oct 19, 1:31:53 PM ERROR
> Unexpected Exception:
> java.nio.channels.CancelledKeyException
> at sun.nio.ch.SelectionKeyImpl.ensureValid(SelectionKeyImpl.java:55)
> at sun.nio.ch.SelectionKeyImpl.interestOps(SelectionKeyImpl.java:59)
> at
> org.apache.zookeeper.server.NIOServerCnxn.sendBuffer(NIOServerCnxn.java:418)
> at
> org.apache.zookeeper.server.NIOServerCnxn.sendResponse(NIOServerCnxn.java:1509)
> at
> org.apache.zookeeper.server.FinalRequestProcessor.processRequest(FinalRequestProcessor.java:367)
> at
> org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:73)
> {noformat}
> This is a long standing problem where we try to send a response after the
> socket has been closed. Prior to ZOOKEEPER-1049 this issues happened much
> less frequently (2 sec linger), but I believe it was possible. The timing
> window is just wider now.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (ZOOKEEPER-2044) CancelledKeyException in zookeeper branch-3.4
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Han reassigned ZOOKEEPER-2044:
--
Assignee: Michael Han (was: Flavio Junqueira)
> CancelledKeyException in zookeeper branch-3.4
> -
>
> Key: ZOOKEEPER-2044
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2044
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
>Affects Versions: 3.4.6
> Environment: Red Hat Enterprise Linux Server release 6.2
>Reporter: shamjith antholi
>Assignee: Michael Han
>Priority: Minor
> Fix For: 3.4.10
>
> Attachments: ZOOKEEPER-2044.patch, ZOOKEEPER-2044.patch
>
>
> I am getting cancelled key exception in zookeeper (version 3.4.5). Please see
> the log below. When this error is thrown, the connected solr shard is going
> down by giving the error "Failed to index metadata in
> Solr,StackTrace=SolrError: HTTP status 503.Reason:
> {"responseHeader":{"status":503,"QTime":204},"error":{"msg":"ClusterState
> says we are the leader, but locally we don't think so","code":503" and
> ultimately the current activity is going down. Could you please give a
> solution for this ?
> Zookeper log
> --
> 2014-09-16 02:58:47,799 [myid:1] - INFO
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@832] - Client
> attempting to renew session 0x24868e7ca980003 at /172.22.0.5:58587
> 2014-09-16 02:58:47,800 [myid:1] - INFO
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:Learner@107] - Revalidating
> client: 0x24868e7ca980003
> 2014-09-16 02:58:47,802 [myid:1] - INFO
> [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:ZooKeeperServer@588] - Invalid
> session 0x24868e7ca980003 for client /172.22.0.5:58587, probably expired
> 2014-09-16 02:58:47,803 [myid:1] - INFO
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed
> socket connection for client /172.22.0.5:58587 which had sessionid
> 0x24868e7ca980003
> 2014-09-16 02:58:47,810 [myid:1] - ERROR
> [CommitProcessor:1:NIOServerCnxn@180] - Unexpected Exception:
> java.nio.channels.CancelledKeyException
> at sun.nio.ch.SelectionKeyImpl.ensureValid(SelectionKeyImpl.java:55)
> at sun.nio.ch.SelectionKeyImpl.interestOps(SelectionKeyImpl.java:59)
> at
> org.apache.zookeeper.server.NIOServerCnxn.sendBuffer(NIOServerCnxn.java:153)
> at
> org.apache.zookeeper.server.NIOServerCnxn.sendResponse(NIOServerCnxn.java:1076)
> at
> org.apache.zookeeper.server.NIOServerCnxn.process(NIOServerCnxn.java:1113)
> at org.apache.zookeeper.server.DataTree.setWatches(DataTree.java:1327)
> at
> org.apache.zookeeper.server.ZKDatabase.setWatches(ZKDatabase.java:384)
> at
> org.apache.zookeeper.server.FinalRequestProcessor.processRequest(FinalRequestProcessor.java:304)
> at
> org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:74)
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ZOOKEEPER-2867) an expired ZK session can be re-established
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495919#comment-16495919
]
Michael Han commented on ZOOKEEPER-2867:
[~junrao] - ok, finally get back to this :=).
I checked the broker 1 and 2's commit log, session {{0x25cd1e82c110001}} was
referenced after the "session close" log statement. For example, in server 1's
log file, the first reference of the session 0x25cd1e82c110001 after it's
"closed" is:
{quote}6/27/17 3:05:20 PM PDT session 0x25cd1e82c110001 cxid 0xdc zxid
0x3047b setData
'/cp15/brokers/topics//state,#7b22636f6e74726f6c6c65725f65706f6368223a312c226c6561646572223a302c2276657273696f6e223a312c226c65616465725f65706f6368223a352c22697372223a5b302c315d7d,10
{quote}
Similarly for server 2's commit log session 0x25cd1e82c110001 is referenced
after the "closed" statement as well.
I think in this case session 0x25cd1e82c110001 is not get closed. It could be
that the close requests were sent to server 1 and 2 and then something happened
so the close requests never committed. Note the "close session" entry in the
commit log is missing some context so I can't really tell where this log
statement was from - if we have more detailed log such to indicate where this
log statement was coming from, I might be able to tell the state of the server
at that time.
One way to make sure the close session proposal really gets committed across
the quorum is to looking for this log statement (need to enable debug logging):
[https://github.com/apache/zookeeper/blob/branch-3.4/src/java/main/org/apache/zookeeper/server/quorum/CommitProcessor.java#L164]
At this point, the proposal reached consensus and is persistent across a quorum
of nodes (the state change might not yet applied to the data tree, but as long
as the proposal is persistent we are fine).
> an expired ZK session can be re-established
> ---
>
> Key: ZOOKEEPER-2867
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2867
> Project: ZooKeeper
> Issue Type: Bug
>Affects Versions: 3.4.10
>Reporter: Jun Rao
>Assignee: Michael Han
>Priority: Major
> Attachments: 0.parsed_commit_log, 1.parsed_commit_log,
> 2.parsed_commit_log, zk.0.08-02, zk.0.08-02, zk.0.formatted, zk.1.08-02,
> zk.1.08-02, zk.1.formatted, zk.2.08-02, zk.2.08-02
>
>
> Not sure if this is a real bug, but I found an instance when a ZK client
> seems to be able to renew a session already expired by the ZK server.
> From ZK server log, session 25cd1e82c110001 was expired at 22:04:39.
> {code:java}
> June 27th 2017, 22:04:39.000 INFO
> org.apache.zookeeper.server.ZooKeeperServer Expiring session
> 0x25cd1e82c110001, timeout of 12000ms exceeded
> June 27th 2017, 22:04:39.001 DEBUG
> org.apache.zookeeper.server.quorum.Leader Proposing::
> sessionid:0x25cd1e82c110001 type:closeSession cxid:0x0 zxid:0x20fc4
> txntype:-11 reqpath:n/a
> June 27th 2017, 22:04:39.001 INFO
> org.apache.zookeeper.server.PrepRequestProcessorProcessed session
> termination for sessionid: 0x25cd1e82c110001
> June 27th 2017, 22:04:39.001 DEBUG
> org.apache.zookeeper.server.quorum.CommitProcessor Processing request::
> sessionid:0x25cd1e82c110001 type:closeSession cxid:0x0 zxid:0x20fc4
> txntype:-11 reqpath:n/a
> June 27th 2017, 22:05:20.324 INFO
> org.apache.zookeeper.server.quorum.Learner Revalidating client:
> 0x25cd1e82c110001
> June 27th 2017, 22:05:20.324 INFO
> org.apache.zookeeper.server.ZooKeeperServer Client attempting to renew
> session 0x25cd1e82c110001 at /100.96.5.6:47618
> June 27th 2017, 22:05:20.325 INFO
> org.apache.zookeeper.server.ZooKeeperServer Established session
> 0x25cd1e82c110001 with negotiated timeout 12000 for client /100.96.5.6:47618
> {code}
> From ZK client's log, it was able to renew the expired session on 22:05:20.
> {code:java}
> June 27th 2017, 22:05:18.590 INFOorg.apache.zookeeper.ClientCnxn Client
> session timed out, have not heard from server in 4485ms for sessionid
> 0x25cd1e82c110001, closing socket connection and attempting reconnect 0
> June 27th 2017, 22:05:18.590 WARNorg.apache.zookeeper.ClientCnxn Client
> session timed out, have not heard from server in 4485ms for sessionid
> 0x25cd1e82c110001 0
> June 27th 2017, 22:05:19.325 WARNorg.apache.zookeeper.ClientCnxn SASL
> configuration failed: javax.security.auth.login.LoginException: No JAAS
> configuration section named 'Client' was found in specified JAAS
> configuration file: '/opt/confluent/etc/kafka/server_jaas.conf'. Will
> continue connection to Zookeeper server without SASL authentication, if
> Zookeeper server allows it. 0
> June 27th 2017, 22:05:19.326 INFOorg.apache.zookeeper.ClientCnxn Opening
> socket
[GitHub] zookeeper issue #451: ZOOKEEPER-2184: Zookeeper Client should re-resolve hos...
Github user ijuma commented on the issue: https://github.com/apache/zookeeper/pull/451 Also, as I'm sure many are wondering, a discussion about the next release including this fix is taking place in the mailing list: https://lists.apache.org/thread.html/8d3dcd84b0ad47563e2cf2619eb0775066ff975453865938dd4e7380@%3Cdev.zookeeper.apache.org%3E ---
[GitHub] zookeeper issue #451: ZOOKEEPER-2184: Zookeeper Client should re-resolve hos...
Github user ijuma commented on the issue: https://github.com/apache/zookeeper/pull/451 Thanks @anmolnar, @fpj and @hanm for getting this in. ---
[jira] [Comment Edited] (ZOOKEEPER-3040) flaky test EphemeralNodeDeletionTest
[
https://issues.apache.org/jira/browse/ZOOKEEPER-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495070#comment-16495070
]
Norbert Kalmar edited comment on ZOOKEEPER-3040 at 5/30/18 11:53 AM:
-
I ran the test 2.000 times, all success, so unfortunately I could not reproduce
the problem.
I checked the close() method, it is synchronized.
I will add a sync call and run the test again a 1.000 times to verify it will
pass.
was (Author: nkalmar):
I ran the test 2.000 times, all success, so unfortunately I could not reproduce.
I checked the close() method, it is synchronized.
I will add a sync call and run the test again a 1.000 times to verify it will
pass.
> flaky test EphemeralNodeDeletionTest
>
>
> Key: ZOOKEEPER-3040
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3040
> Project: ZooKeeper
> Issue Type: Bug
> Components: tests
>Affects Versions: 3.5.4, 3.6.0, 3.4.12
>Reporter: Patrick Hunt
>Assignee: Norbert Kalmar
>Priority: Major
> Labels: flaky
> Fix For: 3.6.0, 3.4.13, 3.5.5
>
>
> Flakey test EphemeralNodeDeletionTest
> {noformat}
> java.lang.AssertionError: After session close ephemeral node must be deleted
> expected null, but
> was:<4294967302,4294967302,1525988536834,1525988536834,0,0,0,144127862257483776,1,0,4294967302
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ZOOKEEPER-3040) flaky test EphemeralNodeDeletionTest
[
https://issues.apache.org/jira/browse/ZOOKEEPER-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495070#comment-16495070
]
Norbert Kalmar commented on ZOOKEEPER-3040:
---
I ran the test 2.000 times, all success, so unfortunately I could not reproduce.
I checked the close() method, it is synchronized.
I will add a sync call and run the test again a 1.000 times to verify it will
pass.
> flaky test EphemeralNodeDeletionTest
>
>
> Key: ZOOKEEPER-3040
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3040
> Project: ZooKeeper
> Issue Type: Bug
> Components: tests
>Affects Versions: 3.5.4, 3.6.0, 3.4.12
>Reporter: Patrick Hunt
>Assignee: Norbert Kalmar
>Priority: Major
> Labels: flaky
> Fix For: 3.6.0, 3.4.13, 3.5.5
>
>
> Flakey test EphemeralNodeDeletionTest
> {noformat}
> java.lang.AssertionError: After session close ephemeral node must be deleted
> expected null, but
> was:<4294967302,4294967302,1525988536834,1525988536834,0,0,0,144127862257483776,1,0,4294967302
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ZOOKEEPER-2968) Add C client code coverage tests
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated ZOOKEEPER-2968: -- Labels: pull-request-available (was: ) > Add C client code coverage tests > > > Key: ZOOKEEPER-2968 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2968 > Project: ZooKeeper > Issue Type: Test > Components: tests >Affects Versions: 3.5.3, 3.4.11 >Reporter: Mark Fenes >Assignee: Mark Fenes >Priority: Major > Labels: pull-request-available > > We have limited code coverage support in ZK. Similarly to Java code coverage > tests add C client code coverage tests by using GCC tools like gcov and lcov. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] zookeeper issue #467: ZOOKEEPER-2968: Add C client code coverage tests
Github user anmolnar commented on the issue: https://github.com/apache/zookeeper/pull/467 @phunt @hanm Are you guys happy to commit this as part of the code coverage initiative or have any comments that we should address first? ---
Success: ZOOKEEPER- PreCommit Build #1767
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1767/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 85.14 MB...] [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/1767//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1767//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1767//console [exec] [exec] This message is automatically generated. [exec] [exec] [exec] == [exec] == [exec] Adding comment to Jira. [exec] == [exec] == [exec] [exec] [exec] Comment with id 16494995 added to ZOOKEEPER-3034. [exec] Session logged out. Session was JSESSIONID=C193D9C47B9ACC4461ECF1EB28E3D629. [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 15 seconds Archiving artifacts Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Recording test results Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 [description-setter] Description set: ZOOKEEPER-3034 Putting comment on the pull request Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Email was triggered for: Success Sending email for trigger: Success Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8 ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Commented] (ZOOKEEPER-3034) Facing issues while building from source
[
https://issues.apache.org/jira/browse/ZOOKEEPER-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494995#comment-16494995
]
Hadoop QA commented on ZOOKEEPER-3034:
--
+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/1767//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1767//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1767//console
This message is automatically generated.
> Facing issues while building from source
>
>
> Key: ZOOKEEPER-3034
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3034
> Project: ZooKeeper
> Issue Type: Bug
> Components: build
>Affects Versions: 3.4.11
> Environment: Linux x86_64, Ubuntu 18.04, Ubuntu 17.10.
>Reporter: Namrata Bhave
>Assignee: Andor Molnar
>Priority: Minor
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Building Zookeeper from source using below steps:
> {{git clone git://github.com/apache/zookeeper}}
> {{cd zookeeper}}
> {{git checkout tags/release-3.4.11}}
> {{ant compile}}
> {{cd src/c}}
> {{sudo apt-get install -y libcppunit-dev}}
> {{ACLOCAL="aclocal -I /usr/share/aclocal" autoreconf -if}}
> {{./configure && make && sudo make install}}
> {{sudo make distclean}}
>
> The 'autoreconf -if' step fails with below error:
> + ACLOCAL='aclocal -I /usr/share/aclocal'
> + autoreconf -if
> configure.ac:37: warning: macro 'AM_PATH_CPPUNIT' not found in library
> libtoolize: putting auxiliary files in '.'.
> libtoolize: copying file './ltmain.sh'
> libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
> libtoolize: and rerunning libtoolize and aclocal.
> libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> configure.ac:37: warning: macro 'AM_PATH_CPPUNIT' not found in library
> configure.ac:37: error: possibly undefined macro: AM_PATH_CPPUNIT
> If this token and others are legitimate, please use m4_pattern_allow.
> See the Autoconf documentation.
> autoreconf: /usr/bin/autoconf failed with exit status: 1
> Build step 'Execute shell' marked build as failure
>
> This is happening on Ubuntu 18.04. Can someone please help in resolving this
> error?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] zookeeper issue #528: ZOOKEEPER-3034 Facing issues while building from sourc...
Github user anmolnar commented on the issue: https://github.com/apache/zookeeper/pull/528 @phunt I ended up defining a custom macro to support static linking. Now the script works with older versions of `pkg-config` too. ---
[GitHub] zookeeper issue #528: ZOOKEEPER-3034 Facing issues while building from sourc...
Github user anmolnar commented on the issue: https://github.com/apache/zookeeper/pull/528 Yeah, I see what the problem is: `pkg-config` package has to be installed, but there's another problem with the version that is shipped with 14.04: it doesn't have `PKG_CHECK_MODULES_STATIC` macro, because it has been added in a more recent version according to this bug: https://bugs.freedesktop.org/show_bug.cgi?id=19541 Adding the definition of the macro to our `configure.ac` script solves the problem, but I don't want it to be effective if recent version of pkg-config is in use. Trying to add it as a conditional, but my autoconf knowledge doesn't seem to be enough here. Still looking. ---
[GitHub] zookeeper issue #533: ZOOKEEPER-2989:IPv6 literal address causes problems fo...
Github user maoling commented on the issue: https://github.com/apache/zookeeper/pull/533 @anmolnar **InitialMessage** is a inner-class of **QuorumCnxManager**. Is it necessary to a separate test file? @phunt @hanm What's your opinion? ---
