[
https://issues.apache.org/jira/browse/YETUS-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982406#comment-15982406
]
Akira Ajisaka commented on YETUS-500:
-------------------------------------
Adding the subheaders looks great and I'm personally +1 for the last type of
subheaders (precheck, branch compile tests, patch compile tests, other tests).
bq. People who complain about the length of the report vs. our inability to
communicate what is happening to new users.
I'm thinking it depends on the projects, so providing some options to configure
the subheaders seems fine.
bq. Also: in the case of findbugs output, I have a hunch most people don't know
what the word "extant" means.
I saw the word "extant" in the output for the first time, so maybe you are
right. "existing" seems more plain.
> 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
>
> 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)
