[ 
https://issues.apache.org/jira/browse/YETUS-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Busbey updated YETUS-500:
------------------------------
    Component/s: Test Patch

> Users are confused by precheck/compile cycle in precommit output
> ----------------------------------------------------------------
>
>                 Key: YETUS-500
>                 URL: https://issues.apache.org/jira/browse/YETUS-500
>             Project: Yetus
>          Issue Type: Improvement
>          Components: Test Patch
>    Affects Versions: 0.5.0
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>         Attachments: YETUS-500.00.patch, YETUS-500.01.patch, 
> YETUS-500.02.patch
>
>
> Every few weeks there is a question in JIRA issues asking why the result is 
> still failed despite them working on fixing said result.  e.g.  master branch 
> has spotbug issues, this patch fixes them, why is it still saying -1?
> I think we could curb a lot of these questions by figuring out how to put 
> "subheaders" into the precommit output in patch testing mode.  
> See below for some ideas.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to