[jira] [Commented] (YETUS-833) start-build-env is failing

2019-04-05 Thread Yetus QA (JIRA)


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

Yetus QA commented on YETUS-833:


| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
46s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} dupname {color} | {color:green}  0m  
0s{color} | {color:green} No case conflicting files found. {color} |
| {color:blue}0{color} | {color:blue} shelldocs {color} | {color:blue}  0m  
0s{color} | {color:blue} Shelldocs was not available. {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} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m  
4s{color} | {color:blue} Maven dependency ordering for branch {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m  
4s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} hadolint {color} | {color:green}  0m  
2s{color} | {color:green} There were no new hadolint issues. {color} |
| {color:green}+1{color} | {color:green} shellcheck {color} | {color:green}  0m 
 0s{color} | {color:green} There were no new shellcheck issues. {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 
13s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}  1m 25s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce base: 
https://builds.apache.org/job/PreCommit-YETUS-Build/997/artifact/patchprocess/Dockerfile
 |
| JIRA Issue | YETUS-833 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12965066/YETUS-833.01.patch |
| Optional Tests | dupname asflicense hadolint shellcheck shelldocs |
| uname | Linux 4cbec41fdbd2 4.4.0-137-generic #163-Ubuntu SMP Mon Sep 24 
13:14:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | precommit/src/main/shell/personality/yetus.sh |
| git revision | master / e113117 |
| maven | version: Apache Maven 3.3.9 |
| shellcheck | v0.6.0 |
| Max. process+thread count | 48 (vs. ulimit of 1000) |
| modules | C: asf-site-src . U: . |
| Console output | 
https://builds.apache.org/job/PreCommit-YETUS-Build/997/console |
| Powered by | Apache Yetus 0.10.0-SNAPSHOT http://yetus.apache.org |


This message was automatically generated.



> start-build-env is failing
> --
>
> Key: YETUS-833
> URL: https://issues.apache.org/jira/browse/YETUS-833
> Project: Yetus
>  Issue Type: Bug
>  Components: build
>Reporter: Allen Wittenauer
>Assignee: Allen Wittenauer
>Priority: Major
> Attachments: YETUS-833.00.patch, YETUS-833.01.patch
>
>
> From the way it appears, the apache/yetus-base image is getting the last RUN 
> statement treated as a CMD statement:
> {code}
> $ docker inspect  apache/yetus-build-501:master
> ...
> "Cmd": [
> "/bin/bash",
> "-o",
> "pipefail",
> "-c",
> "apt-get -q update && apt-get -q install 
> --no-install-recommends -y nodejs npm && apt-get clean && rm -rf 
> /var/lib/apt/lists/* && ln -s /usr/bin/nodejs /usr/bin/node && npm 
> install -g npm@latest && npm install -g jshint"
> ],
> ...
> {code}
> This might be a bug with hub.docker.com. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (YETUS-833) start-build-env is failing

2019-04-05 Thread Yetus QA (JIRA)


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

Yetus QA commented on YETUS-833:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  3m  
2s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} dupname {color} | {color:green}  0m  
0s{color} | {color:green} No case conflicting files found. {color} |
| {color:blue}0{color} | {color:blue} shelldocs {color} | {color:blue}  0m  
0s{color} | {color:blue} Shelldocs was not available. {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} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m  
7s{color} | {color:blue} Maven dependency ordering for branch {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m  
4s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} hadolint {color} | {color:green}  0m  
0s{color} | {color:green} There were no new hadolint issues. {color} |
| {color:red}-1{color} | {color:red} shellcheck {color} | {color:red}  0m  
1s{color} | {color:red} The patch generated 1 new + 0 unchanged - 0 fixed = 1 
total (was 0) {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 
12s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}  3m 46s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce base: 
https://builds.apache.org/job/PreCommit-YETUS-Build/996/artifact/patchprocess/Dockerfile
 |
| JIRA Issue | YETUS-833 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12965061/YETUS-833.00.patch |
| Optional Tests | dupname asflicense hadolint shellcheck shelldocs |
| uname | Linux 327c3ab74de4 4.4.0-137-generic #163-Ubuntu SMP Mon Sep 24 
13:14:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | precommit/src/main/shell/personality/yetus.sh |
| git revision | master / e113117 |
| maven | version: Apache Maven 3.3.9 |
| shellcheck | v0.6.0 |
| shellcheck | 
https://builds.apache.org/job/PreCommit-YETUS-Build/996/artifact/patchprocess/diff-patch-shellcheck.txt
 |
| Max. process+thread count | 47 (vs. ulimit of 1000) |
| modules | C: asf-site-src . U: . |
| Console output | 
https://builds.apache.org/job/PreCommit-YETUS-Build/996/console |
| Powered by | Apache Yetus 0.10.0-SNAPSHOT http://yetus.apache.org |


This message was automatically generated.



> start-build-env is failing
> --
>
> Key: YETUS-833
> URL: https://issues.apache.org/jira/browse/YETUS-833
> Project: Yetus
>  Issue Type: Bug
>  Components: build
>Reporter: Allen Wittenauer
>Assignee: Allen Wittenauer
>Priority: Major
> Attachments: YETUS-833.00.patch
>
>
> From the way it appears, the apache/yetus-base image is getting the last RUN 
> statement treated as a CMD statement:
> {code}
> $ docker inspect  apache/yetus-build-501:master
> ...
> "Cmd": [
> "/bin/bash",
> "-o",
> "pipefail",
> "-c",
> "apt-get -q update && apt-get -q install 
> --no-install-recommends -y nodejs npm && apt-get clean && rm -rf 
> /var/lib/apt/lists/* && ln -s /usr/bin/nodejs /usr/bin/node && npm 
> install -g npm@latest && npm install -g jshint"
> ],
> ...
> {code}
> This might be a bug with hub.docker.com. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (YETUS-833) start-build-env is failing

2019-04-05 Thread Allen Wittenauer (JIRA)


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

Allen Wittenauer commented on YETUS-833:


-00:
* I give up.

> start-build-env is failing
> --
>
> Key: YETUS-833
> URL: https://issues.apache.org/jira/browse/YETUS-833
> Project: Yetus
>  Issue Type: Bug
>  Components: build
>Reporter: Allen Wittenauer
>Assignee: Allen Wittenauer
>Priority: Major
> Attachments: YETUS-833.00.patch
>
>
> From the way it appears, the apache/yetus-base image is getting the last RUN 
> statement treated as a CMD statement:
> {code}
> $ docker inspect  apache/yetus-build-501:master
> ...
> "Cmd": [
> "/bin/bash",
> "-o",
> "pipefail",
> "-c",
> "apt-get -q update && apt-get -q install 
> --no-install-recommends -y nodejs npm && apt-get clean && rm -rf 
> /var/lib/apt/lists/* && ln -s /usr/bin/nodejs /usr/bin/node && npm 
> install -g npm@latest && npm install -g jshint"
> ],
> ...
> {code}
> This might be a bug with hub.docker.com. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)