[
https://issues.apache.org/jira/browse/YARN-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878176#comment-13878176
]
Hadoop QA commented on YARN-1624:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12624257/diff.txt
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The following test timeouts occurred in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.yarn.server.resourcemanager.TestResourceTrackerService
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/2923//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2923//console
This message is automatically generated.
> QueuePlacementPolicy format is not easily readable via a JAXB parser
> --------------------------------------------------------------------
>
> Key: YARN-1624
> URL: https://issues.apache.org/jira/browse/YARN-1624
> Project: Hadoop YARN
> Issue Type: Bug
> Components: scheduler
> Affects Versions: 2.2.0
> Reporter: Aditya Acharya
> Attachments: diff.txt
>
>
> The current format for specifying queue placement rules in the fair scheduler
> allocations file does not lend itself to easy parsing via a JAXB parser. In
> particular, relying on the tag name to encode information about which rule to
> use makes it very difficult for an xsd-based JAXB parser to preserve the
> order of the rules, which is essential.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
