[
https://issues.apache.org/jira/browse/YETUS-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018219#comment-16018219
]
Yetus QA commented on YETUS-500:
--------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 14m
52s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
|| || || || {color:brown} Compile Tests {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:red}-1{color} | {color:red} shellcheck {color} | {color:red} 0m
8s{color} | {color:red} The patch generated 4 new + 64 unchanged - 0 fixed = 68
total (was 64) {color} |
| {color:green}+1{color} | {color:green} shelldocs {color} | {color:green} 0m
0s{color} | {color:green} The patch generated 0 new + 0 unchanged - 36 fixed =
0 total (was 36) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
0s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 15m 8s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/yetus:e4e4903 |
| JIRA Issue | YETUS-500 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12869079/YETUS-500.01.patch |
| Optional Tests | shellcheck shelldocs |
| uname | Linux 6df65ac7781b 3.13.0-105-generic #152-Ubuntu SMP Fri Dec 2
15:37:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | nobuild |
| git revision | master / 3cba029 |
| shellcheck | v0.4.6 |
| shellcheck |
https://builds.apache.org/job/PreCommit-YETUS-Build/568/artifact/patchprocess/diff-patch-shellcheck.txt
|
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-YETUS-Build/568/console |
| Powered by | Apache Yetus 0.5.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> 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, YETUS-500.01.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)
