[jira] [Commented] (YETUS-176) hadoop: mvn site tests aren't getting run
[
https://issues.apache.org/jira/browse/YETUS-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15009825#comment-15009825
]
Yetus QA commented on YETUS-176:
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 3s
{color} | {color:blue} precommit patch detected. {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: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} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
1s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 0m 7s {color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12772860/YETUS-176.00.patch |
| JIRA Issue | YETUS-176 |
| Optional Tests | asflicense shellcheck |
| uname | Linux penates.apache.org 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT
Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | nobuild |
| git revision | master / 87014f4 |
| Default Java | 1.7.0_80 |
| shellcheck | v0.3.3 (This is an old version that has serious bugs. Consider
upgrading.) |
| modules | C: U: |
| Powered by | Apache Yetus http://yetus.apache.org |
| Console output |
https://builds.apache.org/job/PreCommit-YETUS-Build/101/console |
This message was automatically generated.
> hadoop: mvn site tests aren't getting run
> -
>
> Key: YETUS-176
> URL: https://issues.apache.org/jira/browse/YETUS-176
> Project: Yetus
> Issue Type: Bug
> Components: Test Patch
>Reporter: Allen Wittenauer
>Assignee: Allen Wittenauer
>Priority: Blocker
> Attachments: YETUS-176.00.patch
>
>
> It doesn't appear that mvn site tests are getting executed at all anymore.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (YETUS-176) hadoop: mvn site tests aren't getting run
[ https://issues.apache.org/jira/browse/YETUS-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15009824#comment-15009824 ] Yetus QA commented on YETUS-176: (!) 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/101/console in case of problems. > hadoop: mvn site tests aren't getting run > - > > Key: YETUS-176 > URL: https://issues.apache.org/jira/browse/YETUS-176 > Project: Yetus > Issue Type: Bug > Components: Test Patch >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Blocker > Attachments: YETUS-176.00.patch > > > It doesn't appear that mvn site tests are getting executed at all anymore. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YETUS-176) hadoop: mvn site tests aren't getting run
[ https://issues.apache.org/jira/browse/YETUS-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-176: --- Attachment: YETUS-176.00.patch -00: * updates to the hadoop personality > hadoop: mvn site tests aren't getting run > - > > Key: YETUS-176 > URL: https://issues.apache.org/jira/browse/YETUS-176 > Project: Yetus > Issue Type: Bug > Components: Test Patch >Reporter: Allen Wittenauer >Priority: Blocker > Attachments: YETUS-176.00.patch > > > It doesn't appear that mvn site tests are getting executed at all anymore. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (YETUS-176) hadoop: mvn site tests aren't getting run
[ https://issues.apache.org/jira/browse/YETUS-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer reassigned YETUS-176: -- Assignee: Allen Wittenauer > hadoop: mvn site tests aren't getting run > - > > Key: YETUS-176 > URL: https://issues.apache.org/jira/browse/YETUS-176 > Project: Yetus > Issue Type: Bug > Components: Test Patch >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Blocker > Attachments: YETUS-176.00.patch > > > It doesn't appear that mvn site tests are getting executed at all anymore. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YETUS-123) Various Docker mode fixes: plug-in issues, local patch file problems, availability, & Dockerfile re-usability
[ https://issues.apache.org/jira/browse/YETUS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010081#comment-15010081 ] Kengo Seki commented on YETUS-123: -- I confirmed all comments are addressed. +1. > Various Docker mode fixes: plug-in issues, local patch file problems, > availability, & Dockerfile re-usability > - > > Key: YETUS-123 > URL: https://issues.apache.org/jira/browse/YETUS-123 > Project: Yetus > Issue Type: Bug > Components: Test Patch >Affects Versions: 0.1.0 >Reporter: Sean Busbey >Assignee: Allen Wittenauer >Priority: Critical > Fix For: YETUS-83 > > Attachments: YETUS-123.00.patch, YETUS-123.01.patch, > YETUS-123.02.patch, YETUS-123.03.patch, YETUS-123.04.patch, > YETUS-123.05.patch, YETUS-123.06.patch, YETUS-123.07.patch > > > I've made three goes at running in docker mode and all fail in a way that > suggests the set of plugins isn't making it over to the docker invocation. > since hadoop is working, I guess there's something that presumes a > personality will be used? > builds: > * > [13|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/13] > * > [14|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/14] > * > [28|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/28] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YETUS-123) Various Docker mode fixes: plug-in issues, local patch file problems, availability, & Dockerfile re-usability
[ https://issues.apache.org/jira/browse/YETUS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010241#comment-15010241 ] Allen Wittenauer commented on YETUS-123: Assuming test-patch passes this, I'll commit. Thanks for the reviews everyone. :) > Various Docker mode fixes: plug-in issues, local patch file problems, > availability, & Dockerfile re-usability > - > > Key: YETUS-123 > URL: https://issues.apache.org/jira/browse/YETUS-123 > Project: Yetus > Issue Type: Bug > Components: Test Patch >Affects Versions: 0.1.0 >Reporter: Sean Busbey >Assignee: Allen Wittenauer >Priority: Critical > Fix For: YETUS-83 > > Attachments: YETUS-123.00.patch, YETUS-123.01.patch, > YETUS-123.02.patch, YETUS-123.03.patch, YETUS-123.04.patch, > YETUS-123.05.patch, YETUS-123.06.patch, YETUS-123.07.patch, YETUS-123.08.patch > > > I've made three goes at running in docker mode and all fail in a way that > suggests the set of plugins isn't making it over to the docker invocation. > since hadoop is working, I guess there's something that presumes a > personality will be used? > builds: > * > [13|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/13] > * > [14|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/14] > * > [28|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/28] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YETUS-123) Various Docker mode fixes: plug-in issues, local patch file problems, availability, & Dockerfile re-usability
[ https://issues.apache.org/jira/browse/YETUS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-123: --- Attachment: YETUS-123.08.patch -08: * fix some shellcheck issues, other than the one that's too icky to fix. > Various Docker mode fixes: plug-in issues, local patch file problems, > availability, & Dockerfile re-usability > - > > Key: YETUS-123 > URL: https://issues.apache.org/jira/browse/YETUS-123 > Project: Yetus > Issue Type: Bug > Components: Test Patch >Affects Versions: 0.1.0 >Reporter: Sean Busbey >Assignee: Allen Wittenauer >Priority: Critical > Fix For: YETUS-83 > > Attachments: YETUS-123.00.patch, YETUS-123.01.patch, > YETUS-123.02.patch, YETUS-123.03.patch, YETUS-123.04.patch, > YETUS-123.05.patch, YETUS-123.06.patch, YETUS-123.07.patch, YETUS-123.08.patch > > > I've made three goes at running in docker mode and all fail in a way that > suggests the set of plugins isn't making it over to the docker invocation. > since hadoop is working, I guess there's something that presumes a > personality will be used? > builds: > * > [13|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/13] > * > [14|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/14] > * > [28|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/28] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YETUS-123) Various Docker mode fixes: plug-in issues, local patch file problems, availability, & Dockerfile re-usability
[ https://issues.apache.org/jira/browse/YETUS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010249#comment-15010249 ] Yetus QA commented on YETUS-123: (!) 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/102/console in case of problems. > Various Docker mode fixes: plug-in issues, local patch file problems, > availability, & Dockerfile re-usability > - > > Key: YETUS-123 > URL: https://issues.apache.org/jira/browse/YETUS-123 > Project: Yetus > Issue Type: Bug > Components: Test Patch >Affects Versions: 0.1.0 >Reporter: Sean Busbey >Assignee: Allen Wittenauer >Priority: Critical > Fix For: YETUS-83 > > Attachments: YETUS-123.00.patch, YETUS-123.01.patch, > YETUS-123.02.patch, YETUS-123.03.patch, YETUS-123.04.patch, > YETUS-123.05.patch, YETUS-123.06.patch, YETUS-123.07.patch, YETUS-123.08.patch > > > I've made three goes at running in docker mode and all fail in a way that > suggests the set of plugins isn't making it over to the docker invocation. > since hadoop is working, I guess there's something that presumes a > personality will be used? > builds: > * > [13|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/13] > * > [14|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/14] > * > [28|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/28] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YETUS-123) Various Docker mode fixes: plug-in issues, local patch file problems, availability, & Dockerfile re-usability
[
https://issues.apache.org/jira/browse/YETUS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010250#comment-15010250
]
Yetus QA commented on YETUS-123:
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s
{color} | {color:blue} Precommit patch detected. {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:red}-1{color} | {color:red} shellcheck {color} | {color:red} 0m 2s
{color} | {color:red} The applied patch generated 1 new shellcheck issues
(total was 4, now 5). {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
0s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 0m 10s {color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12772919/YETUS-123.08.patch |
| JIRA Issue | YETUS-123 |
| Optional Tests | asflicense shellcheck |
| uname | Linux pomona.apache.org 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT
Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | nobuild |
| git revision | master / 87014f4 |
| shellcheck | v0.3.3 (This is an old version that has serious bugs. Consider
upgrading.) |
| shellcheck |
https://builds.apache.org/job/PreCommit-YETUS-Build/102/artifact/patchprocess/diff-patch-shellcheck.txt
|
| modules | C: U: |
| Powered by | Apache Yetus http://yetus.apache.org |
| Console output |
https://builds.apache.org/job/PreCommit-YETUS-Build/102/console |
This message was automatically generated.
> Various Docker mode fixes: plug-in issues, local patch file problems,
> availability, & Dockerfile re-usability
> -
>
> Key: YETUS-123
> URL: https://issues.apache.org/jira/browse/YETUS-123
> Project: Yetus
> Issue Type: Bug
> Components: Test Patch
>Affects Versions: 0.1.0
>Reporter: Sean Busbey
>Assignee: Allen Wittenauer
>Priority: Critical
> Fix For: YETUS-83
>
> Attachments: YETUS-123.00.patch, YETUS-123.01.patch,
> YETUS-123.02.patch, YETUS-123.03.patch, YETUS-123.04.patch,
> YETUS-123.05.patch, YETUS-123.06.patch, YETUS-123.07.patch, YETUS-123.08.patch
>
>
> I've made three goes at running in docker mode and all fail in a way that
> suggests the set of plugins isn't making it over to the docker invocation.
> since hadoop is working, I guess there's something that presumes a
> personality will be used?
> builds:
> *
> [13|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/13]
> *
> [14|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/14]
> *
> [28|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/28]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (YETUS-176) hadoop: mvn site tests aren't getting run
[ https://issues.apache.org/jira/browse/YETUS-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010291#comment-15010291 ] Sean Busbey commented on YETUS-176: --- +1 looks reasonable. > hadoop: mvn site tests aren't getting run > - > > Key: YETUS-176 > URL: https://issues.apache.org/jira/browse/YETUS-176 > Project: Yetus > Issue Type: Bug > Components: Test Patch >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Blocker > Attachments: YETUS-176.00.patch > > > It doesn't appear that mvn site tests are getting executed at all anymore. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YETUS-171) patches that don't apply are not getting reported back to JIRA
[ https://issues.apache.org/jira/browse/YETUS-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010303#comment-15010303 ] Allen Wittenauer commented on YETUS-171: Yes, definitely. I just saw it today. > patches that don't apply are not getting reported back to JIRA > -- > > Key: YETUS-171 > URL: https://issues.apache.org/jira/browse/YETUS-171 > Project: Yetus > Issue Type: Bug > Components: Test Patch >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Blocker > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YETUS-186) non-existent dockerfile should fail or fallback
[ https://issues.apache.org/jira/browse/YETUS-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010302#comment-15010302 ] Allen Wittenauer commented on YETUS-186: We have a few options here: * fail * don't spawn docker * spawn docker, but use our image instead I think failing and reporting it back up the chain is the correct thing to do since if docker is being invoked, there is a good chance the whole build would have failed anyway. > non-existent dockerfile should fail or fallback > --- > > Key: YETUS-186 > URL: https://issues.apache.org/jira/browse/YETUS-186 > Project: Yetus > Issue Type: Bug > Components: Test Patch >Reporter: Allen Wittenauer >Priority: Blocker > > This is a long standing bug that I just now noticed. :( If the > \-\-dockerfile param points to a file that doesn't actually exist, bad things > happen. Which particular bad thing depends greatly upon what other images > are already installed, but the vast majority end up with a stuck container at > a bash prompt. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YETUS-187) javac can't use calcdiffs
Allen Wittenauer created YETUS-187: -- Summary: javac can't use calcdiffs Key: YETUS-187 URL: https://issues.apache.org/jira/browse/YETUS-187 Project: Yetus Issue Type: Bug Reporter: Allen Wittenauer javac goes through generic which uses calcdiffs. except, at least in maven, javac diffs aren't compatible with calcdiffs, so we report problems that are false positives. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YETUS-188) shelldoc generated docs have lines that end in whitespace
Sean Busbey created YETUS-188: - Summary: shelldoc generated docs have lines that end in whitespace Key: YETUS-188 URL: https://issues.apache.org/jira/browse/YETUS-188 Project: Yetus Issue Type: Bug Components: ShellDocs Affects Versions: 0.1.0 Reporter: Sean Busbey Priority: Minor the markdown created by shelldocs has lines that end in whitespace. see precommit runs from YETUS-81 for example. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YETUS-81) Publish generated apidocs on website
[ https://issues.apache.org/jira/browse/YETUS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010398#comment-15010398 ] Allen Wittenauer commented on YETUS-81: --- awesome. +1 > Publish generated apidocs on website > > > Key: YETUS-81 > URL: https://issues.apache.org/jira/browse/YETUS-81 > Project: Yetus > Issue Type: Improvement > Components: Audience Annotations, Test Patch, website and > documentation >Affects Versions: 0.1.0 >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Critical > Attachments: YETUS-81.0.patch, YETUS-81.1.patch > > > we should publish the javadocs for the IA.Public parts of the project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YETUS-163) parameterize site for releases
[ https://issues.apache.org/jira/browse/YETUS-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated YETUS-163: -- Attachment: YETUS-163.2.patch -02 * rebase * include link to CHANGES * run releasedocmaker when versions are defined. > parameterize site for releases > -- > > Key: YETUS-163 > URL: https://issues.apache.org/jira/browse/YETUS-163 > Project: Yetus > Issue Type: Improvement > Components: website and documentation >Affects Versions: 0.1.0 >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Blocker > Attachments: YETUS-163.0.patch, YETUS-163.1.patch, YETUS-163.2.patch > > > our site needs to handle having releases, i.e. downloads and version specific > documentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YETUS-123) Various Docker mode fixes: plug-in issues, local patch file problems, availability, & Dockerfile re-usability
[ https://issues.apache.org/jira/browse/YETUS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YETUS-123: --- Attachment: YETUS-123.07.patch > Various Docker mode fixes: plug-in issues, local patch file problems, > availability, & Dockerfile re-usability > - > > Key: YETUS-123 > URL: https://issues.apache.org/jira/browse/YETUS-123 > Project: Yetus > Issue Type: Bug > Components: Test Patch >Affects Versions: 0.1.0 >Reporter: Sean Busbey >Assignee: Allen Wittenauer >Priority: Critical > Fix For: YETUS-83 > > Attachments: YETUS-123.00.patch, YETUS-123.01.patch, > YETUS-123.02.patch, YETUS-123.03.patch, YETUS-123.04.patch, > YETUS-123.05.patch, YETUS-123.06.patch, YETUS-123.07.patch > > > I've made three goes at running in docker mode and all fail in a way that > suggests the set of plugins isn't making it over to the docker invocation. > since hadoop is working, I guess there's something that presumes a > personality will be used? > builds: > * > [13|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/13] > * > [14|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/14] > * > [28|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/28] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YETUS-123) Various Docker mode fixes: plug-in issues, local patch file problems, availability, & Dockerfile re-usability
[
https://issues.apache.org/jira/browse/YETUS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15009665#comment-15009665
]
Yetus QA commented on YETUS-123:
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s
{color} | {color:blue} Precommit patch detected. {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:red}-1{color} | {color:red} shellcheck {color} | {color:red} 0m 3s
{color} | {color:red} The applied patch generated 4 new shellcheck issues
(total was 4, now 8). {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
1s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 0m 10s {color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12772844/YETUS-123.07.patch |
| JIRA Issue | YETUS-123 |
| Optional Tests | asflicense shellcheck |
| uname | Linux penates.apache.org 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT
Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | nobuild |
| git revision | master / 87014f4 |
| shellcheck | v0.3.3 (This is an old version that has serious bugs. Consider
upgrading.) |
| shellcheck |
https://builds.apache.org/job/PreCommit-YETUS-Build/100/artifact/patchprocess/diff-patch-shellcheck.txt
|
| modules | C: U: |
| Powered by | Apache Yetus http://yetus.apache.org |
| Console output |
https://builds.apache.org/job/PreCommit-YETUS-Build/100/console |
This message was automatically generated.
> Various Docker mode fixes: plug-in issues, local patch file problems,
> availability, & Dockerfile re-usability
> -
>
> Key: YETUS-123
> URL: https://issues.apache.org/jira/browse/YETUS-123
> Project: Yetus
> Issue Type: Bug
> Components: Test Patch
>Affects Versions: 0.1.0
>Reporter: Sean Busbey
>Assignee: Allen Wittenauer
>Priority: Critical
> Fix For: YETUS-83
>
> Attachments: YETUS-123.00.patch, YETUS-123.01.patch,
> YETUS-123.02.patch, YETUS-123.03.patch, YETUS-123.04.patch,
> YETUS-123.05.patch, YETUS-123.06.patch, YETUS-123.07.patch
>
>
> I've made three goes at running in docker mode and all fail in a way that
> suggests the set of plugins isn't making it over to the docker invocation.
> since hadoop is working, I guess there's something that presumes a
> personality will be used?
> builds:
> *
> [13|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/13]
> *
> [14|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/14]
> *
> [28|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/28]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (YETUS-123) Various Docker mode fixes: plug-in issues, local patch file problems, availability, & Dockerfile re-usability
[ https://issues.apache.org/jira/browse/YETUS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15009664#comment-15009664 ] Yetus QA commented on YETUS-123: (!) 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/100/console in case of problems. > Various Docker mode fixes: plug-in issues, local patch file problems, > availability, & Dockerfile re-usability > - > > Key: YETUS-123 > URL: https://issues.apache.org/jira/browse/YETUS-123 > Project: Yetus > Issue Type: Bug > Components: Test Patch >Affects Versions: 0.1.0 >Reporter: Sean Busbey >Assignee: Allen Wittenauer >Priority: Critical > Fix For: YETUS-83 > > Attachments: YETUS-123.00.patch, YETUS-123.01.patch, > YETUS-123.02.patch, YETUS-123.03.patch, YETUS-123.04.patch, > YETUS-123.05.patch, YETUS-123.06.patch, YETUS-123.07.patch > > > I've made three goes at running in docker mode and all fail in a way that > suggests the set of plugins isn't making it over to the docker invocation. > since hadoop is working, I guess there's something that presumes a > personality will be used? > builds: > * > [13|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/13] > * > [14|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/14] > * > [28|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/28] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YETUS-123) Various Docker mode fixes: plug-in issues, local patch file problems, availability, & Dockerfile re-usability
[ https://issues.apache.org/jira/browse/YETUS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15009662#comment-15009662 ] Allen Wittenauer commented on YETUS-123: -07: * fix all of [~sekikn]'s discoveries. I think. ;) * changed the docker/exec mode vote_table * added elapsed times during docker builds * moved finish_docker_stats to docker_finish_stats in the docker.sh file > Various Docker mode fixes: plug-in issues, local patch file problems, > availability, & Dockerfile re-usability > - > > Key: YETUS-123 > URL: https://issues.apache.org/jira/browse/YETUS-123 > Project: Yetus > Issue Type: Bug > Components: Test Patch >Affects Versions: 0.1.0 >Reporter: Sean Busbey >Assignee: Allen Wittenauer >Priority: Critical > Fix For: YETUS-83 > > Attachments: YETUS-123.00.patch, YETUS-123.01.patch, > YETUS-123.02.patch, YETUS-123.03.patch, YETUS-123.04.patch, > YETUS-123.05.patch, YETUS-123.06.patch, YETUS-123.07.patch > > > I've made three goes at running in docker mode and all fail in a way that > suggests the set of plugins isn't making it over to the docker invocation. > since hadoop is working, I guess there's something that presumes a > personality will be used? > builds: > * > [13|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/13] > * > [14|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/14] > * > [28|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-YETUS-Build/28] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YETUS-81) Publish generated apidocs on website
[ https://issues.apache.org/jira/browse/YETUS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated YETUS-81: - Attachment: YETUS-81.1.patch -01 * rebase * fix formatting on contributing guide * fix link to docs for precommit and audience annotation under middleman exec > Publish generated apidocs on website > > > Key: YETUS-81 > URL: https://issues.apache.org/jira/browse/YETUS-81 > Project: Yetus > Issue Type: Improvement > Components: Audience Annotations, Test Patch, website and > documentation >Affects Versions: 0.1.0 >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Critical > Attachments: YETUS-81.0.patch, YETUS-81.1.patch > > > we should publish the javadocs for the IA.Public parts of the project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YETUS-81) Publish generated apidocs on website
[ https://issues.apache.org/jira/browse/YETUS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010364#comment-15010364 ] Yetus QA commented on YETUS-81: --- (!) 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/103/console in case of problems. > Publish generated apidocs on website > > > Key: YETUS-81 > URL: https://issues.apache.org/jira/browse/YETUS-81 > Project: Yetus > Issue Type: Improvement > Components: Audience Annotations, Test Patch, website and > documentation >Affects Versions: 0.1.0 >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Critical > Attachments: YETUS-81.0.patch, YETUS-81.1.patch > > > we should publish the javadocs for the IA.Public parts of the project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YETUS-81) Publish generated apidocs on website
[
https://issues.apache.org/jira/browse/YETUS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010365#comment-15010365
]
Yetus QA commented on YETUS-81:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s
{color} | {color:blue} Precommit patch detected. {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:blue}0{color} | {color:blue} rubocop {color} | {color:blue} 0m 1s
{color} | {color:blue} Rubocop was not available. {color} |
| {color:blue}0{color} | {color:blue} ruby-lint {color} | {color:blue} 0m 1s
{color} | {color:blue} Ruby-lint was not available. {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m 0s
{color} | {color:red} The patch has 146 line(s) that end in whitespace. Use git
apply --whitespace=fix. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
1s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 0m 10s {color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12772928/YETUS-81.1.patch |
| JIRA Issue | YETUS-81 |
| Optional Tests | asflicense rubocop ruby_lint |
| uname | Linux penates.apache.org 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT
Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | nobuild |
| git revision | master / eb90f14 |
| whitespace |
https://builds.apache.org/job/PreCommit-YETUS-Build/103/artifact/patchprocess/whitespace-eol.txt
|
| modules | C: U: |
| Powered by | Apache Yetus http://yetus.apache.org |
| Console output |
https://builds.apache.org/job/PreCommit-YETUS-Build/103/console |
This message was automatically generated.
> Publish generated apidocs on website
>
>
> Key: YETUS-81
> URL: https://issues.apache.org/jira/browse/YETUS-81
> Project: Yetus
> Issue Type: Improvement
> Components: Audience Annotations, Test Patch, website and
> documentation
>Affects Versions: 0.1.0
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Critical
> Attachments: YETUS-81.0.patch, YETUS-81.1.patch
>
>
> we should publish the javadocs for the IA.Public parts of the project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (YETUS-90) Wrong function name for tap_parse_args
[
https://issues.apache.org/jira/browse/YETUS-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved YETUS-90.
--
Resolution: Duplicate
> Wrong function name for tap_parse_args
> --
>
> Key: YETUS-90
> URL: https://issues.apache.org/jira/browse/YETUS-90
> Project: Yetus
> Issue Type: Bug
> Components: Test Patch
>Reporter: Kengo Seki
> Labels: newbie
> Fix For: 0.1.0, YETUS-83
>
>
> {code}
> 22 function tap_process_args
> 23 {
> 24 declare i
> 25
> 26 for i in "$@"; do
> 27 case ${i} in
> 28 --tap-log-dir=*)
> 29 TAP_LOG_DIR=${i#=*}
> 30 ;;
> 31 esac
> 32 done
> 33 }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (YETUS-90) Wrong function name for tap_parse_args
[
https://issues.apache.org/jira/browse/YETUS-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey reopened YETUS-90:
--
> Wrong function name for tap_parse_args
> --
>
> Key: YETUS-90
> URL: https://issues.apache.org/jira/browse/YETUS-90
> Project: Yetus
> Issue Type: Bug
> Components: Test Patch
>Reporter: Kengo Seki
> Labels: newbie
> Fix For: 0.1.0, YETUS-83
>
>
> {code}
> 22 function tap_process_args
> 23 {
> 24 declare i
> 25
> 26 for i in "$@"; do
> 27 case ${i} in
> 28 --tap-log-dir=*)
> 29 TAP_LOG_DIR=${i#=*}
> 30 ;;
> 31 esac
> 32 done
> 33 }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
