hadoop common build fails creating docs
---
Key: HADOOP-7517
URL: https://issues.apache.org/jira/browse/HADOOP-7517
Project: Hadoop Common
Issue Type: Bug
Components: build
Reporter:
Unable to start HDFS cluster on trunk (after the common mavenisation)
-
Key: HADOOP-7518
URL: https://issues.apache.org/jira/browse/HADOOP-7518
Project: Hadoop Common
Issue
[
https://issues.apache.org/jira/browse/HADOOP-7515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-7515.
---
Resolution: Fixed
Hadoop Flags: [Reviewed]
I've just committed this.
> test-patch reports the
hadoop fs commands should support tar/gzip or an equivalent
---
Key: HADOOP-7519
URL: https://issues.apache.org/jira/browse/HADOOP-7519
Project: Hadoop Common
Issue Type: Improvement
hadoop-main fails to deploy
---
Key: HADOOP-7520
URL: https://issues.apache.org/jira/browse/HADOOP-7520
Project: Hadoop Common
Issue Type: Bug
Components: build
Affects Versions: 0.23.0
Repor
[
https://issues.apache.org/jira/browse/HADOOP-7516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Srinivas resolved HADOOP-7516.
-
Resolution: Not A Problem
HDFS-7515 takes care of the issue reported here.
> Mavenized
bintar created tarball should use a common directory for prefix
---
Key: HADOOP-7521
URL: https://issues.apache.org/jira/browse/HADOOP-7521
Project: Hadoop Common
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HADOOP-7517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giridharan Kesavan resolved HADOOP-7517.
Resolution: Not A Problem
> hadoop common build fails creating docs
>
Please unsubscribe me. Thanks.
Kind regards,
Arindam Khaled
On Aug 4, 2011, at 4:23 PM, Alejandro Abdelnur wrote:
Allen,
I agree 100% with you, there will be setups that will break. I was
just
pointing out that it may be a bit less that expected because of the
scenarios I described.
Hi folks,
Now that the build machines are available again, I tried resubmitting a patch
to https://issues.apache.org/jira/browse/MAPREDUCE-2767. However, it looks like
it is not being picked up by CI.
Is 0.22 branch excluded from hadoop CI ?
* Milind
---
Milind Bhandarkar
Greenplum Labs,
Milind,
patch testing usually happens only on trunk
thanks,
Giri
On Fri, Aug 5, 2011 at 3:11 PM, wrote:
> Hi folks,
>
> Now that the build machines are available again, I tried resubmitting a
> patch to https://issues.apache.org/jira/browse/MAPREDUCE-2767. However, it
> looks like it is not b
Aha!
In that case, is the local test-patch success sufficient for patches on
branches ?
- milind
On 8/5/11 3:38 PM, "Giridharan Kesavan" wrote:
>Milind,
>
>patch testing usually happens only on trunk
>
>
>thanks,
>Giri
>
>On Fri, Aug 5, 2011 at 3:11 PM, wrote:
>
>> Hi folks,
>>
>> Now that th
Yes, with usual +1 vote thing.
Cos
On Fri, Aug 05, 2011 at 07:02PM, milind.bhandar...@emc.com wrote:
> Aha!
>
> In that case, is the local test-patch success sufficient for patches on
> branches ?
>
> - milind
>
> On 8/5/11 3:38 PM, "Giridharan Kesavan" wrote:
>
> >Milind,
> >
> >patch testi
Abandon support for expanding ${user.name} in configs
-
Key: HADOOP-7522
URL: https://issues.apache.org/jira/browse/HADOOP-7522
Project: Hadoop Common
Issue Type: Wish
Components:
I believe the usual practice should be:
1. The trunk patch (if applicable) must pass automated Jenkins testing for
trunk CI build, and code review.
2. The branch patch should have "ant -Dpatch.file= test-patch"
run against it in the developer's build environment for the branch, and the
passing res
15 matches
Mail list logo