[jira] [Commented] (YETUS-500) Users are confused by precheck/compile cycle in precommit output

["Yetus QA (JIRA)" <ji...@apache.org>]

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

Yetus QA commented on YETUS-500:
--------------------------------

(!) A patch to the testing environment has been detected. 
Re-executing against the patched versions to perform further tests. 
The console is at https://builds.apache.org/job/PreCommit-YETUS-Build/566/console in case of problems.


> 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
>    Affects Versions: 0.5.0
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>         Attachments: YETUS-500.00.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.3.15#6346)