[jira] [Commented] (OOZIE-2570) remove -PtestPatchCompile from patch testing as there is no such profile

2016-06-16 Thread Robert Kanter (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334803#comment-15334803
 ] 

Robert Kanter commented on OOZIE-2570:
--

+1  It will be good to get rid of that warning.

> remove  -PtestPatchCompile from patch testing as there is no such profile
> -
>
> Key: OOZIE-2570
> URL: https://issues.apache.org/jira/browse/OOZIE-2570
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2570-1.patch
>
>
> Right not the bin/test-patch-10-compile calls maven like this:
> {noformat}
> mvn clean test -PtestPatchCompile -DskipTests ${MVNPASSTHRU} | tee 
> ${REPORTDIR}/${TASKNAME}-clean.txt >> $STDOUT
> {noformat}
> and every COMPILE-patch.txt contains the warning message
> {noformat}
> [WARNING] The requested profile "testPatchCompile" could not be activated 
> because it does not exist.
> {noformat}
> e.g.: 
> https://builds.apache.org/job/oozie-trunk-precommit-build/2976/artifact/test-patch/reports/COMPILE-patch.txt



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (OOZIE-2570) remove -PtestPatchCompile from patch testing as there is no such profile

2016-06-13 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15327239#comment-15327239
 ] 

Hadoop QA commented on OOZIE-2570:
--

Testing JIRA OOZIE-2570

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1786
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:green}*+1 Overall result, good!, no -1s*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/2981/

> remove  -PtestPatchCompile from patch testing as there is no such profile
> -
>
> Key: OOZIE-2570
> URL: https://issues.apache.org/jira/browse/OOZIE-2570
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2570-1.patch
>
>
> Right not the bin/test-patch-10-compile calls maven like this:
> {noformat}
> mvn clean test -PtestPatchCompile -DskipTests ${MVNPASSTHRU} | tee 
> ${REPORTDIR}/${TASKNAME}-clean.txt >> $STDOUT
> {noformat}
> and every COMPILE-patch.txt contains the warning message
> {noformat}
> [WARNING] The requested profile "testPatchCompile" could not be activated 
> because it does not exist.
> {noformat}
> e.g.: 
> https://builds.apache.org/job/oozie-trunk-precommit-build/2976/artifact/test-patch/reports/COMPILE-patch.txt



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)