You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Cheolsoo Park (JIRA)" <ji...@apache.org> on 2012/09/28 00:29:08 UTC
[jira] [Created] (PIG-2938) All unit tests that use MR2 MiniCluster
are broken in trunk
Cheolsoo Park created PIG-2938:
----------------------------------
Summary: All unit tests that use MR2 MiniCluster are broken in trunk
Key: PIG-2938
URL: https://issues.apache.org/jira/browse/PIG-2938
Project: Pig
Issue Type: Bug
Components: build
Reporter: Cheolsoo Park
Assignee: Cheolsoo Park
Priority: Critical
To reproduce the issue, run:
{code}
ant test -Dhadoopversion=23 -Dtestcase=TestAccumulator
{code}
This fails with the following error:
{code}
Caused by: java.lang.ClassNotFoundException: org.jboss.netty.channel.group.ChannelGroup
{code}
This is a regression from PIG-2844 where netty is commented out from ivy.xml.
I guess that the intention was to exclude netty from the generated pom file, but this breaks unit tests.
I propose that we change the ivy conf of netty from "compile-> master" to "test->master" instead of commenting it out. That would prevent netty from being pulled down at compile time by 3rd party projects that consume the pig pom file.
I am speculating here, so please correct me if I am wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PIG-2938) All unit tests that use MR2 MiniCluster
are broken in trunk
Posted by "Cheolsoo Park (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cheolsoo Park updated PIG-2938:
-------------------------------
Attachment: PIG-2938.patch
Uploading a patch that puts back netty to ivy.xml, but changing the conf attribute from "compile->master" to "test->master".
> All unit tests that use MR2 MiniCluster are broken in trunk
> -----------------------------------------------------------
>
> Key: PIG-2938
> URL: https://issues.apache.org/jira/browse/PIG-2938
> Project: Pig
> Issue Type: Bug
> Components: build
> Reporter: Cheolsoo Park
> Assignee: Cheolsoo Park
> Priority: Critical
> Attachments: PIG-2938.patch
>
>
> To reproduce the issue, run:
> {code}
> ant test -Dhadoopversion=23 -Dtestcase=TestAccumulator
> {code}
> This fails with the following error:
> {code}
> Caused by: java.lang.ClassNotFoundException: org.jboss.netty.channel.group.ChannelGroup
> {code}
> This is a regression from PIG-2844 where netty is commented out from ivy.xml.
> I guess that the intention was to exclude netty from the generated pom file, but this breaks unit tests.
> I propose that we change the ivy conf of netty from "compile-> master" to "test->master" instead of commenting it out. That would prevent netty from being pulled down at compile time by 3rd party projects that consume the pig pom file.
> I am speculating here, so please correct me if I am wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PIG-2938) All unit tests that use MR2
MiniCluster are broken in trunk
Posted by "Julien Le Dem (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465798#comment-13465798 ]
Julien Le Dem commented on PIG-2938:
------------------------------------
Sorry I broke the hadoop23 build.
This looks like a hadoop 23 runtime dependency, it should be in the hadoop23 configuration in ivy.xml
any reason it is not pulled automatically?
> All unit tests that use MR2 MiniCluster are broken in trunk
> -----------------------------------------------------------
>
> Key: PIG-2938
> URL: https://issues.apache.org/jira/browse/PIG-2938
> Project: Pig
> Issue Type: Bug
> Components: build
> Reporter: Cheolsoo Park
> Assignee: Cheolsoo Park
> Priority: Critical
> Attachments: PIG-2938.patch
>
>
> To reproduce the issue, run:
> {code}
> ant test -Dhadoopversion=23 -Dtestcase=TestAccumulator
> {code}
> This fails with the following error:
> {code}
> Caused by: java.lang.ClassNotFoundException: org.jboss.netty.channel.group.ChannelGroup
> {code}
> This is a regression from PIG-2844 where netty is commented out from ivy.xml.
> I guess that the intention was to exclude netty from the generated pom file, but this breaks unit tests.
> I propose that we change the ivy conf of netty from "compile-> master" to "test->master" instead of commenting it out. That would prevent netty from being pulled down at compile time by 3rd party projects that consume the pig pom file.
> I am speculating here, so please correct me if I am wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PIG-2938) All unit tests that use MR2 MiniCluster
are broken in trunk
Posted by "Cheolsoo Park (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cheolsoo Park updated PIG-2938:
-------------------------------
Status: Patch Available (was: Open)
> All unit tests that use MR2 MiniCluster are broken in trunk
> -----------------------------------------------------------
>
> Key: PIG-2938
> URL: https://issues.apache.org/jira/browse/PIG-2938
> Project: Pig
> Issue Type: Bug
> Components: build
> Reporter: Cheolsoo Park
> Assignee: Cheolsoo Park
> Priority: Critical
> Attachments: PIG-2938.patch
>
>
> To reproduce the issue, run:
> {code}
> ant test -Dhadoopversion=23 -Dtestcase=TestAccumulator
> {code}
> This fails with the following error:
> {code}
> Caused by: java.lang.ClassNotFoundException: org.jboss.netty.channel.group.ChannelGroup
> {code}
> This is a regression from PIG-2844 where netty is commented out from ivy.xml.
> I guess that the intention was to exclude netty from the generated pom file, but this breaks unit tests.
> I propose that we change the ivy conf of netty from "compile-> master" to "test->master" instead of commenting it out. That would prevent netty from being pulled down at compile time by 3rd party projects that consume the pig pom file.
> I am speculating here, so please correct me if I am wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PIG-2938) All unit tests that use MR2
MiniCluster are broken in trunk
Posted by "Julien Le Dem (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465802#comment-13465802 ]
Julien Le Dem commented on PIG-2938:
------------------------------------
It does not look like we have a separate hadoop23 test configuration.
I guess test is better than nothing.
+1
> All unit tests that use MR2 MiniCluster are broken in trunk
> -----------------------------------------------------------
>
> Key: PIG-2938
> URL: https://issues.apache.org/jira/browse/PIG-2938
> Project: Pig
> Issue Type: Bug
> Components: build
> Reporter: Cheolsoo Park
> Assignee: Cheolsoo Park
> Priority: Critical
> Attachments: PIG-2938.patch
>
>
> To reproduce the issue, run:
> {code}
> ant test -Dhadoopversion=23 -Dtestcase=TestAccumulator
> {code}
> This fails with the following error:
> {code}
> Caused by: java.lang.ClassNotFoundException: org.jboss.netty.channel.group.ChannelGroup
> {code}
> This is a regression from PIG-2844 where netty is commented out from ivy.xml.
> I guess that the intention was to exclude netty from the generated pom file, but this breaks unit tests.
> I propose that we change the ivy conf of netty from "compile-> master" to "test->master" instead of commenting it out. That would prevent netty from being pulled down at compile time by 3rd party projects that consume the pig pom file.
> I am speculating here, so please correct me if I am wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PIG-2938) All unit tests that use MR2
MiniCluster are broken in trunk
Posted by "Cheolsoo Park (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465814#comment-13465814 ]
Cheolsoo Park commented on PIG-2938:
------------------------------------
Thanks Julien for the quick response.
I am open to suggestions, so please let me know if anyone has a better idea.
> All unit tests that use MR2 MiniCluster are broken in trunk
> -----------------------------------------------------------
>
> Key: PIG-2938
> URL: https://issues.apache.org/jira/browse/PIG-2938
> Project: Pig
> Issue Type: Bug
> Components: build
> Reporter: Cheolsoo Park
> Assignee: Cheolsoo Park
> Priority: Critical
> Attachments: PIG-2938.patch
>
>
> To reproduce the issue, run:
> {code}
> ant test -Dhadoopversion=23 -Dtestcase=TestAccumulator
> {code}
> This fails with the following error:
> {code}
> Caused by: java.lang.ClassNotFoundException: org.jboss.netty.channel.group.ChannelGroup
> {code}
> This is a regression from PIG-2844 where netty is commented out from ivy.xml.
> I guess that the intention was to exclude netty from the generated pom file, but this breaks unit tests.
> I propose that we change the ivy conf of netty from "compile-> master" to "test->master" instead of commenting it out. That would prevent netty from being pulled down at compile time by 3rd party projects that consume the pig pom file.
> I am speculating here, so please correct me if I am wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PIG-2938) All unit tests that use MR2 MiniCluster
are broken in trunk
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy V. Ryaboy updated PIG-2938:
-----------------------------------
Resolution: Fixed
Fix Version/s: 0.11
Status: Resolved (was: Patch Available)
Committed to trunk, thanks Cheolsoo.
> All unit tests that use MR2 MiniCluster are broken in trunk
> -----------------------------------------------------------
>
> Key: PIG-2938
> URL: https://issues.apache.org/jira/browse/PIG-2938
> Project: Pig
> Issue Type: Bug
> Components: build
> Reporter: Cheolsoo Park
> Assignee: Cheolsoo Park
> Priority: Critical
> Fix For: 0.11
>
> Attachments: PIG-2938.patch
>
>
> To reproduce the issue, run:
> {code}
> ant test -Dhadoopversion=23 -Dtestcase=TestAccumulator
> {code}
> This fails with the following error:
> {code}
> Caused by: java.lang.ClassNotFoundException: org.jboss.netty.channel.group.ChannelGroup
> {code}
> This is a regression from PIG-2844 where netty is commented out from ivy.xml.
> I guess that the intention was to exclude netty from the generated pom file, but this breaks unit tests.
> I propose that we change the ivy conf of netty from "compile-> master" to "test->master" instead of commenting it out. That would prevent netty from being pulled down at compile time by 3rd party projects that consume the pig pom file.
> I am speculating here, so please correct me if I am wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira