Stuck Zookeeper-trunk build
Zookeeper trunk build seem to be stuck: hudson 21455 0.0 0.2 1202248 44484 ? S
Apache hudson build machine
Hello, There seem to be an issue with the nfs mount on the apache build servers from h1.grid.sp2.yahoo.net Most of the hudson slaves went offline. I'm workin with the ops to bring the hudson slaves h[1-9] back online. Thanks, Giri
Sendmail restartd for patch process
Folks, It looks like sendmail process on hudson.zones crashed and all the test patch jobs submitted in the last two days didn't get through. Please resubmit your patch to the test-patch job. -Giri
Re: Sendmail restarted for patch process
Jira_cli is still not able to post comments on to jira. Asfinfra is notified of this, they are working on it,. Thanks, Giri On 13/04/10 11:42 AM, "Giridharan Kesavan" wrote: Folks, It looks like sendmail process on hudson.zones crashed and all the test patch jobs submitted in the last two days didn't get through. Please resubmit your patch to the test-patch job. -Giri
zookeeper patch builds.
Zookeeper patch admin jobs running on hudson.zones are failing, as hudson.zones is running out of space. I 've sent an email to the apache infrastructure team. Once I get an update I would restart the zookeeper-patch builds. Thanks, Giri
RE: zookeeper patch builds.
Hi Patrick, I've restarted the patch builds for zookeeper as the space issue seem to be resolved. Thanks, Giri > -Original Message- > From: Patrick Hunt [mailto:ph...@apache.org] > Sent: Thursday, July 30, 2009 11:03 AM > To: zookeeper-dev@hadoop.apache.org > Cc: Nigel Daley > Subject: Re: zookeeper patch builds. > > Hi Giri, any update on this? Has infra been able to resolve the space > issue? > > Thanks! > > Parick > > Giridharan Kesavan wrote: > > Zookeeper patch admin jobs running on hudson.zones are failing, as > > > > hudson.zones is running out of space. > > > > I 've sent an email to the apache infrastructure team. > > > > > > > > Once I get an update I would restart the zookeeper-patch builds. > > > > > > > > Thanks, > > > > Giri > > > >
hudson patch build back to normal
Sendmail issues on hudson.zones is fixed now and patch build for zookeeper is restarted. Regards, Giri
RE: hudson patch build back to normal
If you have changed the jira status to patch available in the last couple of days please resubmit your patch for hudson to pick your patch for testing. -Giri > -Original Message- > From: Giridharan Kesavan [mailto:gkesa...@yahoo-inc.com] > Sent: Wednesday, August 05, 2009 7:18 PM > To: zookeeper-dev@hadoop.apache.org > Cc: Nigel Daley > Subject: hudson patch build back to normal > > Sendmail issues on hudson.zones is fixed now and patch build for > zookeeper is restarted. > > Regards, > Giri
build failures on hudson zones
Build on hudson.zones are failing as the zonestorage for hudson is full. I 've sent an email to the ASF infra team about the space issues on hudson zones. Once the issues is resolved I would restart hudson for builds. Thanks, Giri
BUILDS ARE BACK NORMAL
Restarted all the build jobs on hudson; Builds are running fine. Build failures are due to " /tmp: File system full, swap space limit exceeded " Thanks, -Giri > -Original Message- > From: Giridharan Kesavan [mailto:gkesa...@yahoo-inc.com] > Sent: Thursday, August 06, 2009 9:16 AM > To: mapreduce-...@hadoop.apache.org; hdfs-...@hadoop.apache.org; > common-...@hadoop.apache.org; pig-...@hadoop.apache.org; zookeeper- > d...@hadoop.apache.org > Subject: build failures on hudson zones > > Build on hudson.zones are failing as the zonestorage for hudson is > full. > I 've sent an email to the ASF infra team about the space issues on > hudson zones. > > Once the issues is resolved I would restart hudson for builds. > > Thanks, > Giri >
zookeeper trunk build
Zookeeper trunk build is now moved from vesta.apache.org to a h8.grid.sp2.yahoo.net machine Tnx Giri
[jira] Commented: (ZOOKEEPER-618) hudson not reporting failures correctly
[ https://issues.apache.org/jira/browse/ZOOKEEPER-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789430#action_12789430 ] Giridharan Kesavan commented on ZOOKEEPER-618: -- Patrick, I dont see Quorum test failure in the console o/p of the build that you have mentioned.. Is 612 the build that you are talkin about? > hudson not reporting failures correctly > --- > > Key: ZOOKEEPER-618 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-618 > Project: Zookeeper > Issue Type: Bug > Components: tests >Affects Versions: 3.3.0 >Reporter: Patrick Hunt > Assignee: Giridharan Kesavan >Priority: Critical > > See > http://hudson.zones.apache.org/hudson/view/ZooKeeper/job/ZooKeeper-trunk/612/ > this test failed however there is no indication in the hudson page why it > failed. > Looking at the raw console output I see > [junit] Running org.apache.zookeeper.test.QuorumTest > [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec > [junit] Test org.apache.zookeeper.test.QuorumTest FAILED (timeout) > So it seems there is an error in hudson reporting. > Giri can you look into this? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ZOOKEEPER-621) hudson failure ZooKeeper-trunk/621 - clover issue
[ https://issues.apache.org/jira/browse/ZOOKEEPER-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan resolved ZOOKEEPER-621. -- Resolution: Fixed cleaning /tmp fs helped. > hudson failure ZooKeeper-trunk/621 - clover issue > - > > Key: ZOOKEEPER-621 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-621 > Project: Zookeeper > Issue Type: Bug > Components: build >Reporter: Patrick Hunt > Assignee: Giridharan Kesavan >Priority: Critical > Fix For: 3.3.0 > > > Giri can you take a look? Any recent changes on hudson that could have caused > this? > http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/621/ > jute: > [javac] Compiling 38 source files to > /grid/0/hudson/hudson-slave/workspace/ZooKeeper-trunk/trunk/build/classes >[clover] Clover Version 2.4.3, built on March 09 2009 (build-756) >[clover] Loaded from: /homes/hudson/tools/clover/latest/lib/clover.jar >[clover] Clover: Open Source License registered to Apache. >[clover] Failed to create temp directory >[clover] ** Error(s) occurred and the instrumentation process can't > continue. > BUILD FAILED > /grid/0/hudson/hudson-slave/workspace/ZooKeeper-trunk/trunk/build.xml:879: > The following error occurred while executing this line: > /grid/0/hudson/hudson-slave/workspace/ZooKeeper-trunk/trunk/build.xml:199: > com.cenqua.clover.CloverException: Failed to create temp directory -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-618) hudson not reporting failures correctly
[ https://issues.apache.org/jira/browse/ZOOKEEPER-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790779#action_12790779 ] Giridharan Kesavan commented on ZOOKEEPER-618: -- we need to configure our builds to generate cppunit test report so that hudson can parse and upload > hudson not reporting failures correctly > --- > > Key: ZOOKEEPER-618 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-618 > Project: Zookeeper > Issue Type: Bug > Components: tests >Affects Versions: 3.3.0 >Reporter: Patrick Hunt > Assignee: Giridharan Kesavan >Priority: Critical > > See > http://hudson.zones.apache.org/hudson/view/ZooKeeper/job/ZooKeeper-trunk/612/ > this test failed however there is no indication in the hudson page why it > failed. > Looking at the raw console output I see > [junit] Running org.apache.zookeeper.test.QuorumTest > [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec > [junit] Test org.apache.zookeeper.test.QuorumTest FAILED (timeout) > So it seems there is an error in hudson reporting. > Giri can you look into this? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-625) configure/change build scripts to generate cppunit reports
configure/change build scripts to generate cppunit reports -- Key: ZOOKEEPER-625 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-625 Project: Zookeeper Issue Type: Improvement Components: build Reporter: Giridharan Kesavan -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-618) hudson not reporting failures correctly
[ https://issues.apache.org/jira/browse/ZOOKEEPER-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790785#action_12790785 ] Giridharan Kesavan commented on ZOOKEEPER-618: -- https://issues.apache.org/jira/browse/ZOOKEEPER-625 - created a new jira for changing build script to parse cppunit test reports. > hudson not reporting failures correctly > --- > > Key: ZOOKEEPER-618 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-618 > Project: Zookeeper > Issue Type: Bug > Components: tests >Affects Versions: 3.3.0 >Reporter: Patrick Hunt > Assignee: Giridharan Kesavan >Priority: Critical > > See > http://hudson.zones.apache.org/hudson/view/ZooKeeper/job/ZooKeeper-trunk/612/ > this test failed however there is no indication in the hudson page why it > failed. > Looking at the raw console output I see > [junit] Running org.apache.zookeeper.test.QuorumTest > [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec > [junit] Test org.apache.zookeeper.test.QuorumTest FAILED (timeout) > So it seems there is an error in hudson reporting. > Giri can you look into this? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ZOOKEEPER-618) hudson not reporting failures correctly
[ https://issues.apache.org/jira/browse/ZOOKEEPER-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan resolved ZOOKEEPER-618. -- Resolution: Invalid > hudson not reporting failures correctly > --- > > Key: ZOOKEEPER-618 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-618 > Project: Zookeeper > Issue Type: Bug > Components: tests >Affects Versions: 3.3.0 >Reporter: Patrick Hunt > Assignee: Giridharan Kesavan >Priority: Critical > > See > http://hudson.zones.apache.org/hudson/view/ZooKeeper/job/ZooKeeper-trunk/612/ > this test failed however there is no indication in the hudson page why it > failed. > Looking at the raw console output I see > [junit] Running org.apache.zookeeper.test.QuorumTest > [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec > [junit] Test org.apache.zookeeper.test.QuorumTest FAILED (timeout) > So it seems there is an error in hudson reporting. > Giri can you look into this? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ZOOKEEPER-633) Fetch netty using ivy for bookkeeper
[
https://issues.apache.org/jira/browse/ZOOKEEPER-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giridharan Kesavan reassigned ZOOKEEPER-633:
Assignee: Giridharan Kesavan
> Fetch netty using ivy for bookkeeper
>
>
> Key: ZOOKEEPER-633
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-633
> Project: Zookeeper
> Issue Type: Improvement
> Components: contrib-bookkeeper
>Reporter: Flavio Paiva Junqueira
> Assignee: Giridharan Kesavan
> Fix For: 3.3.0
>
>
> The patch of ZOOKEEPER-507 requires netty and to compile we now have to
> manually add the netty jar to {project root}/src/java/lib. GIven that we
> bookkeeper already fetches junit and log4j using ivy, we could also do it for
> netty. However, we need to configure it to fetch from a different repository.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-633) Fetch netty using ivy for bookkeeper
[
https://issues.apache.org/jira/browse/ZOOKEEPER-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giridharan Kesavan updated ZOOKEEPER-633:
-
Attachment: zookeeper-633.patch
This patch adds a new ivyconfiguration file called ivysettings.xml which has
the details of the resolver.
This new resolver would resolve dependencies from the jboss maven repo when the
central maven repo
doesn't have the required artifact.
> Fetch netty using ivy for bookkeeper
>
>
> Key: ZOOKEEPER-633
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-633
> Project: Zookeeper
> Issue Type: Improvement
> Components: contrib-bookkeeper
>Reporter: Flavio Paiva Junqueira
> Assignee: Giridharan Kesavan
> Fix For: 3.3.0
>
> Attachments: zookeeper-633.patch
>
>
> The patch of ZOOKEEPER-507 requires netty and to compile we now have to
> manually add the netty jar to {project root}/src/java/lib. GIven that we
> bookkeeper already fetches junit and log4j using ivy, we could also do it for
> netty. However, we need to configure it to fetch from a different repository.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-633) Fetch netty using ivy for bookkeeper
[
https://issues.apache.org/jira/browse/ZOOKEEPER-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giridharan Kesavan updated ZOOKEEPER-633:
-
Attachment: zookeeper-633.patch
this patch fixes the DEPRECATED warning message.
tnx
> Fetch netty using ivy for bookkeeper
>
>
> Key: ZOOKEEPER-633
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-633
> Project: Zookeeper
> Issue Type: Improvement
> Components: contrib-bookkeeper
>Reporter: Flavio Paiva Junqueira
> Assignee: Giridharan Kesavan
> Fix For: 3.3.0
>
> Attachments: zookeeper-633.patch, zookeeper-633.patch,
> zookeeper-633.patch
>
>
> The patch of ZOOKEEPER-507 requires netty and to compile we now have to
> manually add the netty jar to {project root}/src/java/lib. GIven that we
> bookkeeper already fetches junit and log4j using ivy, we could also do it for
> netty. However, we need to configure it to fetch from a different repository.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-648) Fix releaseaudit warning count to zero
Fix releaseaudit warning count to zero -- Key: ZOOKEEPER-648 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-648 Project: Zookeeper Issue Type: Improvement Components: build Reporter: Giridharan Kesavan ant releaseaudit -Dforrest.home=<> -Djava5.home=<> 200 unknown license should be updated with Apache License headers releaseaudit: [java] [java] * [java] Summary [java] --- [java] Notes: 57 [java] Binaries: 95 [java] Archives: 16 [java] Standards: 954 [java] [java] Apache Licensed: 610 [java] Generated Documents: 144 [java] [java] JavaDocs are generated and so license header is optional [java] Generated files do not required license headers [java] [java] 200 Unknown Licenses [java] [java] *** -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ZOOKEEPER-620) hudson is not reporting compiler warning correctly
[ https://issues.apache.org/jira/browse/ZOOKEEPER-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan resolved ZOOKEEPER-620. -- Resolution: Fixed > hudson is not reporting compiler warning correctly > -- > > Key: ZOOKEEPER-620 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-620 > Project: Zookeeper > Issue Type: Bug > Components: tests >Affects Versions: 3.3.0 >Reporter: Patrick Hunt > Assignee: Giridharan Kesavan > Fix For: 3.3.0 > > > http://hudson.zones.apache.org/hudson/view/ZooKeeper/job/ZooKeeper-trunk/590/warningsResult/HIGH/ > If you click on any of these links you will see that these are not compiler > warnings: > http://hudson.zones.apache.org/hudson/view/ZooKeeper/job/ZooKeeper-trunk/590/warningsResult/HIGH/file.-1602148846/ > Giri can you take a look at these and resolve? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-620) hudson is not reporting compiler warning correctly
[ https://issues.apache.org/jira/browse/ZOOKEEPER-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802185#action_12802185 ] Giridharan Kesavan commented on ZOOKEEPER-620: -- hudson compiler warnings plubing is now configured with javadoc and java compiler parsers http://hudson.zones.apache.org/hudson/view/ZooKeeper/job/ZooKeeper-trunk/671 > hudson is not reporting compiler warning correctly > -- > > Key: ZOOKEEPER-620 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-620 > Project: Zookeeper > Issue Type: Bug > Components: tests >Affects Versions: 3.3.0 >Reporter: Patrick Hunt > Assignee: Giridharan Kesavan > Fix For: 3.3.0 > > > http://hudson.zones.apache.org/hudson/view/ZooKeeper/job/ZooKeeper-trunk/590/warningsResult/HIGH/ > If you click on any of these links you will see that these are not compiler > warnings: > http://hudson.zones.apache.org/hudson/view/ZooKeeper/job/ZooKeeper-trunk/590/warningsResult/HIGH/file.-1602148846/ > Giri can you take a look at these and resolve? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-648) Fix releaseaudit warning count to zero
[ https://issues.apache.org/jira/browse/ZOOKEEPER-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802644#action_12802644 ] Giridharan Kesavan commented on ZOOKEEPER-648: -- there are about 200 files without Apache License(AL) header. This jira is filed to fix the releaseaudit warnings by adding Apache License headers or by excluding files to which AL headers cant be added. mapreduce-847 can be used an example. > Fix releaseaudit warning count to zero > -- > > Key: ZOOKEEPER-648 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-648 > Project: Zookeeper > Issue Type: Improvement > Components: build > Reporter: Giridharan Kesavan >Priority: Critical > Fix For: 3.3.0 > > > ant releaseaudit -Dforrest.home=<> -Djava5.home=<> > 200 unknown license should be updated with Apache License headers > releaseaudit: > [java] > [java] * > [java] Summary > [java] --- > [java] Notes: 57 > [java] Binaries: 95 > [java] Archives: 16 > [java] Standards: 954 > [java] > [java] Apache Licensed: 610 > [java] Generated Documents: 144 > [java] > [java] JavaDocs are generated and so license header is optional > [java] Generated files do not required license headers > [java] > [java] 200 Unknown Licenses > [java] > [java] *** -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-224) Deploy ZooKeeper jars/artifacts to a Maven Repository
[ https://issues.apache.org/jira/browse/ZOOKEEPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802645#action_12802645 ] Giridharan Kesavan commented on ZOOKEEPER-224: -- Recently, I 've uploaded a patch for hadoop-20 branch which uses maven-ant-task which signs artifacts using gpg and publishes them to the staging or snapshot repository based on the arguments passed. https://issues.apache.org/jira/browse/hadoop-6382 > Deploy ZooKeeper jars/artifacts to a Maven Repository > - > > Key: ZOOKEEPER-224 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-224 > Project: Zookeeper > Issue Type: Task > Components: build >Affects Versions: 3.0.0 >Reporter: Hiram Chirino >Assignee: Patrick Hunt >Priority: Critical > Fix For: 3.3.0 > > > I've created the maven poms needed for the 3.0.0 release. > The directory structure and artifacts located at: > http://people.apache.org/~chirino/zk-repo/ > aka > people.apache.org:/x1/users/chirino/public_html/zk-repo > Just need sto get GPG signed by the project KEY and deployed to: > people.apache.org:/www/people.apache.org/repo/m2-ibiblio-rsync-repository > Who's the current ZooKeeper release manager? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-844) handle auth failure in java client
[
https://issues.apache.org/jira/browse/ZOOKEEPER-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giridharan Kesavan updated ZOOKEEPER-844:
-
Status: Patch Available (was: Open)
> handle auth failure in java client
> --
>
> Key: ZOOKEEPER-844
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-844
> Project: Zookeeper
> Issue Type: Improvement
> Components: java client
>Affects Versions: 3.3.1
>Reporter: Camille Fournier
>Assignee: Camille Fournier
> Fix For: 3.4.0
>
> Attachments: ZOOKEEPER-844.patch
>
>
> ClientCnxn.java currently has the following code:
> if (replyHdr.getXid() == -4) {
> // -2 is the xid for AuthPacket
> // TODO: process AuthPacket here
> if (LOG.isDebugEnabled()) {
> LOG.debug("Got auth sessionid:0x"
> + Long.toHexString(sessionId));
> }
> return;
> }
> Auth failures appear to cause the server to disconnect but the client never
> gets a proper state change or notification that auth has failed, which makes
> handling this scenario very difficult as it causes the client to go into a
> loop of sending bad auth, getting disconnected, trying to reconnect, sending
> bad auth again, over and over.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-844) handle auth failure in java client
[
https://issues.apache.org/jira/browse/ZOOKEEPER-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giridharan Kesavan updated ZOOKEEPER-844:
-
Status: Open (was: Patch Available)
submitting to hudson
> handle auth failure in java client
> --
>
> Key: ZOOKEEPER-844
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-844
> Project: Zookeeper
> Issue Type: Improvement
> Components: java client
>Affects Versions: 3.3.1
>Reporter: Camille Fournier
>Assignee: Camille Fournier
> Fix For: 3.4.0
>
> Attachments: ZOOKEEPER-844.patch
>
>
> ClientCnxn.java currently has the following code:
> if (replyHdr.getXid() == -4) {
> // -2 is the xid for AuthPacket
> // TODO: process AuthPacket here
> if (LOG.isDebugEnabled()) {
> LOG.debug("Got auth sessionid:0x"
> + Long.toHexString(sessionId));
> }
> return;
> }
> Auth failures appear to cause the server to disconnect but the client never
> gets a proper state change or notification that auth has failed, which makes
> handling this scenario very difficult as it causes the client to go into a
> loop of sending bad auth, getting disconnected, trying to reconnect, sending
> bad auth again, over and over.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-780) zkCli.sh generates a ArrayIndexOutOfBoundsException
[ https://issues.apache.org/jira/browse/ZOOKEEPER-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-780: - Status: Open (was: Patch Available) > zkCli.sh generates a ArrayIndexOutOfBoundsException > - > > Key: ZOOKEEPER-780 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-780 > Project: Zookeeper > Issue Type: Bug > Components: scripts >Affects Versions: 3.3.1 > Environment: Linux Ubuntu running in VMPlayer on top of Windows XP >Reporter: Miguel Correia >Assignee: Andrei Savu >Priority: Minor > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-780.patch, ZOOKEEPER-780.patch, > ZOOKEEPER-780.patch > > > I'm starting to play with Zookeeper so I'm still running it in standalone > mode. This is not a big issue, but here it goes for the records. > I've run zkCli.sh to run some commands in the server. I created a znode > /groups. When I tried to create a znode client_1 inside /groups, I forgot to > include the data: an exception was generated and zkCli-sh crashed, instead of > just showing an error. I tried a few variations and it seems like the problem > is not including the data. > A copy of the screen: > [zk: localhost:2181(CONNECTED) 3] create /groups firstgroup > Created /groups > [zk: localhost:2181(CONNECTED) 4] create -e /groups/client_1 > Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 3 > at > org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:678) > at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:581) > at > org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:353) > at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:311) > at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:270) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-780) zkCli.sh generates a ArrayIndexOutOfBoundsException
[ https://issues.apache.org/jira/browse/ZOOKEEPER-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-780: - Status: Patch Available (was: Open) re-submiting to hudson > zkCli.sh generates a ArrayIndexOutOfBoundsException > - > > Key: ZOOKEEPER-780 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-780 > Project: Zookeeper > Issue Type: Bug > Components: scripts >Affects Versions: 3.3.1 > Environment: Linux Ubuntu running in VMPlayer on top of Windows XP >Reporter: Miguel Correia >Assignee: Andrei Savu >Priority: Minor > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-780.patch, ZOOKEEPER-780.patch, > ZOOKEEPER-780.patch > > > I'm starting to play with Zookeeper so I'm still running it in standalone > mode. This is not a big issue, but here it goes for the records. > I've run zkCli.sh to run some commands in the server. I created a znode > /groups. When I tried to create a znode client_1 inside /groups, I forgot to > include the data: an exception was generated and zkCli-sh crashed, instead of > just showing an error. I tried a few variations and it seems like the problem > is not including the data. > A copy of the screen: > [zk: localhost:2181(CONNECTED) 3] create /groups firstgroup > Created /groups > [zk: localhost:2181(CONNECTED) 4] create -e /groups/client_1 > Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 3 > at > org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:678) > at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:581) > at > org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:353) > at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:311) > at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:270) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-780) zkCli.sh generates a ArrayIndexOutOfBoundsException
[ https://issues.apache.org/jira/browse/ZOOKEEPER-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-780: - Status: Open (was: Patch Available) > zkCli.sh generates a ArrayIndexOutOfBoundsException > - > > Key: ZOOKEEPER-780 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-780 > Project: Zookeeper > Issue Type: Bug > Components: scripts >Affects Versions: 3.3.1 > Environment: Linux Ubuntu running in VMPlayer on top of Windows XP >Reporter: Miguel Correia >Assignee: Andrei Savu >Priority: Minor > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-780.patch, ZOOKEEPER-780.patch, > ZOOKEEPER-780.patch > > > I'm starting to play with Zookeeper so I'm still running it in standalone > mode. This is not a big issue, but here it goes for the records. > I've run zkCli.sh to run some commands in the server. I created a znode > /groups. When I tried to create a znode client_1 inside /groups, I forgot to > include the data: an exception was generated and zkCli-sh crashed, instead of > just showing an error. I tried a few variations and it seems like the problem > is not including the data. > A copy of the screen: > [zk: localhost:2181(CONNECTED) 3] create /groups firstgroup > Created /groups > [zk: localhost:2181(CONNECTED) 4] create -e /groups/client_1 > Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 3 > at > org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:678) > at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:581) > at > org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:353) > at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:311) > at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:270) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-780) zkCli.sh generates a ArrayIndexOutOfBoundsException
[ https://issues.apache.org/jira/browse/ZOOKEEPER-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-780: - Status: Patch Available (was: Open) > zkCli.sh generates a ArrayIndexOutOfBoundsException > - > > Key: ZOOKEEPER-780 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-780 > Project: Zookeeper > Issue Type: Bug > Components: scripts >Affects Versions: 3.3.1 > Environment: Linux Ubuntu running in VMPlayer on top of Windows XP >Reporter: Miguel Correia >Assignee: Andrei Savu >Priority: Minor > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-780.patch, ZOOKEEPER-780.patch, > ZOOKEEPER-780.patch > > > I'm starting to play with Zookeeper so I'm still running it in standalone > mode. This is not a big issue, but here it goes for the records. > I've run zkCli.sh to run some commands in the server. I created a znode > /groups. When I tried to create a znode client_1 inside /groups, I forgot to > include the data: an exception was generated and zkCli-sh crashed, instead of > just showing an error. I tried a few variations and it seems like the problem > is not including the data. > A copy of the screen: > [zk: localhost:2181(CONNECTED) 3] create /groups firstgroup > Created /groups > [zk: localhost:2181(CONNECTED) 4] create -e /groups/client_1 > Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 3 > at > org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:678) > at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:581) > at > org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:353) > at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:311) > at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:270) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-756) some cleanup and improvements for zooinspector
[ https://issues.apache.org/jira/browse/ZOOKEEPER-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-756: - Status: Open (was: Patch Available) re-submiting to hudson > some cleanup and improvements for zooinspector > -- > > Key: ZOOKEEPER-756 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-756 > Project: Zookeeper > Issue Type: Improvement > Components: contrib >Affects Versions: 3.3.0 >Reporter: Thomas Koch >Assignee: Colin Goodheart-Smithe > Fix For: 3.4.0 > > Attachments: zooInspectorChanges.patch > > > Copied from the already closed ZOOKEEPER-678: > * specify the exact URL, where the icons are from. It's best to include the > link also in the NOTICE.txt file. > It seems, that zooinspector finds it's icons only if the icons folder is in > the current path. But when I install zooinspector as part of the Zookeeper > Debian package, I want to be able to call it regardless of the current path. > Could you use getRessources or something so that I can point to the icons > location from the wrapper shell script? > Can I place the zooinspector config files in /etc/zookeeper/zooinspector/ ? > Could I give zooinspector a property to point to the config file location? > There are several places, where viewers is missspelled as "Veiwers". Please > do a case insensitive search for "veiw" to correct these. Even the config > file "defaultNodeVeiwers.cfg" is missspelled like this. This has the > potential to confuse the hell out of people when debugging something! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-844) handle auth failure in java client
[
https://issues.apache.org/jira/browse/ZOOKEEPER-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giridharan Kesavan updated ZOOKEEPER-844:
-
Status: Open (was: Patch Available)
> handle auth failure in java client
> --
>
> Key: ZOOKEEPER-844
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-844
> Project: Zookeeper
> Issue Type: Bug
> Components: java client
>Affects Versions: 3.3.1
>Reporter: Camille Fournier
>Assignee: Camille Fournier
> Fix For: 3.3.2, 3.4.0
>
> Attachments: ZOOKEEPER-844.patch, ZOOKEEPER332-844
>
>
> ClientCnxn.java currently has the following code:
> if (replyHdr.getXid() == -4) {
> // -2 is the xid for AuthPacket
> // TODO: process AuthPacket here
> if (LOG.isDebugEnabled()) {
> LOG.debug("Got auth sessionid:0x"
> + Long.toHexString(sessionId));
> }
> return;
> }
> Auth failures appear to cause the server to disconnect but the client never
> gets a proper state change or notification that auth has failed, which makes
> handling this scenario very difficult as it causes the client to go into a
> loop of sending bad auth, getting disconnected, trying to reconnect, sending
> bad auth again, over and over.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-756) some cleanup and improvements for zooinspector
[ https://issues.apache.org/jira/browse/ZOOKEEPER-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-756: - Status: Patch Available (was: Open) > some cleanup and improvements for zooinspector > -- > > Key: ZOOKEEPER-756 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-756 > Project: Zookeeper > Issue Type: Improvement > Components: contrib >Affects Versions: 3.3.0 >Reporter: Thomas Koch >Assignee: Colin Goodheart-Smithe > Fix For: 3.4.0 > > Attachments: zooInspectorChanges.patch > > > Copied from the already closed ZOOKEEPER-678: > * specify the exact URL, where the icons are from. It's best to include the > link also in the NOTICE.txt file. > It seems, that zooinspector finds it's icons only if the icons folder is in > the current path. But when I install zooinspector as part of the Zookeeper > Debian package, I want to be able to call it regardless of the current path. > Could you use getRessources or something so that I can point to the icons > location from the wrapper shell script? > Can I place the zooinspector config files in /etc/zookeeper/zooinspector/ ? > Could I give zooinspector a property to point to the config file location? > There are several places, where viewers is missspelled as "Veiwers". Please > do a case insensitive search for "veiw" to correct these. Even the config > file "defaultNodeVeiwers.cfg" is missspelled like this. This has the > potential to confuse the hell out of people when debugging something! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-844) handle auth failure in java client
[
https://issues.apache.org/jira/browse/ZOOKEEPER-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giridharan Kesavan updated ZOOKEEPER-844:
-
Status: Patch Available (was: Open)
> handle auth failure in java client
> --
>
> Key: ZOOKEEPER-844
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-844
> Project: Zookeeper
> Issue Type: Bug
> Components: java client
>Affects Versions: 3.3.1
>Reporter: Camille Fournier
>Assignee: Camille Fournier
> Fix For: 3.3.2, 3.4.0
>
> Attachments: ZOOKEEPER-844.patch, ZOOKEEPER332-844
>
>
> ClientCnxn.java currently has the following code:
> if (replyHdr.getXid() == -4) {
> // -2 is the xid for AuthPacket
> // TODO: process AuthPacket here
> if (LOG.isDebugEnabled()) {
> LOG.debug("Got auth sessionid:0x"
> + Long.toHexString(sessionId));
> }
> return;
> }
> Auth failures appear to cause the server to disconnect but the client never
> gets a proper state change or notification that auth has failed, which makes
> handling this scenario very difficult as it causes the client to go into a
> loop of sending bad auth, getting disconnected, trying to reconnect, sending
> bad auth again, over and over.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ZOOKEEPER-60) Get cppunit tests running as part of Hudson CI
[ https://issues.apache.org/jira/browse/ZOOKEEPER-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan reassigned ZOOKEEPER-60: --- Assignee: Giridharan Kesavan > Get cppunit tests running as part of Hudson CI > -- > > Key: ZOOKEEPER-60 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-60 > Project: Zookeeper > Issue Type: Improvement > Components: build >Reporter: Patrick Hunt > Assignee: Giridharan Kesavan > > Investigate if it is possible to run cppunit tests as part of Hudson. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-60) Get cppunit tests running as part of Hudson CI
[ https://issues.apache.org/jira/browse/ZOOKEEPER-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-60: Attachment: ZK-60.patch this patch adds couple of ant target's to execute the cppunit tests.. To execute the cppunit test use ant create-configure-cppunit test-cppunit -Dcppunit=true create-configure-cppunit target runs the autoreconf and test-cppunit executes the test. Please review tnx! > Get cppunit tests running as part of Hudson CI > -- > > Key: ZOOKEEPER-60 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-60 > Project: Zookeeper > Issue Type: Improvement > Components: build >Reporter: Patrick Hunt > Assignee: Giridharan Kesavan > Attachments: ZK-60.patch > > > Investigate if it is possible to run cppunit tests as part of Hudson. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-60) Get cppunit tests running as part of Hudson CI
[ https://issues.apache.org/jira/browse/ZOOKEEPER-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689004#action_12689004 ] Giridharan Kesavan commented on ZOOKEEPER-60: - I hardly changed anything in the Makefile.am so it should work with the same set of env variables set in the build.xml > Get cppunit tests running as part of Hudson CI > -- > > Key: ZOOKEEPER-60 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-60 > Project: Zookeeper > Issue Type: Improvement > Components: build >Reporter: Patrick Hunt > Assignee: Giridharan Kesavan > Attachments: ZK-60.patch > > > Investigate if it is possible to run cppunit tests as part of Hudson. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-60) Get cppunit tests running as part of Hudson CI
[ https://issues.apache.org/jira/browse/ZOOKEEPER-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-60: Attachment: ZK-60.patch Here is the patch which addresses the comments added by Patrick Renamed the zkServer.sh to tests-zkServer.sh, hence the conflict with zkServer.sh in the bin folder is avoided. Also restored the compile_jute check in the configure.ac by introducing a flag. If user wants to run tests directly from the src/c folder they have to export PATH variable as fuser binary is not available in the users path. (fuser binary sits in the /sbin dir). so adding tests folder to the path may not an overhead. > Get cppunit tests running as part of Hudson CI > -- > > Key: ZOOKEEPER-60 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-60 > Project: Zookeeper > Issue Type: Improvement > Components: build >Reporter: Patrick Hunt > Assignee: Giridharan Kesavan > Attachments: ZK-60.patch, ZK-60.patch > > > Investigate if it is possible to run cppunit tests as part of Hudson. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-60) Get cppunit tests running as part of Hudson CI
[ https://issues.apache.org/jira/browse/ZOOKEEPER-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689262#action_12689262 ] Giridharan Kesavan commented on ZOOKEEPER-60: - I don't see a way in gettin this done; only way that I see here it to pass the location of the zkserver.sh as an argument to the TestClient.cc file. Mahadev said he will be looking into this. > Get cppunit tests running as part of Hudson CI > -- > > Key: ZOOKEEPER-60 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-60 > Project: Zookeeper > Issue Type: Improvement > Components: build >Reporter: Patrick Hunt > Assignee: Giridharan Kesavan > Attachments: ZK-60.patch, ZK-60.patch > > > Investigate if it is possible to run cppunit tests as part of Hudson. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-60) Get cppunit tests running as part of Hudson CI
[ https://issues.apache.org/jira/browse/ZOOKEEPER-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-60: Attachment: ZK-60.patch Thanks to Mahadev for his help on this patch. With this patch the users of make can continue doing the make calls from src/c folder as they were doing before. > Get cppunit tests running as part of Hudson CI > -- > > Key: ZOOKEEPER-60 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-60 > Project: Zookeeper > Issue Type: Improvement > Components: build >Reporter: Patrick Hunt > Assignee: Giridharan Kesavan > Attachments: ZK-60.patch, ZK-60.patch, ZK-60.patch > > > Investigate if it is possible to run cppunit tests as part of Hudson. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-349) to automate patch testing
to automate patch testing -- Key: ZOOKEEPER-349 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-349 Project: Zookeeper Issue Type: Improvement Reporter: Giridharan Kesavan Assignee: Giridharan Kesavan -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-350) to run rats for releaseaudit
to run rats for releaseaudit - Key: ZOOKEEPER-350 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-350 Project: Zookeeper Issue Type: Sub-task Reporter: Giridharan Kesavan Assignee: Giridharan Kesavan -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-350) to run rats for releaseaudit
[ https://issues.apache.org/jira/browse/ZOOKEEPER-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-350: - Attachment: ZK-350.patch this patch enables releaseaudit target for zk > to run rats for releaseaudit > - > > Key: ZOOKEEPER-350 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-350 > Project: Zookeeper > Issue Type: Sub-task > Reporter: Giridharan Kesavan > Assignee: Giridharan Kesavan > Attachments: ZK-350.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-351) to run checkstyle
to run checkstyle - Key: ZOOKEEPER-351 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-351 Project: Zookeeper Issue Type: Sub-task Components: build Reporter: Giridharan Kesavan Assignee: Giridharan Kesavan -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-349) to automate patch testing
[ https://issues.apache.org/jira/browse/ZOOKEEPER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-349: - Component/s: build > to automate patch testing > -- > > Key: ZOOKEEPER-349 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-349 > Project: Zookeeper > Issue Type: Improvement > Components: build > Reporter: Giridharan Kesavan > Assignee: Giridharan Kesavan > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-351) to run checkstyle
[ https://issues.apache.org/jira/browse/ZOOKEEPER-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-351: - Attachment: ZK-351.patch enables checkstyle for zk > to run checkstyle > - > > Key: ZOOKEEPER-351 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-351 > Project: Zookeeper > Issue Type: Sub-task > Components: build > Reporter: Giridharan Kesavan > Assignee: Giridharan Kesavan > Attachments: ZK-351.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-352) to add standard ant targets required by test-patch.sh script
to add standard ant targets required by test-patch.sh script Key: ZOOKEEPER-352 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-352 Project: Zookeeper Issue Type: Sub-task Components: build Reporter: Giridharan Kesavan Assignee: Giridharan Kesavan -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-352) to add standard ant targets required by test-patch.sh script
[ https://issues.apache.org/jira/browse/ZOOKEEPER-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-352: - Attachment: ZK-352.patch patch adds test-patch and hudson-test-patch , test-contrib and test-core targets to builds.xml which is required by test-patch.sh > to add standard ant targets required by test-patch.sh script > > > Key: ZOOKEEPER-352 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-352 > Project: Zookeeper > Issue Type: Sub-task > Components: build > Reporter: Giridharan Kesavan > Assignee: Giridharan Kesavan > Attachments: ZK-352.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-353) javadoc warnings needs to be fixed
javadoc warnings needs to be fixed
---
Key: ZOOKEEPER-353
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-353
Project: Zookeeper
Issue Type: Sub-task
Reporter: Giridharan Kesavan
[javadoc]
/.../SOMETHING/trunk/src/java/generated/org/apache/zookeeper/server/quorum/QuorumPacket.java:46:
cannot find symbol
[javadoc] symbol : class OutputArchive
[javadoc] location: class org.apache.zookeeper.server.quorum.QuorumPacket
[javadoc] public void serialize(OutputArchive a_, String tag) throws
java.io.IOException {
[javadoc] ^
[javadoc]
/.../SOMETHING/trunk/src/java/generated/org/apache/zookeeper/server/quorum/QuorumPacket.java:63:
cannot find symbol
[javadoc] symbol : class InputArchive
[javadoc] location: class org.apache.zookeeper.server.quorum.QuorumPacket
[javadoc] public void deserialize(InputArchive a_, String tag) throws
java.io.IOException {
[javadoc] ^
[javadoc] Building index for all the packages and classes...
[javadoc] Building index for all classes...
[javadoc] Generating /.../SOMETHING/trunk/build/docs/api/stylesheet.css...
[javadoc] 4 errors
[javadoc] 124 warnings
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-353) javadoc warnings needs to be fixed
[
https://issues.apache.org/jira/browse/ZOOKEEPER-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giridharan Kesavan updated ZOOKEEPER-353:
-
Attachment: ZK-353.patch
this patch removes 100 warnings and 4 errors.
Still those 24 warnings needs to be fixes which requires editing the source
file..
For the remaining 24 warning's I'm going to file a different jira.
tnx!
> javadoc warnings needs to be fixed
> ---
>
> Key: ZOOKEEPER-353
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-353
> Project: Zookeeper
> Issue Type: Sub-task
> Reporter: Giridharan Kesavan
> Attachments: ZK-353.patch
>
>
> [javadoc]
> /.../SOMETHING/trunk/src/java/generated/org/apache/zookeeper/server/quorum/QuorumPacket.java:46:
> cannot find symbol
> [javadoc] symbol : class OutputArchive
> [javadoc] location: class org.apache.zookeeper.server.quorum.QuorumPacket
> [javadoc] public void serialize(OutputArchive a_, String tag) throws
> java.io.IOException {
> [javadoc] ^
> [javadoc]
> /.../SOMETHING/trunk/src/java/generated/org/apache/zookeeper/server/quorum/QuorumPacket.java:63:
> cannot find symbol
> [javadoc] symbol : class InputArchive
> [javadoc] location: class org.apache.zookeeper.server.quorum.QuorumPacket
> [javadoc] public void deserialize(InputArchive a_, String tag) throws
> java.io.IOException {
> [javadoc] ^
> [javadoc] Building index for all the packages and classes...
> [javadoc] Building index for all classes...
> [javadoc] Generating /.../SOMETHING/trunk/build/docs/api/stylesheet.css...
> [javadoc] 4 errors
> [javadoc] 124 warnings
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ZOOKEEPER-353) javadoc warnings needs to be fixed
[
https://issues.apache.org/jira/browse/ZOOKEEPER-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giridharan Kesavan reassigned ZOOKEEPER-353:
Assignee: Giridharan Kesavan
> javadoc warnings needs to be fixed
> ---
>
> Key: ZOOKEEPER-353
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-353
> Project: Zookeeper
> Issue Type: Sub-task
> Reporter: Giridharan Kesavan
> Assignee: Giridharan Kesavan
> Attachments: ZK-353.patch
>
>
> [javadoc]
> /.../SOMETHING/trunk/src/java/generated/org/apache/zookeeper/server/quorum/QuorumPacket.java:46:
> cannot find symbol
> [javadoc] symbol : class OutputArchive
> [javadoc] location: class org.apache.zookeeper.server.quorum.QuorumPacket
> [javadoc] public void serialize(OutputArchive a_, String tag) throws
> java.io.IOException {
> [javadoc] ^
> [javadoc]
> /.../SOMETHING/trunk/src/java/generated/org/apache/zookeeper/server/quorum/QuorumPacket.java:63:
> cannot find symbol
> [javadoc] symbol : class InputArchive
> [javadoc] location: class org.apache.zookeeper.server.quorum.QuorumPacket
> [javadoc] public void deserialize(InputArchive a_, String tag) throws
> java.io.IOException {
> [javadoc] ^
> [javadoc] Building index for all the packages and classes...
> [javadoc] Building index for all classes...
> [javadoc] Generating /.../SOMETHING/trunk/build/docs/api/stylesheet.css...
> [javadoc] 4 errors
> [javadoc] 124 warnings
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-354) to fix javadoc warning in the source files
to fix javadoc warning in the source files -- Key: ZOOKEEPER-354 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-354 Project: Zookeeper Issue Type: Sub-task Reporter: Giridharan Kesavan [javadoc] trunk/src/java/main/org/apache/zookeeper/ZooKeeper.java:597: warning - Tag @see:illegal character: "60" in "#create(String, byte[], List, CreateMode)" [javadoc]trunk/src/java/main/org/apache/zookeeper/ZooKeeper.java:597: warning - Tag @see:illegal character: "62" in "#create(String, byte[], List, CreateMode)" [javadoc]trunk/src/java/main/org/apache/zookeeper/ZooKeeper.java:597: warning - Tag @see: can't find create(String, byte[], List, CreateMode) in org.apache.zookeeper.ZooKeeper [javadoc]trunk/src/java/main/org/apache/zookeeper/ZooKeeper.java:499: warning - @param argument "flags" is not a parameter name. [javadoc] Building index for all the packages and classes... [javadoc] Building index for all classes... [javadoc] Generating trunk/build/docs/api/stylesheet.css... [javadoc] 24 warnings -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ZOOKEEPER-354) to fix javadoc warning in the source files
[ https://issues.apache.org/jira/browse/ZOOKEEPER-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan reassigned ZOOKEEPER-354: Assignee: Mahadev konar Mahadev said he will look into this. > to fix javadoc warning in the source files > -- > > Key: ZOOKEEPER-354 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-354 > Project: Zookeeper > Issue Type: Sub-task > Reporter: Giridharan Kesavan >Assignee: Mahadev konar > > [javadoc] trunk/src/java/main/org/apache/zookeeper/ZooKeeper.java:597: > warning - Tag @see:illegal character: "60" in "#create(String, byte[], > List, CreateMode)" > [javadoc]trunk/src/java/main/org/apache/zookeeper/ZooKeeper.java:597: > warning - Tag @see:illegal character: "62" in "#create(String, byte[], > List, CreateMode)" > [javadoc]trunk/src/java/main/org/apache/zookeeper/ZooKeeper.java:597: > warning - Tag @see: can't find create(String, byte[], List, CreateMode) > in org.apache.zookeeper.ZooKeeper > [javadoc]trunk/src/java/main/org/apache/zookeeper/ZooKeeper.java:499: > warning - @param argument "flags" is not a parameter name. > [javadoc] Building index for all the packages and classes... > [javadoc] Building index for all classes... > [javadoc] Generating trunk/build/docs/api/stylesheet.css... > [javadoc] 24 warnings -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-349) to automate patch testing
[ https://issues.apache.org/jira/browse/ZOOKEEPER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689753#action_12689753 ] Giridharan Kesavan commented on ZOOKEEPER-349: -- we should do the following changes once the above listed sub-tasks gets revolved.. test-patch.sh script resides in http://svn.apache.org/repos/asf/hadoop/core/nightly/test-patch dir. To get this pulled as part of Zookeeper trunk we may have to configure svn:externals. Commands to configure svn externals for test-patch.sh script.. check out zookeeper trunk cd /src/java export EDITOR=vim svn propedit svn:externals test [ the above step will open up the vim editor type in the following line and save it] bin http://svn.apache.org/repos/asf/hadoop/core/nightly/test-patch svn commit Once this is done we can create hudson job to enable patch testing for zookeeper. > to automate patch testing > -- > > Key: ZOOKEEPER-349 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-349 > Project: Zookeeper > Issue Type: Improvement > Components: build > Reporter: Giridharan Kesavan > Assignee: Giridharan Kesavan > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-351) to run checkstyle
[ https://issues.apache.org/jira/browse/ZOOKEEPER-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-351: - Status: Patch Available (was: Open) > to run checkstyle > - > > Key: ZOOKEEPER-351 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-351 > Project: Zookeeper > Issue Type: Sub-task > Components: build > Reporter: Giridharan Kesavan > Assignee: Giridharan Kesavan > Attachments: ZK-351.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-350) to run rats for releaseaudit
[ https://issues.apache.org/jira/browse/ZOOKEEPER-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-350: - Status: Patch Available (was: Open) > to run rats for releaseaudit > - > > Key: ZOOKEEPER-350 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-350 > Project: Zookeeper > Issue Type: Sub-task > Reporter: Giridharan Kesavan > Assignee: Giridharan Kesavan > Attachments: ZK-350.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-353) javadoc warnings needs to be fixed
[
https://issues.apache.org/jira/browse/ZOOKEEPER-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giridharan Kesavan updated ZOOKEEPER-353:
-
Status: Patch Available (was: Open)
> javadoc warnings needs to be fixed
> ---
>
> Key: ZOOKEEPER-353
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-353
> Project: Zookeeper
> Issue Type: Sub-task
> Reporter: Giridharan Kesavan
> Assignee: Giridharan Kesavan
> Attachments: ZK-353.patch
>
>
> [javadoc]
> /.../SOMETHING/trunk/src/java/generated/org/apache/zookeeper/server/quorum/QuorumPacket.java:46:
> cannot find symbol
> [javadoc] symbol : class OutputArchive
> [javadoc] location: class org.apache.zookeeper.server.quorum.QuorumPacket
> [javadoc] public void serialize(OutputArchive a_, String tag) throws
> java.io.IOException {
> [javadoc] ^
> [javadoc]
> /.../SOMETHING/trunk/src/java/generated/org/apache/zookeeper/server/quorum/QuorumPacket.java:63:
> cannot find symbol
> [javadoc] symbol : class InputArchive
> [javadoc] location: class org.apache.zookeeper.server.quorum.QuorumPacket
> [javadoc] public void deserialize(InputArchive a_, String tag) throws
> java.io.IOException {
> [javadoc] ^
> [javadoc] Building index for all the packages and classes...
> [javadoc] Building index for all classes...
> [javadoc] Generating /.../SOMETHING/trunk/build/docs/api/stylesheet.css...
> [javadoc] 4 errors
> [javadoc] 124 warnings
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-352) to add standard ant targets required by test-patch.sh script
[ https://issues.apache.org/jira/browse/ZOOKEEPER-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-352: - Status: Patch Available (was: Open) > to add standard ant targets required by test-patch.sh script > > > Key: ZOOKEEPER-352 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-352 > Project: Zookeeper > Issue Type: Sub-task > Components: build > Reporter: Giridharan Kesavan > Assignee: Giridharan Kesavan > Attachments: ZK-352.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-60) Get cppunit tests running as part of Hudson CI
[ https://issues.apache.org/jira/browse/ZOOKEEPER-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-60: Status: Patch Available (was: Open) > Get cppunit tests running as part of Hudson CI > -- > > Key: ZOOKEEPER-60 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-60 > Project: Zookeeper > Issue Type: Improvement > Components: build >Reporter: Patrick Hunt > Assignee: Giridharan Kesavan > Attachments: ZK-60.patch, ZK-60.patch, ZK-60.patch > > > Investigate if it is possible to run cppunit tests as part of Hudson. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-60) Get cppunit tests running as part of Hudson CI
[ https://issues.apache.org/jira/browse/ZOOKEEPER-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-60: Status: Open (was: Patch Available) > Get cppunit tests running as part of Hudson CI > -- > > Key: ZOOKEEPER-60 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-60 > Project: Zookeeper > Issue Type: Improvement > Components: build >Reporter: Patrick Hunt > Assignee: Giridharan Kesavan > Attachments: ZK-60.patch, ZK-60.patch, ZK-60.patch > > > Investigate if it is possible to run cppunit tests as part of Hudson. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-60) Get cppunit tests running as part of Hudson CI
[ https://issues.apache.org/jira/browse/ZOOKEEPER-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-60: Status: Patch Available (was: Open) re-submitting the patch. > Get cppunit tests running as part of Hudson CI > -- > > Key: ZOOKEEPER-60 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-60 > Project: Zookeeper > Issue Type: Improvement > Components: build >Reporter: Patrick Hunt > Assignee: Giridharan Kesavan > Attachments: ZK-60.patch, ZK-60.patch, ZK-60.patch > > > Investigate if it is possible to run cppunit tests as part of Hudson. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-60) Get cppunit tests running as part of Hudson CI
[ https://issues.apache.org/jira/browse/ZOOKEEPER-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695205#action_12695205 ] Giridharan Kesavan commented on ZOOKEEPER-60: - Thanks again for you help on this patch. > Get cppunit tests running as part of Hudson CI > -- > > Key: ZOOKEEPER-60 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-60 > Project: Zookeeper > Issue Type: Improvement > Components: build >Affects Versions: 3.0.0, 3.0.1, 3.1.0, 3.1.1 >Reporter: Patrick Hunt > Assignee: Giridharan Kesavan > Fix For: 3.2.0 > > Attachments: ZK-60.patch, ZK-60.patch, ZK-60.patch, ZOOKEEPER-60.patch > > > Investigate if it is possible to run cppunit tests as part of Hudson. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (ZOOKEEPER-60) Get cppunit tests running as part of Hudson CI
[ https://issues.apache.org/jira/browse/ZOOKEEPER-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695205#action_12695205 ] Giridharan Kesavan edited comment on ZOOKEEPER-60 at 4/2/09 6:15 PM: - Mahadev, Thanks for you help on this patch was (Author: gkesavan): Thanks again for you help on this patch. > Get cppunit tests running as part of Hudson CI > -- > > Key: ZOOKEEPER-60 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-60 > Project: Zookeeper > Issue Type: Improvement > Components: build >Affects Versions: 3.0.0, 3.0.1, 3.1.0, 3.1.1 >Reporter: Patrick Hunt > Assignee: Giridharan Kesavan > Fix For: 3.2.0 > > Attachments: ZK-60.patch, ZK-60.patch, ZK-60.patch, ZOOKEEPER-60.patch > > > Investigate if it is possible to run cppunit tests as part of Hudson. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-361) integrate cppunit testing as part of hudson patch process.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-361: - Attachment: zk-361.patch Here is the patch; I see a failure here, though this patch makes changes only to the build.xml. [exec] /home/gkesavan/zk-trunk/src/c/tests/TestZookeeperInit.cc:93: Assertion: equality assertion failed [Expected: 1, Actual : 2] [exec] Failures !!! [exec] Run: 32 Failure total: 1 Failures: 1 Errors: 0 [exec] make: *** [run-check] Error 1 [exec] Result: 2 Mahadev, Could you take a look , this failure happens only on vesta and not in my local box. > integrate cppunit testing as part of hudson patch process. > -- > > Key: ZOOKEEPER-361 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-361 > Project: Zookeeper > Issue Type: New Feature > Components: build >Affects Versions: 3.0.0, 3.0.1, 3.1.0, 3.1.1 >Reporter: Mahadev konar > Assignee: Giridharan Kesavan > Attachments: zk-361.patch > > > we need to test the c tests as part of our hudson patch testing process. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-361) integrate cppunit testing as part of hudson patch process.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695259#action_12695259 ] Giridharan Kesavan commented on ZOOKEEPER-361: -- you can test this out by doing "ant call-test-cppunit"- this would create the makefiles and executes the tests. tnx! > integrate cppunit testing as part of hudson patch process. > -- > > Key: ZOOKEEPER-361 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-361 > Project: Zookeeper > Issue Type: New Feature > Components: build >Affects Versions: 3.0.0, 3.0.1, 3.1.0, 3.1.1 >Reporter: Mahadev konar >Assignee: Giridharan Kesavan > Attachments: zk-361.patch > > > we need to test the c tests as part of our hudson patch testing process. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-371) to implement jdiff
to implement jdiff --- Key: ZOOKEEPER-371 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-371 Project: Zookeeper Issue Type: Improvement Components: build Affects Versions: 3.2.0 Environment: to implement jdiff Reporter: Giridharan Kesavan Assignee: Giridharan Kesavan Fix For: 3.2.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-361) integrate cppunit testing as part of hudson patch process.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698315#action_12698315 ] Giridharan Kesavan commented on ZOOKEEPER-361: -- thanks Mahadev for looking into this patch and fixing it. > integrate cppunit testing as part of hudson patch process. > -- > > Key: ZOOKEEPER-361 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-361 > Project: Zookeeper > Issue Type: New Feature > Components: build >Affects Versions: 3.0.0, 3.0.1, 3.1.0, 3.1.1 >Reporter: Mahadev konar > Assignee: Giridharan Kesavan > Fix For: 3.2.0 > > Attachments: zk-361.patch, zookeeper-361.patch > > > we need to test the c tests as part of our hudson patch testing process. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-361) integrate cppunit testing as part of hudson patch process.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698649#action_12698649 ] Giridharan Kesavan commented on ZOOKEEPER-361: -- +1 Patch works on vesta. > integrate cppunit testing as part of hudson patch process. > -- > > Key: ZOOKEEPER-361 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-361 > Project: Zookeeper > Issue Type: New Feature > Components: build >Affects Versions: 3.0.0, 3.0.1, 3.1.0, 3.1.1 >Reporter: Mahadev konar > Assignee: Giridharan Kesavan > Fix For: 3.2.0 > > Attachments: zk-361.patch, zookeeper-361.patch > > > we need to test the c tests as part of our hudson patch testing process. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-371) to implement jdiff
[ https://issues.apache.org/jira/browse/ZOOKEEPER-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-371: - Attachment: zookeeper-371.patch this patch enables jdiff for zookeeper. Tnx! > to implement jdiff > --- > > Key: ZOOKEEPER-371 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-371 > Project: Zookeeper > Issue Type: Improvement > Components: build >Affects Versions: 3.2.0 > Environment: to implement jdiff > Reporter: Giridharan Kesavan >Assignee: Giridharan Kesavan > Fix For: 3.2.0 > > Attachments: zookeeper-371.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-371) to implement jdiff
[ https://issues.apache.org/jira/browse/ZOOKEEPER-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-371: - Status: Patch Available (was: Open) Mahadev, Could you please review this? tnx! > to implement jdiff > --- > > Key: ZOOKEEPER-371 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-371 > Project: Zookeeper > Issue Type: Improvement > Components: build >Affects Versions: 3.2.0 > Environment: to implement jdiff > Reporter: Giridharan Kesavan >Assignee: Giridharan Kesavan > Fix For: 3.2.0 > > Attachments: zookeeper-371.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-371) to implement jdiff
[ https://issues.apache.org/jira/browse/ZOOKEEPER-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-371: - Attachment: (was: zookeeper-371.patch) > to implement jdiff > --- > > Key: ZOOKEEPER-371 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-371 > Project: Zookeeper > Issue Type: Improvement > Components: build >Affects Versions: 3.2.0 > Environment: to implement jdiff > Reporter: Giridharan Kesavan >Assignee: Giridharan Kesavan > Fix For: 3.2.0 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-371) to implement jdiff
[ https://issues.apache.org/jira/browse/ZOOKEEPER-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-371: - Status: Patch Available (was: Open) > to implement jdiff > --- > > Key: ZOOKEEPER-371 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-371 > Project: Zookeeper > Issue Type: Improvement > Components: build >Affects Versions: 3.2.0 > Environment: to implement jdiff > Reporter: Giridharan Kesavan >Assignee: Giridharan Kesavan > Fix For: 3.2.0 > > Attachments: zookeeper-371.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-371) to implement jdiff
[ https://issues.apache.org/jira/browse/ZOOKEEPER-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-371: - Attachment: zookeeper-371.patch > to implement jdiff > --- > > Key: ZOOKEEPER-371 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-371 > Project: Zookeeper > Issue Type: Improvement > Components: build >Affects Versions: 3.2.0 > Environment: to implement jdiff > Reporter: Giridharan Kesavan >Assignee: Giridharan Kesavan > Fix For: 3.2.0 > > Attachments: zookeeper-371.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-371) to implement jdiff
[ https://issues.apache.org/jira/browse/ZOOKEEPER-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-371: - Status: Open (was: Patch Available) > to implement jdiff > --- > > Key: ZOOKEEPER-371 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-371 > Project: Zookeeper > Issue Type: Improvement > Components: build >Affects Versions: 3.2.0 > Environment: to implement jdiff > Reporter: Giridharan Kesavan >Assignee: Giridharan Kesavan > Fix For: 3.2.0 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-371) to implement jdiff
[ https://issues.apache.org/jira/browse/ZOOKEEPER-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699034#action_12699034 ] Giridharan Kesavan commented on ZOOKEEPER-371: -- Please correct me if I'm wrong. patch contains api for 3.1.1(zookeeper_3.1.1.xml) and tha api-xml target would generate the api doc for 3.2.0(trunk version) This 3.1.1 api doc is required to compare the api changes b/w 3.1.1 and 3.2.0. Thanks, > to implement jdiff > --- > > Key: ZOOKEEPER-371 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-371 > Project: Zookeeper > Issue Type: Improvement > Components: build >Affects Versions: 3.2.0 > Environment: to implement jdiff >Reporter: Giridharan Kesavan >Assignee: Giridharan Kesavan > Fix For: 3.2.0 > > Attachments: zookeeper-371.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (ZOOKEEPER-371) to implement jdiff
[
https://issues.apache.org/jira/browse/ZOOKEEPER-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699040#action_12699040
]
Giridharan Kesavan edited comment on ZOOKEEPER-371 at 4/14/09 8:44 PM:
---
{quote}
run jdiff on svn trunk and then run jdiff on svn trunk+patch. If their is a
change then we -1 the patch. That way we do not need to check in the 3.1.1 api
docs. can we do that or doing what you suggest is the right way to go?
{quote}
This patch that I submitted is to run during the nightly to show up any changes
b/w 3.1.1 and 3.2.0.
But I understand the requirement that we want this jdiff as part of the patch
test process, that way we can say whether a patch has introduced any api
changes and do a +1/-1 based on that. I already have this in my task list and
I would be working on this enhancement soon.
tnx
was (Author: gkesavan):
{quote}
run jdiff on svn trunk and then run jdiff on svn trunk+patch. If their is a
change then we -1 the patch. That way we do not need to check in the 3.1.1 api
docs. can we do that or doing what you suggest is the right way to go?
{quote}
This patch that I submitted is to run during the nightly to show up any any
changes b/w 3.1.1 and 3.2.0.
But I understand the requirement that we want this jdiff as part of the path
test process, that way we can say whether a path has introduced any api changes
and do a +1/-1 based on that. I already have this in my task list and I would
be working on this enhancement soon.
tnx
> to implement jdiff
> ---
>
> Key: ZOOKEEPER-371
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-371
> Project: Zookeeper
> Issue Type: Improvement
> Components: build
>Affects Versions: 3.2.0
> Environment: to implement jdiff
> Reporter: Giridharan Kesavan
>Assignee: Giridharan Kesavan
> Fix For: 3.2.0
>
> Attachments: zookeeper-371.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-371) to implement jdiff
[
https://issues.apache.org/jira/browse/ZOOKEEPER-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699040#action_12699040
]
Giridharan Kesavan commented on ZOOKEEPER-371:
--
{quote}
run jdiff on svn trunk and then run jdiff on svn trunk+patch. If their is a
change then we -1 the patch. That way we do not need to check in the 3.1.1 api
docs. can we do that or doing what you suggest is the right way to go?
{quote}
This patch that I submitted is to run during the nightly to show up any any
changes b/w 3.1.1 and 3.2.0.
But I understand the requirement that we want this jdiff as part of the path
test process, that way we can say whether a path has introduced any api changes
and do a +1/-1 based on that. I already have this in my task list and I would
be working on this enhancement soon.
tnx
> to implement jdiff
> ---
>
> Key: ZOOKEEPER-371
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-371
> Project: Zookeeper
> Issue Type: Improvement
> Components: build
>Affects Versions: 3.2.0
> Environment: to implement jdiff
> Reporter: Giridharan Kesavan
>Assignee: Giridharan Kesavan
> Fix For: 3.2.0
>
> Attachments: zookeeper-371.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-371) to implement jdiff
[ https://issues.apache.org/jira/browse/ZOOKEEPER-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-371: - Status: Open (was: Patch Available) > to implement jdiff > --- > > Key: ZOOKEEPER-371 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-371 > Project: Zookeeper > Issue Type: Improvement > Components: build >Affects Versions: 3.2.0 > Environment: to implement jdiff > Reporter: Giridharan Kesavan >Assignee: Giridharan Kesavan > Fix For: 3.2.0 > > Attachments: zookeeper-371.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-371) to implement jdiff
[ https://issues.apache.org/jira/browse/ZOOKEEPER-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-371: - Status: Patch Available (was: Open) patch build stuck on hudson for more that 10Hrs. I killed the patch build. Resubmitting the patch to hudson. tnx > to implement jdiff > --- > > Key: ZOOKEEPER-371 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-371 > Project: Zookeeper > Issue Type: Improvement > Components: build >Affects Versions: 3.2.0 > Environment: to implement jdiff > Reporter: Giridharan Kesavan >Assignee: Giridharan Kesavan > Fix For: 3.2.0 > > Attachments: zookeeper-371.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-224) Deploy ZooKeeper 3.0.0 to a Maven Repository
[ https://issues.apache.org/jira/browse/ZOOKEEPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699044#action_12699044 ] Giridharan Kesavan commented on ZOOKEEPER-224: -- Hadoop-core is yet to be published to the maven repo. With HADOOP-3305 we have dependencies managed by ivy. Publishing hadoop-core to the mvn repo requires some more work :) I will be workin on this soon. > Deploy ZooKeeper 3.0.0 to a Maven Repository > > > Key: ZOOKEEPER-224 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-224 > Project: Zookeeper > Issue Type: Task > Components: build >Affects Versions: 3.0.0 >Reporter: Hiram Chirino >Assignee: Patrick Hunt >Priority: Critical > > I've created the maven poms needed for the 3.0.0 release. > The directory structure and artifacts located at: > http://people.apache.org/~chirino/zk-repo/ > aka > people.apache.org:/x1/users/chirino/public_html/zk-repo > Just need sto get GPG signed by the project KEY and deployed to: > people.apache.org:/www/people.apache.org/repo/m2-ibiblio-rsync-repository > Who's the current ZooKeeper release manager? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-377) running ant cppunit tests, a failure still results in BUILD SUCCESSFUL
[ https://issues.apache.org/jira/browse/ZOOKEEPER-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-377: - Attachment: zookeeper-377.patch this patch would fail the build on test failure. tnx! > running ant cppunit tests, a failure still results in BUILD SUCCESSFUL > -- > > Key: ZOOKEEPER-377 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-377 > Project: Zookeeper > Issue Type: Bug >Affects Versions: 3.2.0 >Reporter: Patrick Hunt > Assignee: Giridharan Kesavan >Priority: Critical > Fix For: 3.2.0 > > Attachments: zookeeper-377.patch > > > Giri, can you take a look at this? > I ran "ant test" > looks like this test failed: > [exec] Zookeeper_operations::testOperationsAndDisconnectConcurrently1 : > assertion > > then later... > [exec] > [exec] > /home/phunt/dev/workspace/svnzk_apache/src/c/tests/TestOperations.cc:551: > Assertion: equality assertion failed [Expected: -4, Actual : 0, > ZCONNECTIONLOSS != rc] > [exec] Failures !!! > [exec] Run: 38 Failure total: 1 Failures: 1 Errors: 0 > [exec] make: *** [run-check] Error 1 > [exec] Result: 2 > test-core: > test-contrib: > BUILD SUCCESSFUL > Total time: 15 minutes 39 seconds -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-377) running ant cppunit tests, a failure still results in BUILD SUCCESSFUL
[ https://issues.apache.org/jira/browse/ZOOKEEPER-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-377: - Status: Patch Available (was: Open) > running ant cppunit tests, a failure still results in BUILD SUCCESSFUL > -- > > Key: ZOOKEEPER-377 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-377 > Project: Zookeeper > Issue Type: Bug >Affects Versions: 3.2.0 >Reporter: Patrick Hunt > Assignee: Giridharan Kesavan >Priority: Critical > Fix For: 3.2.0 > > Attachments: zookeeper-377.patch > > > Giri, can you take a look at this? > I ran "ant test" > looks like this test failed: > [exec] Zookeeper_operations::testOperationsAndDisconnectConcurrently1 : > assertion > > then later... > [exec] > [exec] > /home/phunt/dev/workspace/svnzk_apache/src/c/tests/TestOperations.cc:551: > Assertion: equality assertion failed [Expected: -4, Actual : 0, > ZCONNECTIONLOSS != rc] > [exec] Failures !!! > [exec] Run: 38 Failure total: 1 Failures: 1 Errors: 0 > [exec] make: *** [run-check] Error 1 > [exec] Result: 2 > test-core: > test-contrib: > BUILD SUCCESSFUL > Total time: 15 minutes 39 seconds -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-371) to implement jdiff
[ https://issues.apache.org/jira/browse/ZOOKEEPER-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700652#action_12700652 ] Giridharan Kesavan commented on ZOOKEEPER-371: -- -1 for the release audit is expected as the jdiff is creating files on the fly; but for the author tags I think I should talk to Nigel tnx! > to implement jdiff > --- > > Key: ZOOKEEPER-371 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-371 > Project: Zookeeper > Issue Type: Improvement > Components: build >Affects Versions: 3.2.0 > Environment: to implement jdiff > Reporter: Giridharan Kesavan >Assignee: Giridharan Kesavan > Fix For: 3.2.0 > > Attachments: zookeeper-371.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-379) cppunit tests failed during hudson patch tests
cppunit tests failed during hudson patch tests --- Key: ZOOKEEPER-379 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-379 Project: Zookeeper Issue Type: Bug Components: tests Reporter: Giridharan Kesavan Assignee: Mahadev konar patch test build failed with " equality assertion failed" link: http://hudson.zones.apache.org/hudson/view/ZooKeeper/job/Zookeeper-Patch-vesta.apache.org/44/console Mahadev, Could you take a look? Tnx! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-371) to implement jdiff
[ https://issues.apache.org/jira/browse/ZOOKEEPER-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701379#action_12701379 ] Giridharan Kesavan commented on ZOOKEEPER-371: -- I'm working on recreating this patch to exclude the jute package. -tnx > to implement jdiff > --- > > Key: ZOOKEEPER-371 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-371 > Project: Zookeeper > Issue Type: Improvement > Components: build >Affects Versions: 3.2.0 > Environment: to implement jdiff >Reporter: Giridharan Kesavan >Assignee: Giridharan Kesavan > Fix For: 3.2.0 > > Attachments: zookeeper-371.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-371) to implement jdiff
[ https://issues.apache.org/jira/browse/ZOOKEEPER-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-371: - Status: Open (was: Patch Available) > to implement jdiff > --- > > Key: ZOOKEEPER-371 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-371 > Project: Zookeeper > Issue Type: Improvement > Components: build >Affects Versions: 3.2.0 > Environment: to implement jdiff > Reporter: Giridharan Kesavan >Assignee: Giridharan Kesavan > Fix For: 3.2.0 > > Attachments: zookeeper-371.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-371) to implement jdiff
[ https://issues.apache.org/jira/browse/ZOOKEEPER-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-371: - Attachment: zookeeper-371.patch this patch excludes jute package for jdiff > to implement jdiff > --- > > Key: ZOOKEEPER-371 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-371 > Project: Zookeeper > Issue Type: Improvement > Components: build >Affects Versions: 3.2.0 > Environment: to implement jdiff > Reporter: Giridharan Kesavan >Assignee: Giridharan Kesavan > Fix For: 3.2.0 > > Attachments: zookeeper-371.patch, zookeeper-371.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-371) to implement jdiff
[ https://issues.apache.org/jira/browse/ZOOKEEPER-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-371: - Status: Patch Available (was: Open) > to implement jdiff > --- > > Key: ZOOKEEPER-371 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-371 > Project: Zookeeper > Issue Type: Improvement > Components: build >Affects Versions: 3.2.0 > Environment: to implement jdiff > Reporter: Giridharan Kesavan >Assignee: Giridharan Kesavan > Fix For: 3.2.0 > > Attachments: zookeeper-371.patch, zookeeper-371.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-412) checkstyle target fails trunk build
checkstyle target fails trunk build --- Key: ZOOKEEPER-412 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-412 Project: Zookeeper Issue Type: Bug Reporter: Giridharan Kesavan BUILD FAILED /home/hudson/hudson-slave/workspace/ZooKeeper-trunk/trunk/build.xml:865: Unable to create a Checker: cannot initialize module PackageHtml - Unable to instantiate PackageHtml Tnx! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-429) Python contrib test failing on hudson
[
https://issues.apache.org/jira/browse/ZOOKEEPER-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715901#action_12715901
]
Giridharan Kesavan commented on ZOOKEEPER-429:
--
If you are talkin about warning, I think we can safely ignore it.
if you are talking about the test-contrib target:
test-contrib is a dummy target that I 've created as test-patch script expects
an ant target called test-contrib which would run contrib test.
> Python contrib test failing on hudson
> -
>
> Key: ZOOKEEPER-429
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-429
> Project: Zookeeper
> Issue Type: Bug
>Reporter: Flavio Paiva Junqueira
>
> I was checking the console output of:
> http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-vesta.apache.org/100/
> and I observed the following output for the contrib tests:
> {noformat}
> [exec]
> ==
> [exec]
> ==
> [exec] Running contrib tests.
> [exec]
> ==
> [exec]
> ==
> [exec]
> [exec]
> [exec] Warning: bad ps syntax, perhaps a bogus '-'? See
> http://procps.sf.net/faq.html
> [exec] /bin/kill -9 30147
> [exec] kill: No such process
> [exec] /home/hudson/tools/ant/latest/bin/ant
> -Declipse.home=/home/nigel/tools/eclipse/latest
> -Dpython.home=/home/nigel/tools/python/latest -DZooKeeperPatchProcess=
> -Dtest.junit.output.format=xml -Dtest.output=yes test-contrib
> [exec] Buildfile: build.xml
> [exec]
> [exec] test-contrib:
> [exec]
> [exec] BUILD SUCCESSFUL
> [exec] Total time: 0 seconds
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-224) Deploy ZooKeeper 3.2.0 to a Maven Repository
[ https://issues.apache.org/jira/browse/ZOOKEEPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722951#action_12722951 ] Giridharan Kesavan commented on ZOOKEEPER-224: -- I'm working on getting the hadoop jars published to the maven repository using ivy. In the case of zookeeper as well we can use ivy to publish zookeeper.jar. > Deploy ZooKeeper 3.2.0 to a Maven Repository > > > Key: ZOOKEEPER-224 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-224 > Project: Zookeeper > Issue Type: Task > Components: build >Affects Versions: 3.0.0 >Reporter: Hiram Chirino >Assignee: Patrick Hunt >Priority: Critical > Fix For: 3.2.0 > > > I've created the maven poms needed for the 3.0.0 release. > The directory structure and artifacts located at: > http://people.apache.org/~chirino/zk-repo/ > aka > people.apache.org:/x1/users/chirino/public_html/zk-repo > Just need sto get GPG signed by the project KEY and deployed to: > people.apache.org:/www/people.apache.org/repo/m2-ibiblio-rsync-repository > Who's the current ZooKeeper release manager? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-460) bad testRetry in cppunit tests (hudson failure)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-460: - Attachment: zookeeper-460.patch this should fix the clover classpath issue > bad testRetry in cppunit tests (hudson failure) > --- > > Key: ZOOKEEPER-460 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-460 > Project: Zookeeper > Issue Type: Bug > Components: c client, tests >Reporter: Patrick Hunt >Assignee: Henry Robinson > Fix For: 3.2.1, 3.3.0 > > Attachments: zookeeper-460.patch > > > the followng code failed on hudson > http://hudson.zones.apache.org/hudson/view/ZooKeeper/job/ZooKeeper-trunk/371/ > watchctx_t ctx1, ctx2; > zhandle_t *zk1 = createClient(&ctx1); > CPPUNIT_ASSERT_EQUAL(true, ctx1.waitForConnected(zk1)); > zhandle_t *zk2 = createClient(&ctx2); > zookeeper_close(zk1); > CPPUNIT_ASSERT_EQUAL(true, ctx2.waitForConnected(zk2)); > there's a problem with this test, it assumes that close(1) can be called > before createclient(2) gets connected. > this is not correct: createclient is an async call an in some cases the > connection can be established before > create client returns. > this shows a failure in this case because client1 was created, then client2 > attempted to connect > but failed due to this on the server (max conn exceeded): > sprintf(cmd, "export ZKMAXCNXNS=1;%s startClean %s", ZKSERVER_CMD, > getHostPorts()); > conn 2 failed and therefore the following assert eventually failed. > this code should not assume that close(1) will beat connect(2) > Henry can you take a look? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-488) to fix src/c/tests/zkServer.sh script to add clover in classpath
to fix src/c/tests/zkServer.sh script to add clover in classpath Key: ZOOKEEPER-488 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-488 Project: Zookeeper Issue Type: Improvement Components: scripts Reporter: Giridharan Kesavan Assignee: Giridharan Kesavan -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-488) to fix src/c/tests/zkServer.sh script to add clover in classpath
[ https://issues.apache.org/jira/browse/ZOOKEEPER-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-488: - Attachment: zookeeper-488.patch > to fix src/c/tests/zkServer.sh script to add clover in classpath > > > Key: ZOOKEEPER-488 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-488 > Project: Zookeeper > Issue Type: Improvement > Components: scripts > Reporter: Giridharan Kesavan > Assignee: Giridharan Kesavan > Attachments: zookeeper-488.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-488) to fix src/c/tests/zkServer.sh script to add clover in classpath
[ https://issues.apache.org/jira/browse/ZOOKEEPER-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-488: - Status: Patch Available (was: Open) > to fix src/c/tests/zkServer.sh script to add clover in classpath > > > Key: ZOOKEEPER-488 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-488 > Project: Zookeeper > Issue Type: Improvement > Components: scripts > Reporter: Giridharan Kesavan > Assignee: Giridharan Kesavan > Attachments: zookeeper-488.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-488) to fix src/c/tests/zkServer.sh script to add clover in classpath
[ https://issues.apache.org/jira/browse/ZOOKEEPER-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-488: - Resolution: Fixed Fix Version/s: 3.3.0 Status: Resolved (was: Patch Available) I just committed this! > to fix src/c/tests/zkServer.sh script to add clover in classpath > > > Key: ZOOKEEPER-488 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-488 > Project: Zookeeper > Issue Type: Improvement > Components: scripts > Reporter: Giridharan Kesavan > Assignee: Giridharan Kesavan > Fix For: 3.3.0 > > Attachments: zookeeper-488.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-484) Clients get SESSION MOVED exception when switching from follower to a leader.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-484: - Status: Open (was: Patch Available) resubmitting the patch to the patch queue. > Clients get SESSION MOVED exception when switching from follower to a leader. > - > > Key: ZOOKEEPER-484 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-484 > Project: Zookeeper > Issue Type: Bug > Components: server >Affects Versions: 3.2.0 >Reporter: Mahadev konar >Assignee: Mahadev konar >Priority: Blocker > Fix For: 3.2.1, 3.3.0 > > Attachments: sessionTest.patch, ZOOKEEPER-484.patch > > > When a client is connected to follower and get disconnected and connects to a > leader it gets SESSION MOVED excpetion. This is beacuse of a bug in the new > feature of ZOOKEEPER-417 that we added in 3.2. All the releases before 3.2 DO > NOT have this problem. The fix is to make sure the ownership of a connection > gets changed when a session moves from follower to the leader. The workaround > to it in 3.2.0 would be to swithc off connection from clients to the leader. > take a look at *leaderServers* java property in > http://hadoop.apache.org/zookeeper/docs/r3.2.0/zookeeperAdmin.html. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-484) Clients get SESSION MOVED exception when switching from follower to a leader.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-484: - Status: Patch Available (was: Open) > Clients get SESSION MOVED exception when switching from follower to a leader. > - > > Key: ZOOKEEPER-484 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-484 > Project: Zookeeper > Issue Type: Bug > Components: server >Affects Versions: 3.2.0 >Reporter: Mahadev konar >Assignee: Mahadev konar >Priority: Blocker > Fix For: 3.2.1, 3.3.0 > > Attachments: sessionTest.patch, ZOOKEEPER-484.patch > > > When a client is connected to follower and get disconnected and connects to a > leader it gets SESSION MOVED excpetion. This is beacuse of a bug in the new > feature of ZOOKEEPER-417 that we added in 3.2. All the releases before 3.2 DO > NOT have this problem. The fix is to make sure the ownership of a connection > gets changed when a session moves from follower to the leader. The workaround > to it in 3.2.0 would be to swithc off connection from clients to the leader. > take a look at *leaderServers* java property in > http://hadoop.apache.org/zookeeper/docs/r3.2.0/zookeeperAdmin.html. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-504) ClassCastException in LedgerManagementProcessor
[ https://issues.apache.org/jira/browse/ZOOKEEPER-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-504: - Status: Patch Available (was: Open) > ClassCastException in LedgerManagementProcessor > --- > > Key: ZOOKEEPER-504 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-504 > Project: Zookeeper > Issue Type: Bug > Components: contrib-bookkeeper >Affects Versions: 3.2.0 >Reporter: Utkarsh Srivastava >Assignee: Utkarsh Srivastava > Fix For: 3.3.0 > > Attachments: ZOOKEEPER-504.1.patch, ZOOKEEPER-504.patch, > ZOOKEEPER-504.patch > > > java.lang.ClassCastException: > org.apache.bookkeeper.client.LedgerManagementProcessor$OpenLedgerOp cannot be > cast to org.apache.bookkeeper.client.LedgerManagementProcessor$CloseLedgerOp > at > org.apache.bookkeeper.client.LedgerManagementProcessor.processResult(LedgerManagementProcessor.java:1083) > This seems to be happening because its a nested switch case statement. And > the OPEN: case, doesn't ever call a break. It only calls a break from the > inner switch-case and hence falls through into the CLOSE: case. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
