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

Hadoop QA commented on OOZIE-3265:
----------------------------------


Testing JIRA OOZIE-3265

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 star imports
.    {color:green}+1{color} the patch does not introduce any line longer than 
132
.    {color:green}+1{color} the patch adds/modifies 2 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} Javadoc generation succeeded with the patch
.    {color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
{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:red}-1{color} There are [4] new bugs found below threshold in total that 
must be fixed.
.    {color:green}+1{color} There are no new bugs found in 
[fluent-job/fluent-job-api].
.    {color:green}+1{color} There are no new bugs found in [tools].
.    {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
.    {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
.    {color:green}+1{color} There are no new bugs found in [sharelib/spark].
.    {color:green}+1{color} There are no new bugs found in [sharelib/pig].
.    {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
.    {color:green}+1{color} There are no new bugs found in [sharelib/git].
.    {color:green}+1{color} There are no new bugs found in [sharelib/hive].
.    {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
.    {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.    {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.    {color:orange}0{color} There are [4] new bugs found in [server] that would 
be nice to have fixed.
.    You can find the SpotBugs diff here: server/findbugs-new.html
.    {color:green}+1{color} There are no new bugs found in [examples].
.    {color:red}-1{color} There are [4] new bugs found below threshold in 
[core] that must be fixed.
.    You can find the SpotBugs diff here (look for the red and orange ones): 
core/findbugs-new.html
.    The most important SpotBugs errors are:
.    At CoordJobGetActionsSubsetJPAExecutor.java:[line 111]: This use of 
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
 can be vulnerable to SQL/JPQL injection
.    At CoordJobGetActionsSubsetJPAExecutor.java:[line 77]: At 
CoordJobGetActionsSubsetJPAExecutor.java:[line 76]
.    At CoordJobGetActionsSubsetJPAExecutor.java:[line 86]: At 
CoordJobGetActionsSubsetJPAExecutor.java:[line 85]
.    At CoordJobGetActionsSubsetJPAExecutor.java:[line 111]: At 
CoordJobGetActionsSubsetJPAExecutor.java:[line 108]
.    At AuthorizationService.java:[line 192]: 
java/io/File.<init>(Ljava/lang/String;Ljava/lang/String;)V reads a file 
whose location might be specified by user input
.    {color:green}+1{color} There are no new bugs found in [client].
.    {color:green}+1{color} There are no new bugs found in [docs].
.    {color:green}+1{color} There are no new bugs found in [webapp].
{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: 3175
{color:green}+1 DISTRO{color}
.    {color:green}+1{color} distro tarball builds with the patch 

----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

. https://builds.apache.org/job/PreCommit-OOZIE-Build/1186/



> properties RERUN_FAIL_NODES and RERUN_SKIP_NODES should be able to appear 
> together
> ----------------------------------------------------------------------------------
>
>                 Key: OOZIE-3265
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3265
>             Project: Oozie
>          Issue Type: Task
>    Affects Versions: 5.0.0
>            Reporter: TIAN XING
>            Assignee: Julia Kinga Marton
>            Priority: Minor
>         Attachments: OOZIE-3265-004.patch, OOZIE-3265-005.patch, 
> OOZIE-3265-006.patch, OOZIE-3265-007.patch, OOZIE-3265-v1.patch, 
> OOZIE-3265-v2.patch, OOZIE-3265-v3.patch, rerun.patch
>
>
> Currently when you re-run a workflow with property "oozie.wf.rerun.failnodes" 
>  set to true,
> you can no longer re-run it again with "oozie.wf.rerun.skip.nodes" property 
> specified, even if you set "oozie.wf.rerun.failnodes" to false.
> This kind of limitation is not reasonable. There is only one case where 
> "oozie.wf.rerun.failnodes" is true and "oozie.wf.rerun.skip.nodes" is not 
> null or empty, that should be disallowed.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to