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

Hadoop QA commented on YARN-8676:
---------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  8s{color} 
| {color:red} YARN-8676 does not apply to trunk. Rebase required? Wrong Branch? 
See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | YARN-8676 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12935970/YARN-8676.001.patch |
| Console output | 
https://builds.apache.org/job/PreCommit-YARN-Build/23663/console |
| Powered by | Apache Yetus 0.8.0   http://yetus.apache.org |


This message was automatically generated.



> Incorrect progress index in old yarn UI
> ---------------------------------------
>
>                 Key: YARN-8676
>                 URL: https://issues.apache.org/jira/browse/YARN-8676
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Yeliang Cang
>            Assignee: Yeliang Cang
>            Priority: Critical
>         Attachments: YARN-8676.001.patch
>
>
> The index of parseHadoopProgress index is wrong in 
> WebPageUtils#getAppsTableColumnDefs
> {code:java}
> if (isFairSchedulerPage) {
>  sb.append("[15]");
> } else if (isResourceManager) {
>  sb.append("[17]");
> } else {
>  sb.append("[9]");
> }
> {code}
> should be
> {code:java}
> if (isFairSchedulerPage) {
>  sb.append("[16]");
> } else if (isResourceManager) {
>  sb.append("[18]");
> } else {
>  sb.append("[11]");
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to