You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@yetus.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2017/03/15 20:37:41 UTC

[jira] [Comment Edited] (YETUS-495) Jenkins report shouldn't include -1 for compile report without the patch

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

Allen Wittenauer edited comment on YETUS-495 at 3/15/17 8:37 PM:
-----------------------------------------------------------------

It looks like others in that JIRA understood that Yetus reports before and after.  If one reads the text, they can see "in the (branch)" vs. "in the patch".  This signifies the before and after states.

FWIW, the overall -1 came because there were no tests that Yetus could see.


was (Author: aw):
It looks like others in that JIRA understood that Yetus reports before and after.  The overall -1 came because there were no tests that Yetus could see.

> Jenkins report shouldn't include -1 for compile report without the patch
> ------------------------------------------------------------------------
>
>                 Key: YETUS-495
>                 URL: https://issues.apache.org/jira/browse/YETUS-495
>             Project: Yetus
>          Issue Type: Bug
>          Components: Test Patch
>            Reporter: Junping Du
>            Priority: Critical
>
> In YARN-6336, the patch fixed a YARN UI build failure. However, the Jenkins report have 1 build failure and 1 build success which is confusing on which one is w/o the patch. Also, the final result still count -1 for build failure without the patch which is not right. We should fix this issue which is very confusing.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)