Jenkins build became unstable: zookeeper-master-maven #825

[Apache Jenkins Server]

See 

ZooKeeper_branch34_jdk8 - Build # 2177 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_jdk8/2177/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 43.53 KB...]
[junit] Running org.apache.zookeeper.test.RestoreCommittedLogTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
111.735 sec
[junit] Running org.apache.zookeeper.test.SaslAuthDesignatedClientTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.045 sec
[junit] Running org.apache.zookeeper.test.SaslAuthDesignatedServerTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.971 sec
[junit] Running org.apache.zookeeper.test.SaslAuthFailDesignatedClientTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.219 sec
[junit] Running org.apache.zookeeper.test.SaslAuthFailNotifyTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.925 sec
[junit] Running org.apache.zookeeper.test.SaslAuthFailTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.002 sec
[junit] Running org.apache.zookeeper.test.SaslAuthMissingClientConfigTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.956 sec
[junit] Running org.apache.zookeeper.test.SaslClientTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.134 sec
[junit] Running org.apache.zookeeper.test.SessionInvalidationTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.357 sec
[junit] Running org.apache.zookeeper.test.SessionTest
[junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
13.263 sec
[junit] Running org.apache.zookeeper.test.SessionTimeoutTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.064 sec
[junit] Running org.apache.zookeeper.test.StandaloneTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.936 sec
[junit] Running org.apache.zookeeper.test.StatTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.381 sec
[junit] Running org.apache.zookeeper.test.StaticHostProviderTest
[junit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.654 sec
[junit] Running org.apache.zookeeper.test.SyncCallTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.039 sec
[junit] Running org.apache.zookeeper.test.TruncateTest
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
23.393 sec
[junit] Running org.apache.zookeeper.test.UpgradeTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.347 sec
[junit] Running org.apache.zookeeper.test.WatchedEventTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.137 sec
[junit] Running org.apache.zookeeper.test.WatcherFuncTest
[junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
4.755 sec
[junit] Running org.apache.zookeeper.test.WatcherTest
[junit] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
33.373 sec
[junit] Running org.apache.zookeeper.test.ZkDatabaseCorruptionTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
16.925 sec
[junit] Running org.apache.zookeeper.test.ZooKeeperQuotaTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.044 sec
[junit] Running org.apache.jute.BinaryInputArchiveTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.137 sec

fail.build.on.test.failure:

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk8/build.xml:1425: 
The following error occurred while executing this line:
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk8/build.xml:1428: 
Tests failed!

Total time: 69 minutes 37 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) 
##
4 tests failed.
FAILED:  
org.apache.zookeeper.test.DisconnectedWatcherTest.testManyChildWatchersAutoReset

Error Message:
test timed out after 84 milliseconds

Stack Trace:
org.junit.runners.model.TestTimedOutException: test timed out after 84 
milliseconds
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:502)
at org.apache.zookeeper.ClientCnxn.submitRequest(ClientCnxn.java:1414)
at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:798)
at 

Jenkins build is back to normal : PreCommit-ZOOKEEPER-github-pr-build-maven #2085

[Apache Jenkins Server]

See 

Build failed in Jenkins: PreCommit-ZOOKEEPER-github-pr-build-maven #2084

[Apache Jenkins Server]

See 


Changes:

[jordan] ZOOKEEPER-3831 - add a compatibility test module


