ZooKeeper-trunk-WinVS2008 - Build # 2320 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/2320/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 78 lines...] ivy-retrieve: [ivy:retrieve] :: Apache Ivy 2.4.0 - 20141213170938 :: http://ant.apache.org/ivy/ :: [ivy:retrieve] :: loading settings :: file = f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\ivysettings.xml [ivy:retrieve] :: resolving dependencies :: org.apache.zookeeper#zookeeper;3.6.0-SNAPSHOT [ivy:retrieve] confs: [default] [ivy:retrieve] found jline#jline;2.11 in maven2 [ivy:retrieve] found org.eclipse.jetty#jetty-server;9.2.18.v20160721 in maven2 [ivy:retrieve] found javax.servlet#javax.servlet-api;3.1.0 in maven2 [ivy:retrieve] found org.eclipse.jetty#jetty-http;9.2.18.v20160721 in maven2 [ivy:retrieve] found org.eclipse.jetty#jetty-util;9.2.18.v20160721 in maven2 [ivy:retrieve] found org.eclipse.jetty#jetty-io;9.2.18.v20160721 in maven2 [ivy:retrieve] found org.eclipse.jetty#jetty-servlet;9.2.18.v20160721 in maven2 [ivy:retrieve] found org.eclipse.jetty#jetty-security;9.2.18.v20160721 in maven2 [ivy:retrieve] found org.codehaus.jackson#jackson-mapper-asl;1.9.11 in maven2 [ivy:retrieve] found org.codehaus.jackson#jackson-core-asl;1.9.11 in maven2 [ivy:retrieve] found org.slf4j#slf4j-api;1.7.5 in maven2 [ivy:retrieve] found org.slf4j#slf4j-log4j12;1.7.5 in maven2 [ivy:retrieve] found commons-cli#commons-cli;1.2 in maven2 [ivy:retrieve] found log4j#log4j;1.2.17 in maven2 [ivy:retrieve] found io.netty#netty;3.10.5.Final in maven2 [ivy:retrieve] found net.java.dev.javacc#javacc;5.0 in maven2 [ivy:retrieve] :: resolution report :: resolve 623ms :: artifacts dl 46ms - | |modules|| artifacts | | conf | number| search|dwnlded|evicted|| number|dwnlded| - | default | 16 | 0 | 0 | 0 || 16 | 0 | - [ivy:retrieve] :: retrieving :: org.apache.zookeeper#zookeeper [ivy:retrieve] confs: [default] [ivy:retrieve] 16 artifacts copied, 0 already retrieved (4635kB/274ms) generate_jute_parser: [mkdir] Created dir: f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\build\jute_compiler\org\apache\jute\compiler\generated [ivy:artifactproperty] DEPRECATED: 'ivy.conf.file' is deprecated, use 'ivy.settings.file' instead [ivy:artifactproperty] :: loading settings :: file = f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\ivysettings.xml [move] Moving 1 file to f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\build\lib [javacc] Java Compiler Compiler Version 5.0 (Parser Generator) [javacc] (type "javacc" with no arguments for help) [javacc] Reading from file f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\src\java\main\org\apache\jute\compiler\generated\rcc.jj . . . [javacc] File "TokenMgrError.java" does not exist. Will create one. [javacc] File "ParseException.java" does not exist. Will create one. [javacc] File "Token.java" does not exist. Will create one. [javacc] File "SimpleCharStream.java" does not exist. Will create one. [javacc] Parser generated successfully. jute: BUILD FAILED f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\build.xml:273: Unable to find a javac compiler; com.sun.tools.javac.Main is not on the classpath. Perhaps JAVA_HOME does not point to the JDK. It is currently set to "C:\Program Files\Java\jre1.8.0_92" Total time: 4 seconds Build step 'Invoke Ant' marked build as failure Email was triggered for: Failure - Any Sending email for trigger: Failure - Any ### ## FAILED TESTS (if any) ## No tests ran.
Re: [DISCUSS] QA github pre-commit queue
> On 09 Nov 2016, at 10:39, Patrick Hunt wrote: > > What are the implications of moving away from JIRA patches? Any legal/IP? > Also PRs are through github.com, which is not infra owned by Apache. This is supported by infra: https://reference.apache.org/pmc/github > If > that service ever goes away we'll lose that information. Comments on the pull request are currently propagated to the corresponding jira. See for example ZOOKEEPER-1525. > What are other > projects doing in this regard? I'm aware of at least 3 projects: Spark, Kafka, and BookKeeper. > Any impact on our workflows outside of > qabot? e.g. release other other activity tracking? Not that I'm aware of. The only difference if we make this change is that patch available would be set by our script and the script won't look for a patch in the jira. -Flavio > > Patrick > > On Tue, Nov 8, 2016 at 6:37 PM, Flavio P JUNQUEIRA wrote: > >> I don't have any strong argument for keeping the Jira patches other than >> the fact that this is what we have been doing since the project was >> created. If there is anyone who do not want to use github in the community, >> please speak up. >> >> -Flavio >> >> On Mon, Nov 7, 2016 at 9:49 AM, Michael Han wrote: >> >>> +1 for disabling jira qa and only support pull request for code change >>> contributions. Besides making support easier this approach is also >> aligned >>> with what Spark and Kafka is doing, and being consistent across Apache >>> projects regarding how to use PR seems a good thing to do. >>> > have the tool upload the *.patch file to Jira for archiving purposes. >>> I think nothing will prevent a user submit a patch file to JIRA with our >>> script changes, so the functionality of archiving patches will still >> work. >>> Though, I noticed that Kafka [1] and Spark [2] explicitly stated that do >>> not include patch file in JIRA for code contributions, so probably we'd >> do >>> this too for consistency purpose? Are there any benefit of archiving >>> patches given we prefer (or actually require) pull request instead of >>> patches? >>> >>> [1] >>> https://cwiki.apache.org/confluence/display/KAFKA/ >>> Contributing+Code+Changes#ContributingCodeChanges-PullRequest >>> [2] >>> https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark# >>> ContributingtoSpark-PullRequest >>> >>> On Mon, Nov 7, 2016 at 8:04 AM, Edward Ribeiro >> >>> wrote: >>> I am +1 about having patches submitted via PRs. IMHO, we should disable >>> the Jira QA altogether, but have the tool upload the *.patch file to Jira >> for archiving purposes. On Sun, Nov 6, 2016 at 6:42 PM, Raúl Gutiérrez Segalés < r...@itevenworks.net> wrote: > On 6 November 2016 at 11:54, Flavio Junqueira >> wrote: > >> ZOOKEEPER-2624 has been merged, thank Raul, Ben and Michael for > reviewing. >> >> The QA for pull requests should be working for pull requests agains >> master, but let's keep an eye and polish any rough edges that might still >> be there. >> >> With ZOOKEEPER-2624 in, there is one last major decision we need to make >> to wrap this up. The pull request QA currently do not make a jira >>> patch >> available. This is intentional because making it patch available >> will >> trigger the original Jira QA, which will be confusing because we >> will > see a >> failure (I haven't tested, but I think that's what's going to >>> happen). If >> we change the script to make the Jira patch available, then we need >>> to >> either: >> >> 1- Disable the Jira QA altogether, which means that we will only >> have > pull >> request QA available >> 2- Make the Jira QA script spot that there is a pull request >>> available > and >> not build it. >> >> I'm wondering if folks would be ok with only having patches >> submitted via >> pull requests or if we should continue to support the old Jira QA. >> > > I am +1 on only having patches submitted via PRs, it's simpler to >> only have > to support one method. Thanks Flavio for making this happen! > > > -rgs > >>> >>> >>> >>> -- >>> Cheers >>> Michael. >>> >>
ZooKeeper_branch34 - Build # 1715 - Still Failing
See https://builds.apache.org/job/ZooKeeper_branch34/1715/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 1474 lines...] [mkdir] Created dir: /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build/zookeeper-3.4.10-SNAPSHOT/dist-maven [copy] Copying 1 file to /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build/zookeeper-3.4.10-SNAPSHOT/dist-maven [copy] Copying 2 files to /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build/zookeeper-3.4.10-SNAPSHOT/dist-maven [copy] Copying 1 file to /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build/zookeeper-3.4.10-SNAPSHOT/dist-maven [copy] Copying 8 files to /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build/zookeeper-3.4.10-SNAPSHOT/bin [copy] Copying 3 files to /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build/zookeeper-3.4.10-SNAPSHOT/conf [copy] Copying 318 files to /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build/zookeeper-3.4.10-SNAPSHOT/docs [copy] Copied 22 empty directories to 3 empty directories under /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build/zookeeper-3.4.10-SNAPSHOT/docs [copy] Copying 8 files to /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build/zookeeper-3.4.10-SNAPSHOT [copy] Copying 918 files to /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build/zookeeper-3.4.10-SNAPSHOT/src [copy] Copied 238 empty directories to 1 empty directory under /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build/zookeeper-3.4.10-SNAPSHOT/src tar: [tar] Building tar: /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build/zookeeper-3.4.10-SNAPSHOT.tar.gz check-for-findbugs: findbugs: BUILD FAILED /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build.xml:1481: java.lang.UnsupportedClassVersionError: edu/umd/cs/findbugs/anttask/FindBugsTask : Unsupported major.minor version 51.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) at java.lang.ClassLoader.defineClass(ClassLoader.java:615) at org.apache.tools.ant.AntClassLoader.defineClassFromData(AntClassLoader.java:1149) at org.apache.tools.ant.AntClassLoader.getClassFromStream(AntClassLoader.java:1320) at org.apache.tools.ant.AntClassLoader.findClassInComponents(AntClassLoader.java:1376) at org.apache.tools.ant.AntClassLoader.findClass(AntClassLoader.java:1337) at org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1089) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:249) at org.apache.tools.ant.taskdefs.Definer.addDefinition(Definer.java:579) at org.apache.tools.ant.taskdefs.Definer.execute(Definer.java:237) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:435) at org.apache.tools.ant.Target.performTasks(Target.java:456) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1405) at org.apache.tools.ant.Project.executeTarget(Project.java:1376) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1260) at org.apache.tools.ant.Main.runBuild(Main.java:854) at org.apache.tools.ant.Main.startAnt(Main.java:236) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:285) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:112) Total time: 56 seconds mv: cannot stat 'build/test/findbugs': No such file or directory Build Failed Build step 'Execute shell' marked build as failure Recording test results ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? Email was triggered for: Failure - Any Sending email for trigger: Failure - Any ### ## FAILED TESTS (if any) ## No tests ran.
[jira] [Commented] (ZOOKEEPER-2628) Investigate and fix findbug warnings
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651880#comment-15651880 ] ASF GitHub Bot commented on ZOOKEEPER-2628: --- Github user lvfangmin commented on a diff in the pull request: https://github.com/apache/zookeeper/pull/102#discussion_r87265113 --- Diff: src/java/main/org/apache/zookeeper/server/command/FourLetterCommands.java --- @@ -151,9 +153,13 @@ */ public final static int telnetCloseCmd = 0xfff4fffd; -public final static HashMap cmd2String = +final static HashMap cmd2String = --- End diff -- Same here, we can also define this as Map to keep consistent with the others. > Investigate and fix findbug warnings > > > Key: ZOOKEEPER-2628 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2628 > Project: ZooKeeper > Issue Type: Bug >Affects Versions: 3.5.2 >Reporter: Michael Han > Fix For: 3.5.3 > > > Findbug tool used by Jenkins bot is upgraded to 3.0.1 from 2.0.3 according to > Infra team, and this leads to 20 new warnings produced by findbug. The > warning reports can be found on [pre commit > builds|https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/] with build > number >= 3513. These warnings need to be triaged and fixed if they are > legitimate. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2628) Investigate and fix findbug warnings
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651881#comment-15651881
]
ASF GitHub Bot commented on ZOOKEEPER-2628:
---
Github user lvfangmin commented on a diff in the pull request:
https://github.com/apache/zookeeper/pull/102#discussion_r87264725
--- Diff: src/java/main/org/apache/zookeeper/server/DataTree.java ---
@@ -1293,13 +1293,12 @@ public synchronized WatchesSummary
getWatchesSummary() {
* @param pwriter the output to write to
*/
public void dumpEphemerals(PrintWriter pwriter) {
-Set keys = ephemerals.keySet();
pwriter.println("Sessions with Ephemerals ("
-+ keys.size() + "):");
-for (long k : keys) {
-pwriter.print("0x" + Long.toHexString(k));
++ ephemerals.keySet().size() + "):");
+for (Entry> entry : ephemerals.entrySet()) {
+pwriter.print("0x" + Long.toHexString(entry.getKey()));
pwriter.println(":");
-HashSet tmp = ephemerals.get(k);
+HashSet tmp = entry.getValue();
--- End diff --
Usually, prefer to use the interface if we only use the methods defined in
the interface, which makes it flexible (or less change needed) in case we want
to use another Set implementation.
There is a best practice defined in Effective Java 2nd Edition, Item 52:
Refer to objects by their interfaces:
If appropriate interface types exist, then parameters, return values, and
fields should all be declared using interface types. If you get into the habit
of using interface types, your program will be much more flexible. It is
entirely appropriate to refer to an object by a class if no appropriate
interface exists.
> Investigate and fix findbug warnings
>
>
> Key: ZOOKEEPER-2628
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2628
> Project: ZooKeeper
> Issue Type: Bug
>Affects Versions: 3.5.2
>Reporter: Michael Han
> Fix For: 3.5.3
>
>
> Findbug tool used by Jenkins bot is upgraded to 3.0.1 from 2.0.3 according to
> Infra team, and this leads to 20 new warnings produced by findbug. The
> warning reports can be found on [pre commit
> builds|https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/] with build
> number >= 3513. These warnings need to be triaged and fixed if they are
> legitimate.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] zookeeper pull request #102: ZOOKEEPER-2628: Fix findbug warnings.
Github user lvfangmin commented on a diff in the pull request:
https://github.com/apache/zookeeper/pull/102#discussion_r87264725
--- Diff: src/java/main/org/apache/zookeeper/server/DataTree.java ---
@@ -1293,13 +1293,12 @@ public synchronized WatchesSummary
getWatchesSummary() {
* @param pwriter the output to write to
*/
public void dumpEphemerals(PrintWriter pwriter) {
-Set keys = ephemerals.keySet();
pwriter.println("Sessions with Ephemerals ("
-+ keys.size() + "):");
-for (long k : keys) {
-pwriter.print("0x" + Long.toHexString(k));
++ ephemerals.keySet().size() + "):");
+for (Entry> entry : ephemerals.entrySet()) {
+pwriter.print("0x" + Long.toHexString(entry.getKey()));
pwriter.println(":");
-HashSet tmp = ephemerals.get(k);
+HashSet tmp = entry.getValue();
--- End diff --
Usually, prefer to use the interface if we only use the methods defined in
the interface, which makes it flexible (or less change needed) in case we want
to use another Set implementation.
There is a best practice defined in Effective Java 2nd Edition, Item 52:
Refer to objects by their interfaces:
If appropriate interface types exist, then parameters, return values, and
fields should all be declared using interface types. If you get into the habit
of using interface types, your program will be much more flexible. It is
entirely appropriate to refer to an object by a class if no appropriate
interface exists.
---
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 pull request #102: ZOOKEEPER-2628: Fix findbug warnings.
Github user lvfangmin commented on a diff in the pull request: https://github.com/apache/zookeeper/pull/102#discussion_r87265113 --- Diff: src/java/main/org/apache/zookeeper/server/command/FourLetterCommands.java --- @@ -151,9 +153,13 @@ */ public final static int telnetCloseCmd = 0xfff4fffd; -public final static HashMap cmd2String = +final static HashMap cmd2String = --- End diff -- Same here, we can also define this as Map to keep consistent with the others. --- 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-openjdk7 - Build # 1233 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1233/
###
## LAST 60 LINES OF THE CONSOLE
###
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H17 (ubuntu) in workspace
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-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/master^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 440e0923dd9e3be533a196fdd6ada960860ca7f6
(refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 440e0923dd9e3be533a196fdd6ada960860ca7f6
> git rev-list 440e0923dd9e3be533a196fdd6ada960860ca7f6 # timeout=10
No emails were triggered.
[ZooKeeper-trunk-openjdk7] $ /home/jenkins/tools/ant/latest/bin/ant
-Dtest.output=yes -Dtest.junit.threads=8 -Dtest.junit.output.format=xml
-Djavac.target=1.7 clean test-core-java
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.
Re: [VOTE] move Apache Zookeeper to git
Hi Patrick, We can change the script so that it asks for jira password input on CLI prompt if the JIRA username is set, for example. The change should be straigthforward. Alternatively, the python systems I have dealt with put credentials for database access, etc, in configuration -- sometimes hidden -- files (say, .env), but yet it is clear text stored. Anyone has other suggestions? Eddie Em 9 de nov de 2016 4:18 PM, "Patrick Hunt" escreveu: > Is there any alternative to step 4 as documented here? > https://cwiki.apache.org/confluence/display/ZOOKEEPER/ > Merging+Github+Pull+Requests > > specifically it's asking to "export JIRA_PASSWORD=mypassword" which I feel > very uncomfortable doing. > > Patrick > > On Wed, Oct 26, 2016 at 11:12 AM, Edward Ribeiro > > wrote: > > > AFAIK, yes. I say, if you mean to run unit tests and other CI tasks on > PR. > > > > PS: I have just created a simple script HowTo at > > https://cwiki.apache.org/confluence/display/ZOOKEEPER/ > > Merging+Github+Pull+Requests > > and linked from https://cwiki.apache.org/confluence/display/ZOOKEEPER/ > > Index > > > > On Wed, Oct 26, 2016 at 3:59 PM, Flavio Junqueira > wrote: > > > > > What about QA, are we still missing a github pre-commit queue? > > > > > > -Flavio > > > > > > > On 26 Oct 2016, at 18:53, Michael Han wrote: > > > > > > > > The comment bridging should be fixed now - see INFRA-12752 for more > > > > details. > > > > > > > > On Wed, Oct 26, 2016 at 10:03 AM, Michael Han > > wrote: > > > > > > > The git PR *review* comments for ZOOKEEPER-2597 didn't show up on > > > JIRA. > > > >> > > > >> The bridge was working the day Infra made the change - see the > > previous > > > >> comments made by git bot on ZOOKEEPER-761. Now it seems stop > working. > > I > > > am > > > >> reopening INFRA-12752 and building a case. > > > >> > > > >> On Wed, Oct 26, 2016 at 9:45 AM, Edward Ribeiro < > > > edward.ribe...@gmail.com> > > > >> wrote: > > > >> > > > >>> Dear community, > > > >>> > > > >>> The zk-merger-pr.py script has been merged into master (thanks a > LOT > > > Ben > > > >>> Reed for reviewing/discussing/testing and commiting): > > > >>> https://issues.apache.org/jira/browse/ZOOKEEPER-2597 > > > >>> > > > >>> As stated in the issue and on GH, this tool is a modified version > of > > > >>> similar tools from Kafka, that is a copy of a Spark's one. It has > > some > > > >>> rough edges so we will certainly benefit from further enhancements > > and > > > >>> fixes. I changed the smallest possible pieces of code, just to make > > it > > > >>> work > > > >>> on a ZK repo so the credits go to the original authors. > > > >>> > > > >>> Some notes: > > > >>> > > > >>> 1. The git PR *review* comments for ZOOKEEPER-2597 didn't show up > on > > > JIRA. > > > >>> Only the opening and closing of the issue. Can we double check this > > as > > > >>> INFRA-12752 is closed, Michael Han? > > > >>> > > > >>> 2. I scribbled a draft on how use the tool at > > > >>> https://docs.google.com/document/d/1i00ZXjrW2fu17vr_h7F1bUrq > > > >>> Xg3urw4Hm7KirQDpPIU/edit > > > >>> (still very crude, but feel free to improve it). I would like to > move > > > >>> this > > > >>> text to https://cwiki.apache.org/confluence/display/ZOOKEEPER/ > Index > > > but > > > >>> looks like I don't have permission to create a page there yet. Any > > > help? > > > >>> > > > >>> Best regards, > > > >>> Eddie > > > >>> > > > >>> On Sat, Oct 22, 2016 at 7:08 PM, Michael Han > > > wrote: > > > >>> > > > FYI infra did some work in INFRA-12752 and the git PR comments can > > be > > > pushed to Apache JIRA. > > > > > > On Sat, Oct 8, 2016 at 8:01 AM, Flavio Junqueira > > > >>> wrote: > > > > > > > This is not supported at the moment if nothing has changed: > > > > > > > > https://issues.apache.org/jira/browse/INFRA-11000 < > > > > https://issues.apache.org/jira/browse/INFRA-11000> > > > > > > > > -Flavio > > > > > > > >> On 08 Oct 2016, at 00:54, Benjamin Reed > wrote: > > > >> > > > >> it doesn't look like we need to setup keys. this seems to work > for > > > >>> me: > > > >> > > > >> https://git-wip-us.apache.org/#committers-getting-started > > > >> > > > >> it does seem strange that we aren't using public keys and that > i'm > > > > sticking > > > >> a password in .netrc :P i'm wondering if other projects were > able > > to > > > get > > > >> this going over ssh. > > > >> > > > >> i'll take a whack at cleaning up the svn and subversion > > references. > > > >> > > > >> ben > > > >> > > > >> On Fri, Oct 7, 2016 at 12:59 PM, Camille Fournier < > > > >>> cami...@apache.org> > > > >> wrote: > > > >> > > > >>> Hey folks, > > > >>> > > > >>> So I'm trying to get in a patch but this has not been updated > to > > > >>> tell > > > >>> committers how to actually get the git keys set up: > > > >>> https://cwiki.apache.org/confluence/d
[jira] [Commented] (ZOOKEEPER-761) Remove *synchronous* calls from the *single-threaded* C clieant API, since they are documented not to work
[
https://issues.apache.org/jira/browse/ZOOKEEPER-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651712#comment-15651712
]
Patrick Hunt commented on ZOOKEEPER-761:
bq. we should deprecate the single threaded API altogether. what do others
think?
I know of a number of users who use the single thread apis, they provide
flexibility for integrating into third party code that may or may not be able
to use threads (for whatever reason).
> Remove *synchronous* calls from the *single-threaded* C clieant API, since
> they are documented not to work
> --
>
> Key: ZOOKEEPER-761
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-761
> Project: ZooKeeper
> Issue Type: Improvement
> Components: c client
>Affects Versions: 3.1.1, 3.2.2
> Environment: RHEL 4u8 (Linux). The issue is not OS-specific though.
>Reporter: Jozef Hatala
>Assignee: Benjamin Reed
>Priority: Minor
> Fix For: 3.5.3, 3.6.0
>
> Attachments: fix-sync-apis-in-st-adaptor.patch,
> fix-sync-apis-in-st-adaptor.v2.patch
>
>
> Since the synchronous calls are
> [known|http://hadoop.apache.org/zookeeper/docs/current/zookeeperProgrammers.html#Using+the+C+Client]
> to be unimplemented in the single threaded version of the client library
> libzookeeper_st.so, I believe that it would be helpful towards users of the
> library if that information was also obvious from the header file.
> Anecdotally more than one of us here made the mistake of starting by using
> the synchronous calls with the single-threaded library, and we found
> ourselves debugging it. An early warning would have been greatly appreciated.
> 1. Could you please add warnings to the doxygen blocks of all synchronous
> calls saying that they are not available in the single-threaded API. This
> cannot be safely done with {{#ifdef THREADED}}, obviously, because the same
> header file is included whichever client library implementation one is
> compiling for.
> 2. Could you please bracket the implementation of all synchronous calls in
> zookeeper.c with {{#ifdef THREADED}} and {{#endif}}, so that those symbols
> are not present in libzookeeper_st.so?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [DISCUSS] QA github pre-commit queue
What are the implications of moving away from JIRA patches? Any legal/IP? Also PRs are through github.com, which is not infra owned by Apache. If that service ever goes away we'll lose that information. What are other projects doing in this regard? Any impact on our workflows outside of qabot? e.g. release other other activity tracking? Patrick On Tue, Nov 8, 2016 at 6:37 PM, Flavio P JUNQUEIRA wrote: > I don't have any strong argument for keeping the Jira patches other than > the fact that this is what we have been doing since the project was > created. If there is anyone who do not want to use github in the community, > please speak up. > > -Flavio > > On Mon, Nov 7, 2016 at 9:49 AM, Michael Han wrote: > > > +1 for disabling jira qa and only support pull request for code change > > contributions. Besides making support easier this approach is also > aligned > > with what Spark and Kafka is doing, and being consistent across Apache > > projects regarding how to use PR seems a good thing to do. > > > > >> have the tool upload the *.patch file to Jira for archiving purposes. > > I think nothing will prevent a user submit a patch file to JIRA with our > > script changes, so the functionality of archiving patches will still > work. > > Though, I noticed that Kafka [1] and Spark [2] explicitly stated that do > > not include patch file in JIRA for code contributions, so probably we'd > do > > this too for consistency purpose? Are there any benefit of archiving > > patches given we prefer (or actually require) pull request instead of > > patches? > > > > [1] > > https://cwiki.apache.org/confluence/display/KAFKA/ > > Contributing+Code+Changes#ContributingCodeChanges-PullRequest > > [2] > > https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark# > > ContributingtoSpark-PullRequest > > > > On Mon, Nov 7, 2016 at 8:04 AM, Edward Ribeiro > > > wrote: > > > > > I am +1 about having patches submitted via PRs. IMHO, we should disable > > the > > > Jira QA altogether, but have the tool upload the *.patch file to Jira > for > > > archiving purposes. > > > > > > On Sun, Nov 6, 2016 at 6:42 PM, Raúl Gutiérrez Segalés < > > > r...@itevenworks.net> > > > wrote: > > > > > > > On 6 November 2016 at 11:54, Flavio Junqueira > wrote: > > > > > > > > > ZOOKEEPER-2624 has been merged, thank Raul, Ben and Michael for > > > > reviewing. > > > > > > > > > > The QA for pull requests should be working for pull requests agains > > > > > master, but let's keep an eye and polish any rough edges that might > > > still > > > > > be there. > > > > > > > > > > With ZOOKEEPER-2624 in, there is one last major decision we need to > > > make > > > > > to wrap this up. The pull request QA currently do not make a jira > > patch > > > > > available. This is intentional because making it patch available > will > > > > > trigger the original Jira QA, which will be confusing because we > will > > > > see a > > > > > failure (I haven't tested, but I think that's what's going to > > happen). > > > If > > > > > we change the script to make the Jira patch available, then we need > > to > > > > > either: > > > > > > > > > > 1- Disable the Jira QA altogether, which means that we will only > have > > > > pull > > > > > request QA available > > > > > 2- Make the Jira QA script spot that there is a pull request > > available > > > > and > > > > > not build it. > > > > > > > > > > I'm wondering if folks would be ok with only having patches > submitted > > > via > > > > > pull requests or if we should continue to support the old Jira QA. > > > > > > > > > > > > > I am +1 on only having patches submitted via PRs, it's simpler to > only > > > have > > > > to support one method. Thanks Flavio for making this happen! > > > > > > > > > > > > -rgs > > > > > > > > > > > > > > > -- > > Cheers > > Michael. > > >
[jira] [Commented] (ZOOKEEPER-1525) Plumb ZooKeeperServer object into auth plugins
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651659#comment-15651659 ] ASF GitHub Bot commented on ZOOKEEPER-1525: --- Github user lvfangmin commented on the issue: https://github.com/apache/zookeeper/pull/84 Generally looks good to me, but I have the same concern as @fpj, maybe in the future the newly added auth needs additional parameters, then we have to add another wrapper with new interface to keep the old ones backward compatible. I also agree a general metadata map is error-prone, but I think we can have a compromise solution between explicit parameters and general metadata map: Create a class (e.g. AuthData) with the explicit parameters(zks, cnxn, path, perm, setAcls) in it, which has the get and set method, and use this class in the newly added ServerAuthenticationProvider interface. In the future if we need additional parameter, we only need to change this class, no interface and backward compatible issues will be involved. What do you think @Randgalt @fpj? > Plumb ZooKeeperServer object into auth plugins > -- > > Key: ZOOKEEPER-1525 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1525 > Project: ZooKeeper > Issue Type: Improvement >Affects Versions: 3.5.0 >Reporter: Warren Turkal >Assignee: Jordan Zimmerman > Fix For: 3.5.3, 3.6.0 > > Attachments: ZOOKEEPER-1525.patch, ZOOKEEPER-1525.patch, > ZOOKEEPER-1525.patch, ZOOKEEPER-1525.patch, ZOOKEEPER-1525.patch, > ZOOKEEPER-1525.patch, ZOOKEEPER-1525.patch, ZOOKEEPER-1525.patch, > ZOOKEEPER-1525.patch, ZOOKEEPER-1525.patch > > > I want to plumb the ZooKeeperServer object into the auth plugins so that I > can store authentication data in zookeeper itself. With access to the > ZooKeeperServer object, I also have access to the ZKDatabase and can look up > entries in the local copy of the zookeeper data. > In order to implement this, I make sure that a ZooKeeperServer instance is > passed in to the ProviderRegistry.initialize() method. Then initialize() will > try to find a constructor for the AuthenticationProvider that takes a > ZooKeeperServer instance. If the constructor is found, it will be used. > Otherwise, initialize() will look for a constructor that takes no arguments > and use that instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] zookeeper issue #84: [ZOOKEEPER-1525] Plumb ZooKeeperServer object into auth...
Github user lvfangmin commented on the issue: https://github.com/apache/zookeeper/pull/84 Generally looks good to me, but I have the same concern as @fpj, maybe in the future the newly added auth needs additional parameters, then we have to add another wrapper with new interface to keep the old ones backward compatible. I also agree a general metadata map is error-prone, but I think we can have a compromise solution between explicit parameters and general metadata map: Create a class (e.g. AuthData) with the explicit parameters(zks, cnxn, path, perm, setAcls) in it, which has the get and set method, and use this class in the newly added ServerAuthenticationProvider interface. In the future if we need additional parameter, we only need to change this class, no interface and backward compatible issues will be involved. What do you think @Randgalt @fpj? --- 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. ---
Re: [VOTE] move Apache Zookeeper to git
Is there any alternative to step 4 as documented here? https://cwiki.apache.org/confluence/display/ZOOKEEPER/Merging+Github+Pull+Requests specifically it's asking to "export JIRA_PASSWORD=mypassword" which I feel very uncomfortable doing. Patrick On Wed, Oct 26, 2016 at 11:12 AM, Edward Ribeiro wrote: > AFAIK, yes. I say, if you mean to run unit tests and other CI tasks on PR. > > PS: I have just created a simple script HowTo at > https://cwiki.apache.org/confluence/display/ZOOKEEPER/ > Merging+Github+Pull+Requests > and linked from https://cwiki.apache.org/confluence/display/ZOOKEEPER/ > Index > > On Wed, Oct 26, 2016 at 3:59 PM, Flavio Junqueira wrote: > > > What about QA, are we still missing a github pre-commit queue? > > > > -Flavio > > > > > On 26 Oct 2016, at 18:53, Michael Han wrote: > > > > > > The comment bridging should be fixed now - see INFRA-12752 for more > > > details. > > > > > > On Wed, Oct 26, 2016 at 10:03 AM, Michael Han > wrote: > > > > > The git PR *review* comments for ZOOKEEPER-2597 didn't show up on > > JIRA. > > >> > > >> The bridge was working the day Infra made the change - see the > previous > > >> comments made by git bot on ZOOKEEPER-761. Now it seems stop working. > I > > am > > >> reopening INFRA-12752 and building a case. > > >> > > >> On Wed, Oct 26, 2016 at 9:45 AM, Edward Ribeiro < > > edward.ribe...@gmail.com> > > >> wrote: > > >> > > >>> Dear community, > > >>> > > >>> The zk-merger-pr.py script has been merged into master (thanks a LOT > > Ben > > >>> Reed for reviewing/discussing/testing and commiting): > > >>> https://issues.apache.org/jira/browse/ZOOKEEPER-2597 > > >>> > > >>> As stated in the issue and on GH, this tool is a modified version of > > >>> similar tools from Kafka, that is a copy of a Spark's one. It has > some > > >>> rough edges so we will certainly benefit from further enhancements > and > > >>> fixes. I changed the smallest possible pieces of code, just to make > it > > >>> work > > >>> on a ZK repo so the credits go to the original authors. > > >>> > > >>> Some notes: > > >>> > > >>> 1. The git PR *review* comments for ZOOKEEPER-2597 didn't show up on > > JIRA. > > >>> Only the opening and closing of the issue. Can we double check this > as > > >>> INFRA-12752 is closed, Michael Han? > > >>> > > >>> 2. I scribbled a draft on how use the tool at > > >>> https://docs.google.com/document/d/1i00ZXjrW2fu17vr_h7F1bUrq > > >>> Xg3urw4Hm7KirQDpPIU/edit > > >>> (still very crude, but feel free to improve it). I would like to move > > >>> this > > >>> text to https://cwiki.apache.org/confluence/display/ZOOKEEPER/Index > > but > > >>> looks like I don't have permission to create a page there yet. Any > > help? > > >>> > > >>> Best regards, > > >>> Eddie > > >>> > > >>> On Sat, Oct 22, 2016 at 7:08 PM, Michael Han > > wrote: > > >>> > > FYI infra did some work in INFRA-12752 and the git PR comments can > be > > pushed to Apache JIRA. > > > > On Sat, Oct 8, 2016 at 8:01 AM, Flavio Junqueira > > >>> wrote: > > > > > This is not supported at the moment if nothing has changed: > > > > > > https://issues.apache.org/jira/browse/INFRA-11000 < > > > https://issues.apache.org/jira/browse/INFRA-11000> > > > > > > -Flavio > > > > > >> On 08 Oct 2016, at 00:54, Benjamin Reed wrote: > > >> > > >> it doesn't look like we need to setup keys. this seems to work for > > >>> me: > > >> > > >> https://git-wip-us.apache.org/#committers-getting-started > > >> > > >> it does seem strange that we aren't using public keys and that i'm > > > sticking > > >> a password in .netrc :P i'm wondering if other projects were able > to > > get > > >> this going over ssh. > > >> > > >> i'll take a whack at cleaning up the svn and subversion > references. > > >> > > >> ben > > >> > > >> On Fri, Oct 7, 2016 at 12:59 PM, Camille Fournier < > > >>> cami...@apache.org> > > >> wrote: > > >> > > >>> Hey folks, > > >>> > > >>> So I'm trying to get in a patch but this has not been updated to > > >>> tell > > >>> committers how to actually get the git keys set up: > > >>> https://cwiki.apache.org/confluence/display/ZOOKEEPER/ > > > Committing+changes > > >>> > > >>> Can someone float me a link that says how to do this? > > >>> > > >>> Also a bunch of our documentation still discusses SVN and not > git, > > which > > >>> means we are not done with this migration. If you were pushing > for > > this > > >>> change can you please do some due diligence on the wikis and > > >>> correct > > the > > >>> stuff that refers to SVN? > > >>> > > >>> Thanks, > > >>> C > > >>> > > >>> On Wed, Oct 5, 2016 at 1:02 PM, Edward Ribeiro < > > > edward.ribe...@gmail.com> > > >>> wrote: > > >>> > > Excuse me guys! > > > > I've written on Macbook Pro. No ide
ZooKeeper_branch35_solaris - Build # 311 - Still Failing
See https://builds.apache.org/job/ZooKeeper_branch35_solaris/311/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 437739 lines...] [junit] 2016-11-09 17:16:38,156 [myid:] - INFO [main:ClientBase@386] - CREATING server instance 127.0.0.1:11222 [junit] 2016-11-09 17:16:38,157 [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] 2016-11-09 17:16:38,157 [myid:] - INFO [main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222 [junit] 2016-11-09 17:16:38,158 [myid:] - INFO [main:ClientBase@361] - STARTING server instance 127.0.0.1:11222 [junit] 2016-11-09 17:16:38,158 [myid:] - INFO [main:ZooKeeperServer@889] - minSessionTimeout set to 6000 [junit] 2016-11-09 17:16:38,158 [myid:] - INFO [main:ZooKeeperServer@898] - maxSessionTimeout set to 6 [junit] 2016-11-09 17:16:38,159 [myid:] - INFO [main:ZooKeeperServer@159] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/build/test/tmp/test7944631555632926050.junit.dir/version-2 snapdir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/build/test/tmp/test7944631555632926050.junit.dir/version-2 [junit] 2016-11-09 17:16:38,159 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/build/test/tmp/test7944631555632926050.junit.dir/version-2/snapshot.b [junit] 2016-11-09 17:16:38,161 [myid:] - INFO [main:FileTxnSnapLog@306] - Snapshotting: 0xb to /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/build/test/tmp/test7944631555632926050.junit.dir/version-2/snapshot.b [junit] 2016-11-09 17:16:38,163 [myid:] - ERROR [main:ZooKeeperServer@501] - ZKShutdownHandler is not registered, so ZooKeeper server won't take any action on ERROR or SHUTDOWN server state changes [junit] 2016-11-09 17:16:38,163 [myid:] - INFO [main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222 [junit] 2016-11-09 17:16:38,163 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:35856 [junit] 2016-11-09 17:16:38,164 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from /127.0.0.1:35856 [junit] 2016-11-09 17:16:38,164 [myid:] - INFO [NIOWorkerThread-1:StatCommand@49] - Stat command output [junit] 2016-11-09 17:16:38,164 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client /127.0.0.1:35856 (no session established for client) [junit] 2016-11-09 17:16:38,165 [myid:] - INFO [main:JMXEnv@228] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2016-11-09 17:16:38,166 [myid:] - INFO [main:JMXEnv@245] - expect:InMemoryDataTree [junit] 2016-11-09 17:16:38,166 [myid:] - INFO [main:JMXEnv@249] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree [junit] 2016-11-09 17:16:38,167 [myid:] - INFO [main:JMXEnv@245] - expect:StandaloneServer_port [junit] 2016-11-09 17:16:38,167 [myid:] - INFO [main:JMXEnv@249] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11222 [junit] 2016-11-09 17:16:38,167 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17683 [junit] 2016-11-09 17:16:38,167 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24 [junit] 2016-11-09 17:16:38,167 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD testQuota [junit] 2016-11-09 17:16:38,167 [myid:] - INFO [main:ClientBase@543] - tearDown starting [junit] 2016-11-09 17:16:38,242 [myid:] - INFO [main:ZooKeeper@1313] - Session: 0x124c711e32f closed [junit] 2016-11-09 17:16:38,242 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for session: 0x124c711e32f [junit] 2016-11-09 17:16:38,242 [myid:] - INFO [main:ClientBase@513] - STOPPING server [junit] 2016-11-09 17:16:38,243 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2016-11-09 17:16:38,243 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@219] - accept thread exitted run method [junit] 2016-11-09 17:16:38,243 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$Se
ZooKeeper_branch34_solaris - Build # 1352 - Failure
See https://builds.apache.org/job/ZooKeeper_branch34_solaris/1352/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 180603 lines...] [junit] 2016-11-09 13:51:06,040 [myid:] - INFO [main:ZooKeeperServer@497] - shutting down [junit] 2016-11-09 13:51:06,040 [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] 2016-11-09 13:51:06,040 [myid:] - INFO [main:SessionTrackerImpl@225] - Shutting down [junit] 2016-11-09 13:51:06,040 [myid:] - INFO [main:PrepRequestProcessor@765] - Shutting down [junit] 2016-11-09 13:51:06,041 [myid:] - INFO [main:SyncRequestProcessor@208] - Shutting down [junit] 2016-11-09 13:51:06,041 [myid:] - INFO [ProcessThread(sid:0 cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop! [junit] 2016-11-09 13:51:06,041 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited! [junit] 2016-11-09 13:51:06,041 [myid:] - INFO [main:FinalRequestProcessor@402] - shutdown of request processor complete [junit] 2016-11-09 13:51:06,042 [myid:] - INFO [main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221 [junit] 2016-11-09 13:51:06,042 [myid:] - INFO [main:JMXEnv@146] - ensureOnly:[] [junit] 2016-11-09 13:51:06,043 [myid:] - INFO [main:ClientBase@445] - STARTING server [junit] 2016-11-09 13:51:06,043 [myid:] - INFO [main:ClientBase@366] - CREATING server instance 127.0.0.1:11221 [junit] 2016-11-09 13:51:06,044 [myid:] - INFO [main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2016-11-09 13:51:06,044 [myid:] - INFO [main:ClientBase@341] - STARTING server instance 127.0.0.1:11221 [junit] 2016-11-09 13:51:06,045 [myid:] - INFO [main:ZooKeeperServer@173] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/build/test/tmp/test1015655834503549030.junit.dir/version-2 snapdir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/build/test/tmp/test1015655834503549030.junit.dir/version-2 [junit] 2016-11-09 13:51:06,048 [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] 2016-11-09 13:51:06,049 [myid:] - INFO [main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221 [junit] 2016-11-09 13:51:06,049 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - Accepted socket connection from /127.0.0.1:51270 [junit] 2016-11-09 13:51:06,049 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing stat command from /127.0.0.1:51270 [junit] 2016-11-09 13:51:06,050 [myid:] - INFO [Thread-5:NIOServerCnxn$StatCommand@663] - Stat command output [junit] 2016-11-09 13:51:06,050 [myid:] - INFO [Thread-5:NIOServerCnxn@1008] - Closed socket connection for client /127.0.0.1:51270 (no session established for client) [junit] 2016-11-09 13:51:06,050 [myid:] - INFO [main:JMXEnv@229] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2016-11-09 13:51:06,052 [myid:] - INFO [main:JMXEnv@246] - expect:InMemoryDataTree [junit] 2016-11-09 13:51:06,052 [myid:] - INFO [main:JMXEnv@250] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree [junit] 2016-11-09 13:51:06,052 [myid:] - INFO [main:JMXEnv@246] - expect:StandaloneServer_port [junit] 2016-11-09 13:51:06,052 [myid:] - INFO [main:JMXEnv@250] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11221 [junit] 2016-11-09 13:51:06,052 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 8837 [junit] 2016-11-09 13:51:06,053 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 19 [junit] 2016-11-09 13:51:06,053 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota [junit] 2016-11-09 13:51:06,053 [myid:] - INFO [main:ClientBase@522] - tearDown starting [junit] 2016-11-09 13:51:06,262 [myid:] - INFO [main:ZooKeeper@684] - Session: 0x158495b38a6 closed [junit] 2016-11-09 13:51:06,262 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for session: 0x158495b38a6 [junit] 2016-11-09 13:51:06,262 [myid:] - INFO [main:ClientBase@492] - STOPPING server [junit] 2016-11-09 13:51:06,263 [myid:] - INFO [main:ZooKeeperServer@497] - shutting down [junit] 2016-11-09 13:51:06,263 [myid:] - E
ZooKeeper_branch35_jdk8 - Build # 294 - Failure
See https://builds.apache.org/job/ZooKeeper_branch35_jdk8/294/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 458263 lines...] [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214) [junit] 2016-11-09 12:15:54,344 [myid:127.0.0.1:22118] - INFO [main-SendThread(127.0.0.1:22118):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:22118. Will not attempt to authenticate using SASL (unknown error) [junit] 2016-11-09 12:15:54,345 [myid:127.0.0.1:22118] - WARN [main-SendThread(127.0.0.1:22118):ClientCnxn$SendThread@1235] - Session 0x2018ed2e97e for server 127.0.0.1/127.0.0.1:22118, 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] 2016-11-09 12:15:54,797 [myid:127.0.0.1:21994] - INFO [main-SendThread(127.0.0.1:21994):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:21994. Will not attempt to authenticate using SASL (unknown error) [junit] 2016-11-09 12:15:54,798 [myid:127.0.0.1:21994] - WARN [main-SendThread(127.0.0.1:21994):ClientCnxn$SendThread@1235] - Session 0x1018ecf68bb for server 127.0.0.1/127.0.0.1:21994, 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] 2016-11-09 12:15:55,119 [myid:127.0.0.1:22115] - INFO [main-SendThread(127.0.0.1:22115):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:22115. Will not attempt to authenticate using SASL (unknown error) [junit] 2016-11-09 12:15:55,120 [myid:127.0.0.1:22115] - WARN [main-SendThread(127.0.0.1:22115):ClientCnxn$SendThread@1235] - Session 0x1018ed2e980 for server 127.0.0.1/127.0.0.1:22115, 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] 2016-11-09 12:15:55,159 [myid:] - INFO [ProcessThread(sid:0 cport:22238)::PrepRequestProcessor@647] - Processed session termination for sessionid: 0x1018ed5acd9 [junit] 2016-11-09 12:15:55,161 [myid:] - INFO [main:ZooKeeper@1313] - Session: 0x1018ed5acd9 closed [junit] 2016-11-09 12:15:55,161 [myid:] - INFO [SessionTracker:SessionTrackerImpl@158] - SessionTrackerImpl exited loop! [junit] 2016-11-09 12:15:55,161 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 107914 [junit] 2016-11-09 12:15:55,161 [myid:] - INFO [SyncThread:0:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port22238,name1=Connections,name2=127.0.0.1,name3=0x1018ed5acd9] [junit] 2016-11-09 12:15:55,161 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for session: 0x1018ed5acd9 [junit] 2016-11-09 12:15:55,161 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 468 [junit] 2016-11-09 12:15:55,161 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD testWatcherAutoResetWithLocal [junit] 2016-11-09 12:15:55,161 [myid:] - INFO [main:ClientBase@543] - tearDown starting [junit] 2016-11-09 12:15:55,162 [myid:] - INFO [main:ClientBase@513] - STOPPING server [junit] 2016-11-09 12:15:55,162 [myid:] - INFO [main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:22238 [junit] 2016-11-09 12:15:55,163 [myid:] - INFO [main:ZooKeeperServer@529] - shutting down [junit] 2016-11-09 12:15:55,163 [myid:] - ERROR [main:ZooKeeperServer@501] - ZKShutdownHandler is not registered, so ZooKeeper server won't take any action on ERROR or SHUTDOWN server state changes [
ZooKeeper_branch35_openjdk7 - Build # 291 - Still Failing
See https://builds.apache.org/job/ZooKeeper_branch35_openjdk7/291/
###
## LAST 60 LINES OF THE CONSOLE
###
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H16 (ubuntu) in workspace
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_openjdk7
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url git://git.apache.org/zookeeper.git # timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
> git --version # timeout=10
> git -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.5^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/branch-3.5^{commit} # timeout=10
Checking out Revision 6bd38e3d89ecc03285459be3e511d32f487ced0c
(refs/remotes/origin/branch-3.5)
> git config core.sparsecheckout # timeout=10
> git checkout -f 6bd38e3d89ecc03285459be3e511d32f487ced0c
> git rev-list 6bd38e3d89ecc03285459be3e511d32f487ced0c # timeout=10
No emails were triggered.
[ZooKeeper_branch35_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.
ZooKeeper-trunk-solaris - Build # 1378 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-solaris/1378/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 439297 lines...] [junit] 2016-11-09 08:20:30,779 [myid:] - INFO [main:ClientBase@386] - CREATING server instance 127.0.0.1:11222 [junit] 2016-11-09 08:20:30,779 [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] 2016-11-09 08:20:30,780 [myid:] - INFO [main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222 [junit] 2016-11-09 08:20:30,780 [myid:] - INFO [main:ClientBase@361] - STARTING server instance 127.0.0.1:11222 [junit] 2016-11-09 08:20:30,781 [myid:] - INFO [main:ZooKeeperServer@889] - minSessionTimeout set to 6000 [junit] 2016-11-09 08:20:30,781 [myid:] - INFO [main:ZooKeeperServer@898] - maxSessionTimeout set to 6 [junit] 2016-11-09 08:20:30,781 [myid:] - INFO [main:ZooKeeperServer@159] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test1012091823661749529.junit.dir/version-2 snapdir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test1012091823661749529.junit.dir/version-2 [junit] 2016-11-09 08:20:30,782 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test1012091823661749529.junit.dir/version-2/snapshot.b [junit] 2016-11-09 08:20:30,784 [myid:] - INFO [main:FileTxnSnapLog@306] - Snapshotting: 0xb to /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test1012091823661749529.junit.dir/version-2/snapshot.b [junit] 2016-11-09 08:20:30,785 [myid:] - ERROR [main:ZooKeeperServer@501] - ZKShutdownHandler is not registered, so ZooKeeper server won't take any action on ERROR or SHUTDOWN server state changes [junit] 2016-11-09 08:20:30,785 [myid:] - INFO [main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222 [junit] 2016-11-09 08:20:30,786 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:43904 [junit] 2016-11-09 08:20:30,786 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from /127.0.0.1:43904 [junit] 2016-11-09 08:20:30,787 [myid:] - INFO [NIOWorkerThread-1:StatCommand@49] - Stat command output [junit] 2016-11-09 08:20:30,787 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client /127.0.0.1:43904 (no session established for client) [junit] 2016-11-09 08:20:30,787 [myid:] - INFO [main:JMXEnv@228] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2016-11-09 08:20:30,788 [myid:] - INFO [main:JMXEnv@245] - expect:InMemoryDataTree [junit] 2016-11-09 08:20:30,789 [myid:] - INFO [main:JMXEnv@249] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree [junit] 2016-11-09 08:20:30,789 [myid:] - INFO [main:JMXEnv@245] - expect:StandaloneServer_port [junit] 2016-11-09 08:20:30,789 [myid:] - INFO [main:JMXEnv@249] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11222 [junit] 2016-11-09 08:20:30,789 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17666 [junit] 2016-11-09 08:20:30,789 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24 [junit] 2016-11-09 08:20:30,789 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD testQuota [junit] 2016-11-09 08:20:30,790 [myid:] - INFO [main:ClientBase@543] - tearDown starting [junit] 2016-11-09 08:20:30,832 [myid:] - INFO [main:ZooKeeper@1315] - Session: 0x124c5270fc3 closed [junit] 2016-11-09 08:20:30,832 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for session: 0x124c5270fc3 [junit] 2016-11-09 08:20:30,832 [myid:] - INFO [main:ClientBase@513] - STOPPING server [junit] 2016-11-09 08:20:30,832 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@219] - accept thread exitted run method [junit] 2016-11-09 08:20:30,832 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2016-11-09 08:20:30,832 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@4
