hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-618) Modify RM_INVALID_IDENTIFIER to a -ve number
Date Wed, 01 May 2013 23:48:18 GMT

     [ https://issues.apache.org/jira/browse/YARN-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vinod Kumar Vavilapalli updated YARN-618:
-----------------------------------------

    Attachment: YARN-618.3-branch-2.patch

The patch didn't apply cleanly against branch-2. Here's the one that I generated one myself
which compiles successfully and passes TestContainerManager which had the merge conflict.
                
> Modify RM_INVALID_IDENTIFIER to  a -ve number
> ---------------------------------------------
>
>                 Key: YARN-618
>                 URL: https://issues.apache.org/jira/browse/YARN-618
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Jian He
>            Assignee: Jian He
>         Attachments: YARN-618.1.patch, YARN-618.2.patch, YARN-618.3-branch-2.patch, YARN-618.3.patch,
YARN-618.patch
>
>
> RM_INVALID_IDENTIFIER set to 0 doesnt sound right as many tests set it to 0. Probably
a -ve number is what we want.

--
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

Mime
View raw message