[jira] [Created] (MAPREDUCE-6057) Remove obsolete entries from mapred-default.xml

Ray Chiang created MAPREDUCE-6057: - Summary: Remove obsolete entries from mapred-default.xml Key: MAPREDUCE-6057 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6057 Project: Hadoop Map/Reduce

Re: Updates on migration to git

Thanks for making this happen, Karthik and Daniel. Great job. best, Colin On Tue, Aug 26, 2014 at 5:59 PM, Karthik Kambatla wrote: > Yes, we have requested for force-push disabled on trunk and branch-* > branches. I didn't test it though :P, it is not writable yet. > > > On Tue, Aug 26, 2014 at

[jira] [Resolved] (MAPREDUCE-6054) native-task: speed up test runs

[ https://issues.apache.org/jira/browse/MAPREDUCE-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved MAPREDUCE-6054. Resolution: Fixed Hadoop Flags: Reviewed Committed to the branch. I agree, let's

[jira] [Resolved] (MAPREDUCE-5977) Fix or suppress native-task gcc warnings

[ https://issues.apache.org/jira/browse/MAPREDUCE-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved MAPREDUCE-5977. Resolution: Fixed Hadoop Flags: Reviewed Committed to branch (via git). Thanks, M

[jira] [Resolved] (MAPREDUCE-6043) Lost messages from RM to MRAppMaster

[ https://issues.apache.org/jira/browse/MAPREDUCE-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maysam Yabandeh resolved MAPREDUCE-6043. Resolution: Invalid > Lost messages from RM to MRAppMaster > --

Re: Git repo ready to use

svngit2jira would write a message like this - https://issues.apache.org/jira/browse/CLOUDSTACK-1638?focusedCommentId=13714929&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13714929 with a link to the commit like this - https://git-wip-us.apache.org/repos/asf?p=clouds

Re: Git repo ready to use

It appears the comments from Hudson on our JIRAs (post commits) are not setup by the INFRA team. Do we use any other scripts for this? If yes, do we want to fix those scripts or use svngit2jira? On Wed, Aug 27, 2014 at 10:18 AM, Karthik Kambatla wrote: > The emails for commits apparently all go

Re: Git repo ready to use

The emails for commits apparently all go to common-commits@, irrespective of the project. Apparently, the git filtering is not as good as svn filtering. Daniel offered to look into alternatives this coming weekend. I filed INFRA-8250 to restore updates to JIRA on commits. On Wed, Aug 27, 2014 at

Hadoop-Mapreduce-trunk - Build # 1876 - Still Failing

See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1876/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 35715 lines...] Tests run: 1, Failures: 0, Errors: 0

[jira] [Created] (MAPREDUCE-6056) nativetask: move system test working dir to target dir and cleanup test config xml files

Binglin Chang created MAPREDUCE-6056: Summary: nativetask: move system test working dir to target dir and cleanup test config xml files Key: MAPREDUCE-6056 URL: https://issues.apache.org/jira/browse/MAPREDUCE-

Re: Git repo ready to use

Committed YARN-2035 successfully via git. Email notification seems to work already. On Wed, Aug 27, 2014 at 1:40 AM, Karthik Kambatla wrote: > Oh.. a couple more things. > > The git commit hashes have changed and are different from what we had on > our github. This might interfere with any buil

Re: Git repo ready to use

Oh.. a couple more things. The git commit hashes have changed and are different from what we had on our github. This might interfere with any build automations that folks have. Another follow-up item: email and JIRA integration On Wed, Aug 27, 2014 at 1:33 AM, Karthik Kambatla wrote: > Hi fol

Git repo ready to use

Hi folks, I am very excited to let you know that the git repo is now writable. I committed a few changes (CHANGES.txt fixes and branching for 2.5.1) and everything looks good. Current status: 1. All branches have the same names, including trunk. 2. Force push is disabled on trunk, branch-2