You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Chris Darroch (JIRA)" <ji...@apache.org> on 2009/07/15 20:08:14 UTC
[jira] Created: (ZOOKEEPER-474) add compile, test, and improved
package targets to zkperl build.xml
add compile, test, and improved package targets to zkperl build.xml
-------------------------------------------------------------------
Key: ZOOKEEPER-474
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-474
Project: Zookeeper
Issue Type: Improvement
Components: contrib
Affects Versions: 3.2.0
Reporter: Chris Darroch
Fix For: 3.2.1
Attachments: ZOOKEEPER-474.patch
This patch adds compile and test targets to the zkperl build.xml, and tweaks the package target a little to use the manifest file.
For me, "ant compile", "ant test", and "ant clean" all work (from scratch, in each case) when using Ant in the local src/contrib/zkperl directory.
Further, "ant package" in the top-level directory seems to continue to build zkperl along with everything else, and leaves out the build.xml and t/zkServer.sh files, which is appropriate.
>From what I can see, the top-level build.xml doesn't actually invoke the test-contrib target, so I'm not sure if there's a way to integrate the zkperl tests into the main hudson automated test process, but that would be ideal, if at all possible. I feel like I've seen comments to the effect that the zkpython tests are run automatically, but I'm not sure if that's actually true or not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-474) add compile, test, and improved
package targets to zkperl build.xml
Posted by "Chris Darroch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Darroch updated ZOOKEEPER-474:
------------------------------------
Attachment: ZOOKEEPER-474.patch
> add compile, test, and improved package targets to zkperl build.xml
> -------------------------------------------------------------------
>
> Key: ZOOKEEPER-474
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-474
> Project: Zookeeper
> Issue Type: Improvement
> Components: contrib
> Affects Versions: 3.2.0
> Reporter: Chris Darroch
> Fix For: 3.2.1
>
> Attachments: ZOOKEEPER-474.patch
>
>
> This patch adds compile and test targets to the zkperl build.xml, and tweaks the package target a little to use the manifest file.
> For me, "ant compile", "ant test", and "ant clean" all work (from scratch, in each case) when using Ant in the local src/contrib/zkperl directory.
> Further, "ant package" in the top-level directory seems to continue to build zkperl along with everything else, and leaves out the build.xml and t/zkServer.sh files, which is appropriate.
> From what I can see, the top-level build.xml doesn't actually invoke the test-contrib target, so I'm not sure if there's a way to integrate the zkperl tests into the main hudson automated test process, but that would be ideal, if at all possible. I feel like I've seen comments to the effect that the zkpython tests are run automatically, but I'm not sure if that's actually true or not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-474) add compile, test, and improved
package targets to zkperl build.xml
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-474:
-----------------------------------
Attachment: zk474_testout.txt
> add compile, test, and improved package targets to zkperl build.xml
> -------------------------------------------------------------------
>
> Key: ZOOKEEPER-474
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-474
> Project: Zookeeper
> Issue Type: Improvement
> Components: contrib
> Affects Versions: 3.2.0
> Reporter: Chris Darroch
> Assignee: Chris Darroch
> Fix For: 3.2.1, 3.3.0
>
> Attachments: zk474_testout.txt, ZOOKEEPER-474.patch
>
>
> This patch adds compile and test targets to the zkperl build.xml, and tweaks the package target a little to use the manifest file.
> For me, "ant compile", "ant test", and "ant clean" all work (from scratch, in each case) when using Ant in the local src/contrib/zkperl directory.
> Further, "ant package" in the top-level directory seems to continue to build zkperl along with everything else, and leaves out the build.xml and t/zkServer.sh files, which is appropriate.
> From what I can see, the top-level build.xml doesn't actually invoke the test-contrib target, so I'm not sure if there's a way to integrate the zkperl tests into the main hudson automated test process, but that would be ideal, if at all possible. I feel like I've seen comments to the effect that the zkpython tests are run automatically, but I'm not sure if that's actually true or not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-474) add compile, test, and improved
package targets to zkperl build.xml
Posted by "Chris Darroch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741503#action_12741503 ]
Chris Darroch commented on ZOOKEEPER-474:
-----------------------------------------
Nothing yet, sorry. Might be a couple of weeks before I get a chance to look; it's extra busy at work at the moment.
> add compile, test, and improved package targets to zkperl build.xml
> -------------------------------------------------------------------
>
> Key: ZOOKEEPER-474
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-474
> Project: Zookeeper
> Issue Type: Improvement
> Components: contrib
> Affects Versions: 3.2.0
> Reporter: Chris Darroch
> Assignee: Chris Darroch
> Fix For: 3.2.1, 3.3.0
>
> Attachments: zk474_testout.txt, ZOOKEEPER-474.patch
>
>
> This patch adds compile and test targets to the zkperl build.xml, and tweaks the package target a little to use the manifest file.
> For me, "ant compile", "ant test", and "ant clean" all work (from scratch, in each case) when using Ant in the local src/contrib/zkperl directory.
> Further, "ant package" in the top-level directory seems to continue to build zkperl along with everything else, and leaves out the build.xml and t/zkServer.sh files, which is appropriate.
> From what I can see, the top-level build.xml doesn't actually invoke the test-contrib target, so I'm not sure if there's a way to integrate the zkperl tests into the main hudson automated test process, but that would be ideal, if at all possible. I feel like I've seen comments to the effect that the zkpython tests are run automatically, but I'm not sure if that's actually true or not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ZOOKEEPER-474) add compile, test, and improved
package targets to zkperl build.xml
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt reassigned ZOOKEEPER-474:
--------------------------------------
Assignee: Chris Darroch
> add compile, test, and improved package targets to zkperl build.xml
> -------------------------------------------------------------------
>
> Key: ZOOKEEPER-474
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-474
> Project: Zookeeper
> Issue Type: Improvement
> Components: contrib
> Affects Versions: 3.2.0
> Reporter: Chris Darroch
> Assignee: Chris Darroch
> Fix For: 3.2.1
>
> Attachments: ZOOKEEPER-474.patch
>
>
> This patch adds compile and test targets to the zkperl build.xml, and tweaks the package target a little to use the manifest file.
> For me, "ant compile", "ant test", and "ant clean" all work (from scratch, in each case) when using Ant in the local src/contrib/zkperl directory.
> Further, "ant package" in the top-level directory seems to continue to build zkperl along with everything else, and leaves out the build.xml and t/zkServer.sh files, which is appropriate.
> From what I can see, the top-level build.xml doesn't actually invoke the test-contrib target, so I'm not sure if there's a way to integrate the zkperl tests into the main hudson automated test process, but that would be ideal, if at all possible. I feel like I've seen comments to the effect that the zkpython tests are run automatically, but I'm not sure if that's actually true or not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-474) add compile, test, and improved
package targets to zkperl build.xml
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-474:
-----------------------------------
Fix Version/s: (was: 3.3.0)
3.4.0
> add compile, test, and improved package targets to zkperl build.xml
> -------------------------------------------------------------------
>
> Key: ZOOKEEPER-474
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-474
> Project: Zookeeper
> Issue Type: Improvement
> Components: contrib
> Affects Versions: 3.2.0
> Reporter: Chris Darroch
> Assignee: Chris Darroch
> Fix For: 3.4.0
>
> Attachments: zk474_testout.txt, ZOOKEEPER-474.patch
>
>
> This patch adds compile and test targets to the zkperl build.xml, and tweaks the package target a little to use the manifest file.
> For me, "ant compile", "ant test", and "ant clean" all work (from scratch, in each case) when using Ant in the local src/contrib/zkperl directory.
> Further, "ant package" in the top-level directory seems to continue to build zkperl along with everything else, and leaves out the build.xml and t/zkServer.sh files, which is appropriate.
> From what I can see, the top-level build.xml doesn't actually invoke the test-contrib target, so I'm not sure if there's a way to integrate the zkperl tests into the main hudson automated test process, but that would be ideal, if at all possible. I feel like I've seen comments to the effect that the zkpython tests are run automatically, but I'm not sure if that's actually true or not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-474) add compile, test, and improved
package targets to zkperl build.xml
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-474:
-----------------------------------
Fix Version/s: 3.3.0
> add compile, test, and improved package targets to zkperl build.xml
> -------------------------------------------------------------------
>
> Key: ZOOKEEPER-474
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-474
> Project: Zookeeper
> Issue Type: Improvement
> Components: contrib
> Affects Versions: 3.2.0
> Reporter: Chris Darroch
> Assignee: Chris Darroch
> Fix For: 3.2.1, 3.3.0
>
> Attachments: ZOOKEEPER-474.patch
>
>
> This patch adds compile and test targets to the zkperl build.xml, and tweaks the package target a little to use the manifest file.
> For me, "ant compile", "ant test", and "ant clean" all work (from scratch, in each case) when using Ant in the local src/contrib/zkperl directory.
> Further, "ant package" in the top-level directory seems to continue to build zkperl along with everything else, and leaves out the build.xml and t/zkServer.sh files, which is appropriate.
> From what I can see, the top-level build.xml doesn't actually invoke the test-contrib target, so I'm not sure if there's a way to integrate the zkperl tests into the main hudson automated test process, but that would be ideal, if at all possible. I feel like I've seen comments to the effect that the zkpython tests are run automatically, but I'm not sure if that's actually true or not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-474) add compile, test, and improved
package targets to zkperl build.xml
Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741443#action_12741443 ]
Mahadev konar commented on ZOOKEEPER-474:
-----------------------------------------
chris,
any update on this?
> add compile, test, and improved package targets to zkperl build.xml
> -------------------------------------------------------------------
>
> Key: ZOOKEEPER-474
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-474
> Project: Zookeeper
> Issue Type: Improvement
> Components: contrib
> Affects Versions: 3.2.0
> Reporter: Chris Darroch
> Assignee: Chris Darroch
> Fix For: 3.2.1, 3.3.0
>
> Attachments: zk474_testout.txt, ZOOKEEPER-474.patch
>
>
> This patch adds compile and test targets to the zkperl build.xml, and tweaks the package target a little to use the manifest file.
> For me, "ant compile", "ant test", and "ant clean" all work (from scratch, in each case) when using Ant in the local src/contrib/zkperl directory.
> Further, "ant package" in the top-level directory seems to continue to build zkperl along with everything else, and leaves out the build.xml and t/zkServer.sh files, which is appropriate.
> From what I can see, the top-level build.xml doesn't actually invoke the test-contrib target, so I'm not sure if there's a way to integrate the zkperl tests into the main hudson automated test process, but that would be ideal, if at all possible. I feel like I've seen comments to the effect that the zkpython tests are run automatically, but I'm not sure if that's actually true or not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-474) add compile, test, and improved
package targets to zkperl build.xml
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-474:
-----------------------------------
Status: Open (was: Patch Available)
tests failing on my system - cancelling patch
See the attached file for test output
note to committer : make sure to chmod +x on the shell script
> add compile, test, and improved package targets to zkperl build.xml
> -------------------------------------------------------------------
>
> Key: ZOOKEEPER-474
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-474
> Project: Zookeeper
> Issue Type: Improvement
> Components: contrib
> Affects Versions: 3.2.0
> Reporter: Chris Darroch
> Assignee: Chris Darroch
> Fix For: 3.2.1, 3.3.0
>
> Attachments: zk474_testout.txt, ZOOKEEPER-474.patch
>
>
> This patch adds compile and test targets to the zkperl build.xml, and tweaks the package target a little to use the manifest file.
> For me, "ant compile", "ant test", and "ant clean" all work (from scratch, in each case) when using Ant in the local src/contrib/zkperl directory.
> Further, "ant package" in the top-level directory seems to continue to build zkperl along with everything else, and leaves out the build.xml and t/zkServer.sh files, which is appropriate.
> From what I can see, the top-level build.xml doesn't actually invoke the test-contrib target, so I'm not sure if there's a way to integrate the zkperl tests into the main hudson automated test process, but that would be ideal, if at all possible. I feel like I've seen comments to the effect that the zkpython tests are run automatically, but I'm not sure if that's actually true or not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-474) add compile, test, and improved
package targets to zkperl build.xml
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-474:
-----------------------------------
Status: Patch Available (was: Open)
> add compile, test, and improved package targets to zkperl build.xml
> -------------------------------------------------------------------
>
> Key: ZOOKEEPER-474
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-474
> Project: Zookeeper
> Issue Type: Improvement
> Components: contrib
> Affects Versions: 3.2.0
> Reporter: Chris Darroch
> Assignee: Chris Darroch
> Fix For: 3.2.1, 3.3.0
>
> Attachments: ZOOKEEPER-474.patch
>
>
> This patch adds compile and test targets to the zkperl build.xml, and tweaks the package target a little to use the manifest file.
> For me, "ant compile", "ant test", and "ant clean" all work (from scratch, in each case) when using Ant in the local src/contrib/zkperl directory.
> Further, "ant package" in the top-level directory seems to continue to build zkperl along with everything else, and leaves out the build.xml and t/zkServer.sh files, which is appropriate.
> From what I can see, the top-level build.xml doesn't actually invoke the test-contrib target, so I'm not sure if there's a way to integrate the zkperl tests into the main hudson automated test process, but that would be ideal, if at all possible. I feel like I've seen comments to the effect that the zkpython tests are run automatically, but I'm not sure if that's actually true or not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-474) add compile, test, and improved
package targets to zkperl build.xml
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738810#action_12738810 ]
Patrick Hunt commented on ZOOKEEPER-474:
----------------------------------------
btw - I have a linux 32bit system, single core, 1.6ghz, 1gig, up to date jaunty
> add compile, test, and improved package targets to zkperl build.xml
> -------------------------------------------------------------------
>
> Key: ZOOKEEPER-474
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-474
> Project: Zookeeper
> Issue Type: Improvement
> Components: contrib
> Affects Versions: 3.2.0
> Reporter: Chris Darroch
> Assignee: Chris Darroch
> Fix For: 3.2.1, 3.3.0
>
> Attachments: zk474_testout.txt, ZOOKEEPER-474.patch
>
>
> This patch adds compile and test targets to the zkperl build.xml, and tweaks the package target a little to use the manifest file.
> For me, "ant compile", "ant test", and "ant clean" all work (from scratch, in each case) when using Ant in the local src/contrib/zkperl directory.
> Further, "ant package" in the top-level directory seems to continue to build zkperl along with everything else, and leaves out the build.xml and t/zkServer.sh files, which is appropriate.
> From what I can see, the top-level build.xml doesn't actually invoke the test-contrib target, so I'm not sure if there's a way to integrate the zkperl tests into the main hudson automated test process, but that would be ideal, if at all possible. I feel like I've seen comments to the effect that the zkpython tests are run automatically, but I'm not sure if that's actually true or not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-474) add compile, test, and improved
package targets to zkperl build.xml
Posted by "Chris Darroch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Darroch updated ZOOKEEPER-474:
------------------------------------
Interesting. I'll try to take a look shortly. The ironic thing is that you appear to have some intriguing but harmless compile warnings, and then the tests fail in one of the smallest tests (where we just try to work around the single log file from the C client), but pass all the complex ones! So that's mostly good news, I think.
> add compile, test, and improved package targets to zkperl build.xml
> -------------------------------------------------------------------
>
> Key: ZOOKEEPER-474
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-474
> Project: Zookeeper
> Issue Type: Improvement
> Components: contrib
> Affects Versions: 3.2.0
> Reporter: Chris Darroch
> Assignee: Chris Darroch
> Fix For: 3.2.1, 3.3.0
>
> Attachments: zk474_testout.txt, ZOOKEEPER-474.patch
>
>
> This patch adds compile and test targets to the zkperl build.xml, and tweaks the package target a little to use the manifest file.
> For me, "ant compile", "ant test", and "ant clean" all work (from scratch, in each case) when using Ant in the local src/contrib/zkperl directory.
> Further, "ant package" in the top-level directory seems to continue to build zkperl along with everything else, and leaves out the build.xml and t/zkServer.sh files, which is appropriate.
> From what I can see, the top-level build.xml doesn't actually invoke the test-contrib target, so I'm not sure if there's a way to integrate the zkperl tests into the main hudson automated test process, but that would be ideal, if at all possible. I feel like I've seen comments to the effect that the zkpython tests are run automatically, but I'm not sure if that's actually true or not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-474) add compile, test, and improved
package targets to zkperl build.xml
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-474:
-----------------------------------
Fix Version/s: (was: 3.2.1)
moving out of 3.2.1, won't be ready for release timeframe, can go into 3.3
> add compile, test, and improved package targets to zkperl build.xml
> -------------------------------------------------------------------
>
> Key: ZOOKEEPER-474
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-474
> Project: Zookeeper
> Issue Type: Improvement
> Components: contrib
> Affects Versions: 3.2.0
> Reporter: Chris Darroch
> Assignee: Chris Darroch
> Fix For: 3.3.0
>
> Attachments: zk474_testout.txt, ZOOKEEPER-474.patch
>
>
> This patch adds compile and test targets to the zkperl build.xml, and tweaks the package target a little to use the manifest file.
> For me, "ant compile", "ant test", and "ant clean" all work (from scratch, in each case) when using Ant in the local src/contrib/zkperl directory.
> Further, "ant package" in the top-level directory seems to continue to build zkperl along with everything else, and leaves out the build.xml and t/zkServer.sh files, which is appropriate.
> From what I can see, the top-level build.xml doesn't actually invoke the test-contrib target, so I'm not sure if there's a way to integrate the zkperl tests into the main hudson automated test process, but that would be ideal, if at all possible. I feel like I've seen comments to the effect that the zkpython tests are run automatically, but I'm not sure if that's actually true or not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.