--
[...truncated 909.19 KB...]
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-manager-plexus/1.9.2/maven-scm-manager-plexus-1.9.2.jar
 (11 kB at 709 kB/s)
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-gitexe/1.9.2/maven-scm-provider-gitexe-1.9.2.jar
 (64 kB at 3.8 MB/s)
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/com/github/stephenc/wagon/wagon-gitsite/0.5/wagon-gitsite-0.5.jar
 (20 kB at 1.1 MB/s)
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-api/1.9.2/maven-scm-api-1.9.2.jar
 (106 kB at 5.9 MB/s)
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-git-commons/1.9.2/maven-scm-provider-git-commons-1.9.2.jar
 (38 kB at 1.2 MB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/felix/maven-bundle-plugin/2.3.7/maven-bundle-plugin-2.3.7.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/felix/maven-bundle-plugin/2.3.7/maven-bundle-plugin-2.3.7.pom
 (4.0 kB at 267 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/felix/maven-bundle-plugin/2.3.7/maven-bundle-plugin-2.3.7.jar
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/felix/maven-bundle-plugin/2.3.7/maven-bundle-plugin-2.3.7.jar
 (124 kB at 5.0 MB/s)
[INFO] Building tar: 

[INFO] 
[INFO] --- maven-assembly-plugin:3.1.0:single (lib-assembly) @ 
zookeeper-assembly ---
[INFO] Reading assembly descriptor: 

[INFO] Building tar: 

[INFO] 
[INFO] --- checksum-maven-plugin:1.8:artifacts (default) @ zookeeper-assembly 
---
[INFO] apache-zookeeper-3.7.0-SNAPSHOT-bin.tar.gz - SHA-512 : 
f535644cf8fa4f21a6b169339928015ca085327015a93146a6a3428d847458ed45d4f8c22c6711217f355b01dd7bdaf0b318cceb44798f62df36234eab6c49d7
[INFO] apache-zookeeper-3.7.0-SNAPSHOT-lib.tar.gz - SHA-512 : 
3a7fbc68d874492d4e35b0c69eddd831bda8d0a8dac35e36fb7d65c9cfc7fe76dca49543b9a74f05768616020aad7fbbc1467ee93d5fdec9c93244bc9c12a3a2
[INFO] 
[INFO] >>> spotbugs-maven-plugin:4.0.0:check (default-cli) > :spotbugs @ 
zookeeper-assembly >>>
[INFO] 
[INFO] --- spotbugs-maven-plugin:4.0.0:spotbugs (spotbugs) @ zookeeper-assembly 
---
[INFO] 
[INFO] <<< spotbugs-maven-plugin:4.0.0:check (default-cli) < :spotbugs @ 
zookeeper-assembly <<<
[INFO] 
[INFO] 
[INFO] --- spotbugs-maven-plugin:4.0.0:check (default-cli) @ zookeeper-assembly 
---
[INFO] 
[INFO] --- maven-checkstyle-plugin:3.1.0:check (default-cli) @ 
zookeeper-assembly ---
[INFO] Starting audit...
Audit done.
[INFO] 
[INFO] -< org.apache.zookeeper:zookeeper-compatibility-tests >-
[INFO] Building Apache ZooKeeper - Compatibility Tests 3.7.0-SNAPSHOT   [14/20]
[INFO] [ jar ]-
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/curator/curator-recipes/5.0.0/curator-recipes-5.0.0.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/curator/curator-recipes/5.0.0/curator-recipes-5.0.0.pom
 (3.6 kB at 39 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/curator/apache-curator/5.0.0/apache-curator-5.0.0.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/curator/apache-curator/5.0.0/apache-curator-5.0.0.pom
 (40 kB at 1.3 MB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/curator/curator-framework/5.0.0/curator-framework-5.0.0.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/curator/curator-framework/5.0.0/curator-framework-5.0.0.pom
 (3.6 kB at 115 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/curator/curator-client/5.0.0/curator-client-5.0.0.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/curator/curator-client/5.0.0/curator-client-5.0.0.pom
 (4.4 kB at 244 kB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/zookeeper/zookeeper/3.6.0/zookeeper-3.6.0.pom
[INFO] Downloaded from central: 

[GitHub] [zookeeper] Randgalt opened a new pull request #1369: ZOOKEEPER-3831 - add a compatibility test module

[GitBox]

Randgalt opened a new pull request #1369:
URL: https://github.com/apache/zookeeper/pull/1369


   ZooKeeper has many external libraries that are dependent on staying 
compatible. For example, Apache Curator. This new module will be used to add 
compatibility tests for any third party library, tool, etc. that we want to 
ensure maintains compatibility. The module is configured with Maven not to 
install/deploy so it's only for testing purposes. An initial test using Apache 
Curator is added.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Jenkins build is back to normal : zookeeper-master-maven-jdk12 #529

[Apache Jenkins Server]

See 

Jenkins build is back to stable : zookeeper-master-maven-jdk-ea #19

[Apache Jenkins Server]

See 

Jenkins build is back to stable : zookeeper-branch36-java8 #200

[Apache Jenkins Server]

See 

[GitHub] [zookeeper] symat commented on pull request #1356: ZOOKEEPER-3829: fix rolling restart when dynamic reconfig is disabled

[GitBox]

symat commented on pull request #1356:
URL: https://github.com/apache/zookeeper/pull/1356#issuecomment-636003458


   Sure, thanks for the tests and the merge! I will create a new PR soon on 3.5 
and also do some manual tests there.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Jenkins build is back to stable : zookeeper-branch36-java11 #198

[Apache Jenkins Server]

See 

Jenkins build is back to normal : zookeeper-master-maven-jdk13 #224

[Apache Jenkins Server]

See 

Jenkins build became unstable: zookeeper-master-maven-jdk-ea #18

[Apache Jenkins Server]

See 

Jenkins build is still unstable: zookeeper-branch36-java8 #199

[Apache Jenkins Server]

See 

Build failed in Jenkins: zookeeper-master-maven-jdk12 #528

[Apache Jenkins Server]

See 


Changes:

[nkalmar] ZOOKEEPER-3829: fix rolling restart when dynamic reconfig is disabled


--
[...truncated 299.55 KB...]
 [exec] Using config: 

 [exec] Stopping zookeeper ... STOPPED
 [exec]  : elapsed 11369 : OK
 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 

 [exec] 
TestReconfigServer::testReconfigFailureWithoutServerSuperuserPasswordConfiguredStarting
 zookeeper ... STARTED
 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 

 [exec] Starting zookeeper ... STARTED
 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 

 [exec] Starting zookeeper ... STARTED
 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 

 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 

 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 

 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 

 [exec] Stopping zookeeper ... STOPPED
 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 

 [exec] Stopping zookeeper ... STOPPED
 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 

 [exec] Stopping zookeeper ... STOPPED
 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 

 [exec] Starting zookeeper ... STARTED
 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 

 [exec] Starting zookeeper ... STARTED
 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 

 [exec] Starting zookeeper ... STARTED
 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 

 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 

 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 

 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 

 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 

 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 

 [exec] ZooKeeper JMX enabled by default
 [exec] Using config: 

Jenkins build became unstable: zookeeper-master-maven-jdk14 #115

[Apache Jenkins Server]

See 

[GitHub] [zookeeper] nkalmar commented on pull request #1356: ZOOKEEPER-3829: fix rolling restart when dynamic reconfig is disabled

[GitBox]

nkalmar commented on pull request #1356:
URL: https://github.com/apache/zookeeper/pull/1356#issuecomment-635960427


   It had 11 conflicting files, tried to merge them but I got a "Segmentation 
fault: 11" error... anyway, it didn't seem a trivial cherry-pick to 3.5, can 
you please create a PR against branch-3.5 @symat ? Merged to master and 3.6. 
Thanks!



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [zookeeper] asfgit closed pull request #1356: ZOOKEEPER-3829: fix rolling restart when dynamic reconfig is disabled

[GitBox]

asfgit closed pull request #1356:
URL: https://github.com/apache/zookeeper/pull/1356


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [zookeeper] samz406 opened a new pull request #1368: Maybe the word is misspelled

[GitBox]

samz406 opened a new pull request #1368:
URL: https://github.com/apache/zookeeper/pull/1368


   Maybe the word is misspelled



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [zookeeper] symat edited a comment on pull request #1356: ZOOKEEPER-3829: backward compatibility fix for rolling restart without dynamic reconfig

[GitBox]

symat edited a comment on pull request #1356:
URL: https://github.com/apache/zookeeper/pull/1356#issuecomment-635796433


   > What I don't understand is what does backward compatibility have to do 
here? 
   
   By backward compatibility I meant that some rolling-restart sequences that 
was working well with 3.4 are not working with 3.5 and 3.6, even if 
`reconfigEnabled=false`. When the dynamic reconfig is disabled, then we would 
assume that rolling-restarts are behaving similarly as they did before 3.5. 
   
   I think you are right, maybe this is a bad phrase here. I will try to make 
it more clear in the PR / Jira. Thanks for the feedback! :)



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [zookeeper] symat commented on pull request #1356: ZOOKEEPER-3829: backward compatibility fix for rolling restart without dynamic reconfig

[GitBox]

symat commented on pull request #1356:
URL: https://github.com/apache/zookeeper/pull/1356#issuecomment-635796433


   > What I don't understand is what does backward compatibility have to do 
here? 
   
   By backward compatibility I meant that some rolling-restart sequences that 
was working well with 3.4 are not working with 3.5 and 3.6, even if 
`reconfigEnabled=false`. When the dynamic reconfig is disabled, then we would 
assume that rolling-restarts are behaving similarly as they did before 3.5. 
   
   I think you are right, maybe this is a bad phrase here. I will try to make 
it more clear in the PR / Jira.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org