[jira] [Commented] (YARN-1615) Fix typos in FSSchedulerApp.java

2015-01-29 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297810#comment-14297810
 ] 

Hadoop QA commented on YARN-1615:
-

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12623903/YARN-1615.patch
  against trunk revision 3f982c5.

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6461//console

This message is automatically generated.

> Fix typos in FSSchedulerApp.java
> 
>
> Key: YARN-1615
> URL: https://issues.apache.org/jira/browse/YARN-1615
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: documentation, scheduler
>Affects Versions: 2.2.0
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Trivial
>  Labels: newbie
> Attachments: YARN-1615.patch
>
>
> In FSSchedulerApp.java there're 4 typos:
> {code}
>* containers over rack-local or off-switch containers. To acheive this
>* we first only allow node-local assigments for a given prioirty level,
>* then relax the locality threshold once we've had a long enough period
>* without succesfully scheduling. We measure both the number of "missed"
> {code}
> They should be fixed as follows:
> {code}
>* containers over rack-local or off-switch containers. To achieve this
>* we first only allow node-local assignments for a given priority level,
>* then relax the locality threshold once we've had a long enough period
>* without successfully scheduling. We measure both the number of "missed"
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (YARN-1615) Fix typos in FSSchedulerApp.java

2014-09-26 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14150186#comment-14150186
 ] 

Hadoop QA commented on YARN-1615:
-

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12623903/YARN-1615.patch
  against trunk revision 6b7673e.

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5157//console

This message is automatically generated.

> Fix typos in FSSchedulerApp.java
> 
>
> Key: YARN-1615
> URL: https://issues.apache.org/jira/browse/YARN-1615
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: documentation, scheduler
>Affects Versions: 2.2.0
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Trivial
>  Labels: newbie
> Attachments: YARN-1615.patch
>
>
> In FSSchedulerApp.java there're 4 typos:
> {code}
>* containers over rack-local or off-switch containers. To acheive this
>* we first only allow node-local assigments for a given prioirty level,
>* then relax the locality threshold once we've had a long enough period
>* without succesfully scheduling. We measure both the number of "missed"
> {code}
> They should be fixed as follows:
> {code}
>* containers over rack-local or off-switch containers. To achieve this
>* we first only allow node-local assignments for a given priority level,
>* then relax the locality threshold once we've had a long enough period
>* without successfully scheduling. We measure both the number of "missed"
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (YARN-1615) Fix typos in FSSchedulerApp.java

2014-01-19 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876179#comment-13876179
 ] 

Hadoop QA commented on YARN-1615:
-

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12623903/YARN-1615.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+0 tests included{color}.  The patch appears to be a 
documentation patch that doesn't require tests.

{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:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/2913//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2913//console

This message is automatically generated.

> Fix typos in FSSchedulerApp.java
> 
>
> Key: YARN-1615
> URL: https://issues.apache.org/jira/browse/YARN-1615
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: documentation, scheduler
>Affects Versions: 2.2.0
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Trivial
>  Labels: newbie
> Attachments: YARN-1615.patch
>
>
> In FSSchedulerApp.java there're 4 typos:
> {code}
>* containers over rack-local or off-switch containers. To acheive this
>* we first only allow node-local assigments for a given prioirty level,
>* then relax the locality threshold once we've had a long enough period
>* without succesfully scheduling. We measure both the number of "missed"
> {code}
> They should be fixed as follows:
> {code}
>* containers over rack-local or off-switch containers. To achieve this
>* we first only allow node-local assignments for a given priority level,
>* then relax the locality threshold once we've had a long enough period
>* without successfully scheduling. We measure both the number of "missed"
> {code}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)