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

genericqa commented on YARN-6995:
---------------------------------

| (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} docker {color} | {color:red} 12m 
37s{color} | {color:red} Docker failed to build yetus/hadoop:abb62dd. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | YARN-6995 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12931927/YARN-6995.008.patch |
| Console output | 
https://builds.apache.org/job/PreCommit-YARN-Build/21272/console |
| Powered by | Apache Yetus 0.8.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> Improve use of ResourceNotFoundException in resource types code
> ---------------------------------------------------------------
>
>                 Key: YARN-6995
>                 URL: https://issues.apache.org/jira/browse/YARN-6995
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager, resourcemanager
>            Reporter: Daniel Templeton
>            Assignee: Szilard Nemeth
>            Priority: Minor
>         Attachments: YARN-6995.005.patch, YARN-6995.006.patch, 
> YARN-6995.007.patch, YARN-6995.008.patch, YARN-6995.YARN-3926.001.patch, 
> YARN-6995.YARN-3926.002.patch, YARN-6995.YARN-3926.003.patch, 
> YARN-6995.YARN-3926.004.patch
>
>
> Now that all the YarnExceptions have been replaced with 
> ResourceNotFoundExceptions, we should make the ResourceNotFoundExceptions as 
> useful as possible.



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