[jira] [Commented] (OOZIE-3688) Introduce retry mechanism when starting embedded servlet containers in unit tests
[
https://issues.apache.org/jira/browse/OOZIE-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17647059#comment-17647059
]
Hadoop QA commented on OOZIE-3688:
--
Testing JIRA OOZIE-3688
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 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} 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 [8] new bugs found below threshold in total that
must be fixed.
.{color:red}-1{color} There are [7] new bugs found below threshold in
[core] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
core/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At BulkJPAExecutor.java:[line 206]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175]
.At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199]
.This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206]
.At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127]
.{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
[fluent-job/fluent-job-api].
.{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:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{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/spark].
.{color:red}-1{color} There are [1] new bugs found below threshold in
[sharelib/oozie] that must be fixed.
.You can find the SpotBugs diff here (look for the red and orange ones):
sharelib/oozie/findbugs-new.html
.The most important SpotBugs errors are:
.At ShellMain.java:[line 93]: This usage of
java/lang/ProcessBuilder.init(Ljava/util/List;)V can be vulnerable to
Command Injection
.At ShellMain.java:[line 91]: At ShellMain.java:[line 90]
.At ShellMain.java:[line 92]
.{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/streaming].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/hive].
.{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/git].
{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: 3259
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/170/
> Introduce retry mechanism when starting embedded servlet containers in unit
> tests
> -
>
> Key: OOZIE-3688
>
[jira] [Commented] (OOZIE-3688) Introduce retry mechanism when starting embedded servlet containers in unit tests
[ https://issues.apache.org/jira/browse/OOZIE-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17647020#comment-17647020 ] Hadoop QA commented on OOZIE-3688: -- PreCommit-OOZIE-Build started > Introduce retry mechanism when starting embedded servlet containers in unit > tests > - > > Key: OOZIE-3688 > URL: https://issues.apache.org/jira/browse/OOZIE-3688 > Project: Oozie > Issue Type: Bug >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3688-001.patch > > > In the unit tests which uses the embedded servlet container an intermittent > issue can occur without this change, because those tests start the container > in a specific port, which is available at the start of the unit tests. > However, in some corner cases, it can happen that the port is being available > at the start of the test, but some process occupies that port meanwhile, > leading to a `java.net.BindException: Address already in use` exception > during the unit test's execution. > The goal of this ticket is resolve this by introducing a retry mechanism when > starting the embedded servlet container. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3141) Expose external child job IDs to EL functions: wf:externalChildIDs(String actionName)
[
https://issues.apache.org/jira/browse/OOZIE-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646060#comment-17646060
]
Hadoop QA commented on OOZIE-3141:
--
Testing JIRA OOZIE-3141
Cleaning local git workspace
{color:red}-1{color} Patch failed to apply to head of branch
> Expose external child job IDs to EL functions: wf:externalChildIDs(String
> actionName)
> -
>
> Key: OOZIE-3141
> URL: https://issues.apache.org/jira/browse/OOZIE-3141
> Project: Oozie
> Issue Type: Improvement
> Components: core
>Affects Versions: 5.0.0b1
>Reporter: Huizhi Lu
>Priority: Minor
> Attachments: OOZIE-3141.0001.patch
>
>
> Expose external child job IDs to EL functions: wf:externalChildIDs(String
> actionName).
> So we can use this EL function wf:externalChildIDs(String actionName) to get
> the child jobs and call yarn rest api to get the job information such
> diagnostics and embed the info in the email notifications.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3141) Expose external child job IDs to EL functions: wf:externalChildIDs(String actionName)
[ https://issues.apache.org/jira/browse/OOZIE-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646057#comment-17646057 ] Hadoop QA commented on OOZIE-3141: -- PreCommit-OOZIE-Build started > Expose external child job IDs to EL functions: wf:externalChildIDs(String > actionName) > - > > Key: OOZIE-3141 > URL: https://issues.apache.org/jira/browse/OOZIE-3141 > Project: Oozie > Issue Type: Improvement > Components: core >Affects Versions: 5.0.0b1 >Reporter: Huizhi Lu >Priority: Minor > Attachments: OOZIE-3141.0001.patch > > > Expose external child job IDs to EL functions: wf:externalChildIDs(String > actionName). > So we can use this EL function wf:externalChildIDs(String actionName) to get > the child jobs and call yarn rest api to get the job information such > diagnostics and embed the info in the email notifications. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3141) Expose external child job IDs to EL functions: wf:externalChildIDs(String actionName)
[ https://issues.apache.org/jira/browse/OOZIE-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646031#comment-17646031 ] Hadoop QA commented on OOZIE-3141: -- PreCommit-OOZIE-Build started > Expose external child job IDs to EL functions: wf:externalChildIDs(String > actionName) > - > > Key: OOZIE-3141 > URL: https://issues.apache.org/jira/browse/OOZIE-3141 > Project: Oozie > Issue Type: Improvement > Components: core >Affects Versions: 5.0.0b1 >Reporter: Huizhi Lu >Priority: Minor > Attachments: OOZIE-3141.0001.patch > > > Expose external child job IDs to EL functions: wf:externalChildIDs(String > actionName). > So we can use this EL function wf:externalChildIDs(String actionName) to get > the child jobs and call yarn rest api to get the job information such > diagnostics and embed the info in the email notifications. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3141) Expose external child job IDs to EL functions: wf:externalChildIDs(String actionName)
[ https://issues.apache.org/jira/browse/OOZIE-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646032#comment-17646032 ] Hadoop QA commented on OOZIE-3141: -- Testing JIRA OOZIE-3141 Cleaning local git workspace > Expose external child job IDs to EL functions: wf:externalChildIDs(String > actionName) > - > > Key: OOZIE-3141 > URL: https://issues.apache.org/jira/browse/OOZIE-3141 > Project: Oozie > Issue Type: Improvement > Components: core >Affects Versions: 5.0.0b1 >Reporter: Huizhi Lu >Priority: Minor > Attachments: OOZIE-3141.0001.patch > > > Expose external child job IDs to EL functions: wf:externalChildIDs(String > actionName). > So we can use this EL function wf:externalChildIDs(String actionName) to get > the child jobs and call yarn rest api to get the job information such > diagnostics and embed the info in the email notifications. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3687) Fix Oozie client always using the current system username instead the one specified by the user (e.g.: via kerberos or via explicit basic authentication)
[
https://issues.apache.org/jira/browse/OOZIE-3687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645454#comment-17645454
]
Hadoop QA commented on OOZIE-3687:
--
Testing JIRA OOZIE-3687
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch contains 1 line(s) longer than 132
characters
.{color:green}+1{color} the patch 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} 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 [22] new bugs found below threshold in total
that must be fixed.
.{color:red}-1{color} There are [15] new bugs found below threshold in
[tools] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
tools/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At OozieDBCLI.java:[line 584]: This use of
java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be vulnerable to SQL
injection
.At OozieDBCLI.java:[line 574]: At OozieDBCLI.java:[line 573]
.At OozieDBCLI.java:[line 577]: At OozieDBCLI.java:[line 575]
.At OozieDBCLI.java:[line 579]: At OozieDBCLI.java:[line 578]
.At OozieDBCLI.java:[line 584]: At OozieDBCLI.java:[line 581]
.{color:red}-1{color} There are [6] new bugs found below threshold in
[core] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
core/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At BulkJPAExecutor.java:[line 206]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175]
.At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199]
.This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206]
.At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127]
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/streaming].
.{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/spark].
.{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/git].
.{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/oozie].
.{color:green}+1{color} There are no new bugs found in [sharelib/pig].
.{color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
.{color:red}-1{color} There are [1] new bugs found below threshold in
[client] that must be fixed.
.You can find the SpotBugs diff here (look for the red and orange ones):
client/findbugs-new.html
.The most important SpotBugs errors are:
.At DebugConsoleLogger.java:[line 28]: Possible information exposure
through an error message
.{color:green}+1{color} There are no new bugs found in [server].
.{color:green}+1{color} There are no new bugs found in [docs].
{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:red}-1 TESTS{color}
.Tests run: 3262
.Tests failed : 2
.Tests in error : 1
.Tests timed out : 0
{color:red}-1{color} [ERROR] There are [2] test failures in [core]. Listing
only the first [5] ones
[jira] [Commented] (OOZIE-3687) Fix Oozie client always using the current system username instead the one specified by the user (e.g.: via kerberos or via explicit basic authentication)
[ https://issues.apache.org/jira/browse/OOZIE-3687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645400#comment-17645400 ] Hadoop QA commented on OOZIE-3687: -- PreCommit-OOZIE-Build started > Fix Oozie client always using the current system username instead the one > specified by the user (e.g.: via kerberos or via explicit basic > authentication) > - > > Key: OOZIE-3687 > URL: https://issues.apache.org/jira/browse/OOZIE-3687 > Project: Oozie > Issue Type: Bug >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3687-001.patch > > > Oozie client relies on user.name system property now which is not secure in a > kerberised environment. This has to be changed. > A bug in Oozie CLI causes the Workflow to be launched in the name of the > current Unix user even if Kerberos authentication is used with a ticket for a > different user. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3663) Upgrade Apache Xerces Java to 2.12.2
[
https://issues.apache.org/jira/browse/OOZIE-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644936#comment-17644936
]
Hadoop QA commented on OOZIE-3663:
--
Testing JIRA OOZIE-3663
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch does not add/modify any testcase
{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 [1] new bugs found below threshold in total that
must be fixed.
.{color:green}+1{color} There are no new bugs found in [examples].
.{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 [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/distcp].
.{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/sqoop].
.{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/oozie].
.{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/streaming].
.{color:green}+1{color} There are no new bugs found in [server].
.{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:red}-1{color} There are [1] 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 ShareLibService.java:[line 695]: Unsafe comparison of hash that are
susceptible to timing attack
.At ShareLibService.java:[line 691]: At ShareLibService.java:[line 689]
.At ShareLibService.java:[line 693]
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [client].
{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:red}-1 TESTS{color}
.Tests run: 3259
.Tests failed : 7
.Tests in error : 0
.Tests timed out : 0
{color:red}-1{color} [ERROR] There are [7] test failures in [core]. Listing
only the first [5] ones
testDryrunInvalidXml:org.apache.oozie.command.wf.TestSubmitXCommand
Check console output for the full list of errors/failures
.{color:orange}Tests failed at first run:{color}
TestCLIParser#testCommandParserShowHelpWithOptions
TestCoordActionsKillXCommand#testActionKillCommandActionNumbers
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/166/
> Upgrade Apache Xerces Java to 2.12.2
>
>
> Key: OOZIE-3663
> URL: https://issues.apache.org/jira/browse/OOZIE-3663
> Project: Oozie
> Issue Type: Improvement
>Reporter: Ashutosh Gupta
>Assignee: Ashutosh Gupta
>Priority: Major
> Attachments: OOZIE-3663-001.patch
>
>
> Description
> [https://github.com/advisories/GHSA-h65f-jvqw-m9fj]
> There's a vulnerability within the Apache Xerces Java (XercesJ) XML parser
> when handling specially crafted XML document payloads. This
[jira] [Commented] (OOZIE-3663) Upgrade Apache Xerces Java to 2.12.2
[ https://issues.apache.org/jira/browse/OOZIE-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644887#comment-17644887 ] Hadoop QA commented on OOZIE-3663: -- PreCommit-OOZIE-Build started > Upgrade Apache Xerces Java to 2.12.2 > > > Key: OOZIE-3663 > URL: https://issues.apache.org/jira/browse/OOZIE-3663 > Project: Oozie > Issue Type: Improvement >Reporter: Ashutosh Gupta >Assignee: Ashutosh Gupta >Priority: Major > Attachments: OOZIE-3663-001.patch > > > Description > [https://github.com/advisories/GHSA-h65f-jvqw-m9fj] > There's a vulnerability within the Apache Xerces Java (XercesJ) XML parser > when handling specially crafted XML document payloads. This causes, the > XercesJ XML parser to wait in an infinite loop, which may sometimes consume > system resources for prolonged duration. This vulnerability is present within > XercesJ version 2.12.1 and the previous versions. > References > [https://nvd.nist.gov/vuln/detail/CVE-2022-23437] > [https://lists.apache.org/thread/6pjwm10bb69kq955fzr1n0nflnjd27dl] > [http://www.openwall.com/lists/oss-security/2022/01/24/3] > [https://www.oracle.com/security-alerts/cpuapr2022.html] > h4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3686) Repair flaky testRetryConsoleUrlForked unit test
[
https://issues.apache.org/jira/browse/OOZIE-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644495#comment-17644495
]
Hadoop QA commented on OOZIE-3686:
--
Testing JIRA OOZIE-3686
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 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} 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:orange}0{color} There are [4] new bugs found in total that would be nice
to have fixed.
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/streaming].
.{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/spark].
.{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/git].
.{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/oozie].
.{color:green}+1{color} There are no new bugs found in [sharelib/pig].
.{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 [client].
.{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 [docs].
{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: 3259
.{color:orange}Tests failed at first run:{color}
TestCoordActionsKillXCommand#testActionKillCommandActionNumbers
TestCoordActionsKillXCommand#testActionKillCommandDate
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:green}*+1 Overall result, good!, no -1s*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/165/
> Repair flaky testRetryConsoleUrlForked unit test
>
>
> Key: OOZIE-3686
> URL: https://issues.apache.org/jira/browse/OOZIE-3686
> Project: Oozie
> Issue Type: Bug
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3686-001.patch
>
>
> testRetryConsoleUrlForked can fail periodically and can be reproduced
> locally. The following exception is thrown:
> {code:java}
> java.lang.NullPointerException
> at
> org.apache.oozie.command.wf.TestWorkflowActionRetryInfoXCommand.validateRetryConsoleUrl(TestWorkflowActionRetryInfoXCommand.java:192)
> at
> org.apache.oozie.command.wf.TestWorkflowActionRetryInfoXCommand.testRetryConsoleUrlForked(TestWorkflowActionRetryInfoXCommand.java:126)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
[jira] [Commented] (OOZIE-3685) Repair flaky testCoordActionInputCheckXCommandUniqueness unit test
[
https://issues.apache.org/jira/browse/OOZIE-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644476#comment-17644476
]
Hadoop QA commented on OOZIE-3685:
--
Testing JIRA OOZIE-3685
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:orange}0{color} There are [4] new bugs found in total that would be nice
to have fixed.
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
.{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 [core].
.{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/hive2].
.{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/streaming].
.{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/git].
.{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/pig].
.{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/sqoop].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:green}+1{color} There are no new bugs found in [examples].
{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: 3259
.{color:orange}Tests failed at first run:{color}
TestCoordActionInputCheckXCommand#testNone
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:green}*+1 Overall result, good!, no -1s*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/164/
> Repair flaky testCoordActionInputCheckXCommandUniqueness unit test
> --
>
> Key: OOZIE-3685
> URL: https://issues.apache.org/jira/browse/OOZIE-3685
> Project: Oozie
> Issue Type: Bug
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3685-001.patch
>
>
> org.apache.oozie.command.coord.TestCoordActionInputCheckXCommand#testCoordActionInputCheckXCommandUniqueness
> unit test is flaky.
> This unit test failure can be reproduced easily using the following command:
> {code:java}
> mvn clean package test
> -Dtest=org.apache.oozie.command.coord.TestCoordActionInputCheckXCommand#testCoordActionInputCheckXCommandUniqueness
> {code}
> The goal of this Jira is to eliminate this intermittent behaviour.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3684) Migrate to commons-lang3 again
[
https://issues.apache.org/jira/browse/OOZIE-3684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644462#comment-17644462
]
Hadoop QA commented on OOZIE-3684:
--
Testing JIRA OOZIE-3684
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch does not add/modify any testcase
{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:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [examples].
.{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 [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/distcp].
.{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/sqoop].
.{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/oozie].
.{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/streaming].
.{color:green}+1{color} There are no new bugs found in [server].
.{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{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [client].
{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: 3259
.{color:orange}Tests failed at first run:{color}
TestCoordActionsKillXCommand#testActionKillCommandDate
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/163/
> Migrate to commons-lang3 again
> --
>
> Key: OOZIE-3684
> URL: https://issues.apache.org/jira/browse/OOZIE-3684
> Project: Oozie
> Issue Type: Improvement
> Components: core
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3684-001.patch
>
>
> There was already a commons-lang 2->3 upgrade in scope of OOZIE-3446, but
> OOZIE-3492 brought it back again to:
> org.apache.oozie.action.hadoop.SparkActionExecutor:
> https://github.com/apache/oozie/blob/3a932ad1cd7e294576b03c48bbd28e691ad6f58b/core/src/main/java/org/apache/oozie/action/hadoop/SparkActionExecutor.java#L22
> The goal of this Jira is to change this import to the commons-lang3 version
> one to make Oozie fully migrated to commons-lang3 again.
> _NOTE_: the commons-lang 2 version is available via transitive dependency.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3686) Repair flaky testRetryConsoleUrlForked unit test
[
https://issues.apache.org/jira/browse/OOZIE-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644451#comment-17644451
]
Hadoop QA commented on OOZIE-3686:
--
PreCommit-OOZIE-Build started
> Repair flaky testRetryConsoleUrlForked unit test
>
>
> Key: OOZIE-3686
> URL: https://issues.apache.org/jira/browse/OOZIE-3686
> Project: Oozie
> Issue Type: Bug
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3686-001.patch
>
>
> testRetryConsoleUrlForked can fail periodically and can be reproduced
> locally. The following exception is thrown:
> {code:java}
> java.lang.NullPointerException
> at
> org.apache.oozie.command.wf.TestWorkflowActionRetryInfoXCommand.validateRetryConsoleUrl(TestWorkflowActionRetryInfoXCommand.java:192)
> at
> org.apache.oozie.command.wf.TestWorkflowActionRetryInfoXCommand.testRetryConsoleUrlForked(TestWorkflowActionRetryInfoXCommand.java:126)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:177)
> at junit.framework.TestCase.runBare(TestCase.java:142)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:130)
> at junit.framework.TestSuite.runTest(TestSuite.java:241)
> at junit.framework.TestSuite.run(TestSuite.java:236)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:90)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at
> org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:410)
> at
> org.apache.maven.surefire.junitcore.pc.InvokerStrategy.schedule(InvokerStrategy.java:54)
> at
> org.apache.maven.surefire.junitcore.pc.Scheduler.schedule(Scheduler.java:367)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.apache.maven.surefire.junitcore.pc.ParallelComputerBuilder$PC$1.run(ParallelComputerBuilder.java:590)
> at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
> {code}
> The goal of this ticket is to prevent the above NPE to happen by adding a
> sleep which lets Oozie finish its back end DB synchronisation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3685) Repair flaky testCoordActionInputCheckXCommandUniqueness unit test
[
https://issues.apache.org/jira/browse/OOZIE-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644434#comment-17644434
]
Hadoop QA commented on OOZIE-3685:
--
PreCommit-OOZIE-Build started
> Repair flaky testCoordActionInputCheckXCommandUniqueness unit test
> --
>
> Key: OOZIE-3685
> URL: https://issues.apache.org/jira/browse/OOZIE-3685
> Project: Oozie
> Issue Type: Bug
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3685-001.patch
>
>
> org.apache.oozie.command.coord.TestCoordActionInputCheckXCommand#testCoordActionInputCheckXCommandUniqueness
> unit test is flaky.
> This unit test failure can be reproduced easily using the following command:
> {code:java}
> mvn clean package test
> -Dtest=org.apache.oozie.command.coord.TestCoordActionInputCheckXCommand#testCoordActionInputCheckXCommandUniqueness
> {code}
> The goal of this Jira is to eliminate this intermittent behaviour.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3684) Migrate to commons-lang3 again
[ https://issues.apache.org/jira/browse/OOZIE-3684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644406#comment-17644406 ] Hadoop QA commented on OOZIE-3684: -- PreCommit-OOZIE-Build started > Migrate to commons-lang3 again > -- > > Key: OOZIE-3684 > URL: https://issues.apache.org/jira/browse/OOZIE-3684 > Project: Oozie > Issue Type: Improvement > Components: core >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3684-001.patch > > > There was already a commons-lang 2->3 upgrade in scope of OOZIE-3446, but > OOZIE-3492 brought it back again to: > org.apache.oozie.action.hadoop.SparkActionExecutor: > https://github.com/apache/oozie/blob/3a932ad1cd7e294576b03c48bbd28e691ad6f58b/core/src/main/java/org/apache/oozie/action/hadoop/SparkActionExecutor.java#L22 > The goal of this Jira is to change this import to the commons-lang3 version > one to make Oozie fully migrated to commons-lang3 again. > _NOTE_: the commons-lang 2 version is available via transitive dependency. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3683) Fix intermittent unit test failure in testLoadOnRestart
[
https://issues.apache.org/jira/browse/OOZIE-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644324#comment-17644324
]
Hadoop QA commented on OOZIE-3683:
--
Testing JIRA OOZIE-3683
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 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} 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:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [examples].
.{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 [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/distcp].
.{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/sqoop].
.{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/oozie].
.{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/streaming].
.{color:green}+1{color} There are no new bugs found in [server].
.{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{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [client].
{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: 3256
.{color:orange}Tests failed at first run:{color}
TestCoordActionsKillXCommand#testActionKillCommandDate
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:green}*+1 Overall result, good!, no -1s*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/162/
> Fix intermittent unit test failure in testLoadOnRestart
>
>
> Key: OOZIE-3683
> URL: https://issues.apache.org/jira/browse/OOZIE-3683
> Project: Oozie
> Issue Type: Bug
> Components: core
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3683-001.patch
>
>
> The following failure can happen occasionally in
> _org.apache.oozie.sla.TestSLACalculatorMemory.testLoadOnRestart_ unit test:
>
> {code:java}
> junit.framework.AssertionFailedError: expected:
> but was:
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:246)
> at
> org.apache.oozie.sla.TestSLACalculatorMemory.testLoadOnRestart(TestSLACalculatorMemory.java:230)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at
[jira] [Commented] (OOZIE-3683) Fix intermittent unit test failure in testLoadOnRestart
[
https://issues.apache.org/jira/browse/OOZIE-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644280#comment-17644280
]
Hadoop QA commented on OOZIE-3683:
--
PreCommit-OOZIE-Build started
> Fix intermittent unit test failure in testLoadOnRestart
>
>
> Key: OOZIE-3683
> URL: https://issues.apache.org/jira/browse/OOZIE-3683
> Project: Oozie
> Issue Type: Bug
> Components: core
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3683-001.patch
>
>
> The following failure can happen occasionally in
> _org.apache.oozie.sla.TestSLACalculatorMemory.testLoadOnRestart_ unit test:
>
> {code:java}
> junit.framework.AssertionFailedError: expected:
> but was:
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:246)
> at
> org.apache.oozie.sla.TestSLACalculatorMemory.testLoadOnRestart(TestSLACalculatorMemory.java:230)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:177)
> at junit.framework.TestCase.runBare(TestCase.java:142)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:130)
> at junit.framework.TestSuite.runTest(TestSuite.java:241)
> at junit.framework.TestSuite.run(TestSuite.java:236)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:90)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at
> org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:410)
> at
> org.apache.maven.surefire.junitcore.pc.InvokerStrategy.schedule(InvokerStrategy.java:54)
> at
> org.apache.maven.surefire.junitcore.pc.Scheduler.schedule(Scheduler.java:367)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.apache.maven.surefire.junitcore.pc.ParallelComputerBuilder$PC$1.run(ParallelComputerBuilder.java:590)
> at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
> {code}
> The root cause of this is that the set expectedDuration can be too
[jira] [Commented] (OOZIE-3679) Correct maximum wait time between database retry attempts property
[
https://issues.apache.org/jira/browse/OOZIE-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643858#comment-17643858
]
Hadoop QA commented on OOZIE-3679:
--
Testing JIRA OOZIE-3679
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 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} 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 [22] new bugs found below threshold in total
that must be fixed.
.{color:green}+1{color} There are no new bugs found in [examples].
.{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 [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/distcp].
.{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/sqoop].
.{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/oozie].
.{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/streaming].
.{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 [docs].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{color:red}-1{color} There are [7] new bugs found below threshold in
[core] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
core/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At BulkJPAExecutor.java:[line 206]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175]
.At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199]
.This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206]
.At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127]
.{color:red}-1{color} There are [15] new bugs found below threshold in
[tools] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
tools/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At OozieDBCLI.java:[line 584]: This use of
java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be vulnerable to SQL
injection
.At OozieDBCLI.java:[line 574]: At OozieDBCLI.java:[line 573]
.At OozieDBCLI.java:[line 577]: At OozieDBCLI.java:[line 575]
.At OozieDBCLI.java:[line 579]: At OozieDBCLI.java:[line 578]
.At OozieDBCLI.java:[line 584]: At OozieDBCLI.java:[line 581]
.{color:green}+1{color} There are no new bugs found in [client].
{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: 3259
.{color:orange}Tests failed at first run:{color}
TestLocalOozieClientCoord#testJobsOperations
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check
[jira] [Commented] (OOZIE-3682) Prepare ssh-wrapper script to handle callback specific arguments with quotes
[
https://issues.apache.org/jira/browse/OOZIE-3682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643854#comment-17643854
]
Hadoop QA commented on OOZIE-3682:
--
Testing JIRA OOZIE-3682
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch does not add/modify any testcase
{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:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [core].
.{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
[fluent-job/fluent-job-api].
.{color:green}+1{color} There are no new bugs found in [server].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{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/spark].
.{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/hcatalog].
.{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/hive2].
.{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/hive].
.{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/git].
{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: 3256
.{color:orange}Tests failed at first run:{color}
TestJMSAccessorService#testConnectionRetryExceptionListener
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/160/
> Prepare ssh-wrapper script to handle callback specific arguments with quotes
>
>
> Key: OOZIE-3682
> URL: https://issues.apache.org/jira/browse/OOZIE-3682
> Project: Oozie
> Issue Type: Bug
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3682-001.patch, OOZIE-3682-002.patch
>
>
> In case someone runs an SSH action which connects from Oozie server (linux)
> to an AIX host, then the ssh-wrapper process is showing up on the remote
> host, but it hangs forever.
> This happens because the quotes around the callback URL are being retained in
> the arguments taken by ssh-base and sent to ssh-wrapper, causing an infinite
> loop.
> The goal of this ticket is to track the fix of this issue in the callback
> mechanism.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3679) Correct maximum wait time between database retry attempts property
[
https://issues.apache.org/jira/browse/OOZIE-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643791#comment-17643791
]
Hadoop QA commented on OOZIE-3679:
--
PreCommit-OOZIE-Build started
> Correct maximum wait time between database retry attempts property
> --
>
> Key: OOZIE-3679
> URL: https://issues.apache.org/jira/browse/OOZIE-3679
> Project: Oozie
> Issue Type: Bug
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3679-001.patch, OOZIE-3679-002.patch,
> OOZIE-3679-003.patch
>
>
> Based on the oozie-default.xml:
> {code:xml}
>
> oozie.service.JPAService.retry.maximum-wait-time.ms
> 3
>
> Maximum wait time between database retry attempts.
>
>
> {code}
> it looks like we are missing a "{_}retry{_}" string before the maximum wait
> time between database retry attempts static string in Oozie's JPAService:
> {code:java}
> public static final String MAX_WAIT_TIME = CONF_PREFIX +
> "maximum-wait-time.ms";
> {code}
> {color:#172b4d}The goal of this change is to sync the config names between
> oozie-default.xml and Oozie but we should also support the old, invalid
> config name.{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3682) Prepare ssh-wrapper script to handle callback specific arguments with quotes
[ https://issues.apache.org/jira/browse/OOZIE-3682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643790#comment-17643790 ] Hadoop QA commented on OOZIE-3682: -- PreCommit-OOZIE-Build started > Prepare ssh-wrapper script to handle callback specific arguments with quotes > > > Key: OOZIE-3682 > URL: https://issues.apache.org/jira/browse/OOZIE-3682 > Project: Oozie > Issue Type: Bug >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3682-001.patch, OOZIE-3682-002.patch > > > In case someone runs an SSH action which connects from Oozie server (linux) > to an AIX host, then the ssh-wrapper process is showing up on the remote > host, but it hangs forever. > This happens because the quotes around the callback URL are being retained in > the arguments taken by ssh-base and sent to ssh-wrapper, causing an infinite > loop. > The goal of this ticket is to track the fix of this issue in the callback > mechanism. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3679) Correct maximum wait time between database retry attempts property
[
https://issues.apache.org/jira/browse/OOZIE-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643459#comment-17643459
]
Hadoop QA commented on OOZIE-3679:
--
Testing JIRA OOZIE-3679
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 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} 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 [22] new bugs found below threshold in total
that must be fixed.
.{color:green}+1{color} There are no new bugs found in [webapp].
.{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 [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/sqoop].
.{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/git].
.{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/hive].
.{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/hive2].
.{color:green}+1{color} There are no new bugs found in [sharelib/oozie].
.{color:red}-1{color} There are [15] new bugs found below threshold in
[tools] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
tools/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At OozieDBCLI.java:[line 584]: This use of
java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be vulnerable to SQL
injection
.At OozieDBCLI.java:[line 574]: At OozieDBCLI.java:[line 573]
.At OozieDBCLI.java:[line 577]: At OozieDBCLI.java:[line 575]
.At OozieDBCLI.java:[line 579]: At OozieDBCLI.java:[line 578]
.At OozieDBCLI.java:[line 584]: At OozieDBCLI.java:[line 581]
.{color:green}+1{color} There are no new bugs found in [server].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:green}+1{color} There are no new bugs found in [client].
.{color:red}-1{color} There are [7] new bugs found below threshold in
[core] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
core/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At BulkJPAExecutor.java:[line 206]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175]
.At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199]
.This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206]
.At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127]
{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:red}-1 TESTS{color}
.Tests run: 3259
.Tests failed : 1
.Tests in error : 0
.Tests timed out : 0
{color:red}-1{color} [ERROR] There are [1] test failures in [core]. Listing
only the first [5] ones
testIfNoCustomFsConfigProvidedBaseConfigRemainsTheSame:org.apache.oozie.service.TestHadoopAccessorService
Check console output for the full list of errors/failures
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1
[jira] [Commented] (OOZIE-3679) Correct maximum wait time between database retry attempts property
[
https://issues.apache.org/jira/browse/OOZIE-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643382#comment-17643382
]
Hadoop QA commented on OOZIE-3679:
--
PreCommit-OOZIE-Build started
> Correct maximum wait time between database retry attempts property
> --
>
> Key: OOZIE-3679
> URL: https://issues.apache.org/jira/browse/OOZIE-3679
> Project: Oozie
> Issue Type: Bug
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3679-001.patch, OOZIE-3679-002.patch,
> OOZIE-3679-003.patch
>
>
> Based on the oozie-default.xml:
> {code:xml}
>
> oozie.service.JPAService.retry.maximum-wait-time.ms
> 3
>
> Maximum wait time between database retry attempts.
>
>
> {code}
> it looks like we are missing a "{_}retry{_}" string before the maximum wait
> time between database retry attempts static string in Oozie's JPAService:
> {code:java}
> public static final String MAX_WAIT_TIME = CONF_PREFIX +
> "maximum-wait-time.ms";
> {code}
> {color:#172b4d}The goal of this change is to sync the config names between
> oozie-default.xml and Oozie but we should also support the old, invalid
> config name.{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3682) Prepare ssh-wrapper script to handle callback specific arguments with quotes
[
https://issues.apache.org/jira/browse/OOZIE-3682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643321#comment-17643321
]
Hadoop QA commented on OOZIE-3682:
--
Testing JIRA OOZIE-3682
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch does not add/modify any testcase
{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:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/streaming].
.{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/spark].
.{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/git].
.{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/oozie].
.{color:green}+1{color} There are no new bugs found in [sharelib/pig].
.{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 [client].
.{color:green}+1{color} There are no new bugs found in [server].
.{color:green}+1{color} There are no new bugs found in [docs].
{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:red}-1 TESTS{color}
.Tests run: 3256
.Tests failed : 1
.Tests in error : 0
.Tests timed out : 0
{color:red}-1{color} [ERROR] There are [1] test failures in [core]. Listing
only the first [5] ones
testIfNoCustomFsConfigProvidedBaseConfigRemainsTheSame:org.apache.oozie.service.TestHadoopAccessorService
Check console output for the full list of errors/failures
.{color:orange}Tests failed at first run:{color}
TestCoordActionsKillXCommand#testActionKillCommandActionNumbers
TestCoordActionsKillXCommand#testActionKillCommandDate
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/158/
> Prepare ssh-wrapper script to handle callback specific arguments with quotes
>
>
> Key: OOZIE-3682
> URL: https://issues.apache.org/jira/browse/OOZIE-3682
> Project: Oozie
> Issue Type: Bug
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3682-001.patch, OOZIE-3682-002.patch
>
>
> In case someone runs an SSH action which connects from Oozie server (linux)
> to an AIX host, then the ssh-wrapper process is showing up on the remote
> host, but it hangs forever.
> This happens because the quotes around the callback URL are being retained in
> the arguments taken by ssh-base and sent to ssh-wrapper, causing an infinite
> loop.
> The goal of this ticket is to track the fix of this issue in the callback
> mechanism.
--
This message was sent by Atlassian Jira
[jira] [Commented] (OOZIE-3679) Correct maximum wait time between database retry attempts property
[
https://issues.apache.org/jira/browse/OOZIE-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643306#comment-17643306
]
Hadoop QA commented on OOZIE-3679:
--
Testing JIRA OOZIE-3679
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 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} 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 [23] new bugs found below threshold in total
that must be fixed.
.{color:green}+1{color} There are no new bugs found in [examples].
.{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 [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/distcp].
.{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/sqoop].
.{color:green}+1{color} There are no new bugs found in [sharelib/spark].
.{color:red}-1{color} There are [1] new bugs found below threshold in
[sharelib/oozie] that must be fixed.
.You can find the SpotBugs diff here (look for the red and orange ones):
sharelib/oozie/findbugs-new.html
.The most important SpotBugs errors are:
.At ShellMain.java:[line 93]: This usage of
java/lang/ProcessBuilder.init(Ljava/util/List;)V can be vulnerable to
Command Injection
.At ShellMain.java:[line 91]: At ShellMain.java:[line 90]
.At ShellMain.java:[line 92]
.{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/streaming].
.{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 [docs].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{color:red}-1{color} There are [7] new bugs found below threshold in
[core] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
core/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At BulkJPAExecutor.java:[line 206]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175]
.At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199]
.This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206]
.At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127]
.{color:red}-1{color} There are [15] new bugs found below threshold in
[tools] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
tools/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At OozieDBCLI.java:[line 584]: This use of
java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be vulnerable to SQL
injection
.At OozieDBCLI.java:[line 574]: At OozieDBCLI.java:[line 573]
.At OozieDBCLI.java:[line 577]: At OozieDBCLI.java:[line 575]
.At OozieDBCLI.java:[line 579]: At OozieDBCLI.java:[line 578]
.At OozieDBCLI.java:[line 584]: At OozieDBCLI.java:[line 581]
.{color:green}+1{color} There are no new bugs found in [client].
{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
[jira] [Commented] (OOZIE-3682) Prepare ssh-wrapper script to handle callback specific arguments with quotes
[ https://issues.apache.org/jira/browse/OOZIE-3682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643249#comment-17643249 ] Hadoop QA commented on OOZIE-3682: -- PreCommit-OOZIE-Build started > Prepare ssh-wrapper script to handle callback specific arguments with quotes > > > Key: OOZIE-3682 > URL: https://issues.apache.org/jira/browse/OOZIE-3682 > Project: Oozie > Issue Type: Bug >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3682-001.patch, OOZIE-3682-002.patch > > > In case someone runs an SSH action which connects from Oozie server (linux) > to an AIX host, then the ssh-wrapper process is showing up on the remote > host, but it hangs forever. > This happens because the quotes around the callback URL are being retained in > the arguments taken by ssh-base and sent to ssh-wrapper, causing an infinite > loop. > The goal of this ticket is to track the fix of this issue in the callback > mechanism. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3679) Correct maximum wait time between database retry attempts property
[
https://issues.apache.org/jira/browse/OOZIE-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643211#comment-17643211
]
Hadoop QA commented on OOZIE-3679:
--
PreCommit-OOZIE-Build started
> Correct maximum wait time between database retry attempts property
> --
>
> Key: OOZIE-3679
> URL: https://issues.apache.org/jira/browse/OOZIE-3679
> Project: Oozie
> Issue Type: Bug
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3679-001.patch, OOZIE-3679-002.patch
>
>
> Based on the oozie-default.xml:
> {code:xml}
>
> oozie.service.JPAService.retry.maximum-wait-time.ms
> 3
>
> Maximum wait time between database retry attempts.
>
>
> {code}
> it looks like we are missing a "{_}retry{_}" string before the maximum wait
> time between database retry attempts static string in Oozie's JPAService:
> {code:java}
> public static final String MAX_WAIT_TIME = CONF_PREFIX +
> "maximum-wait-time.ms";
> {code}
> {color:#172b4d}The goal of this change is to sync the config names between
> oozie-default.xml and Oozie but we should also support the old, invalid
> config name.{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3680) Add default value to custom configuration of all the supported file systems in Oozie
[
https://issues.apache.org/jira/browse/OOZIE-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642103#comment-17642103
]
Hadoop QA commented on OOZIE-3680:
--
Testing JIRA OOZIE-3680
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch does not add/modify any testcase
{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:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{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 [server].
.{color:green}+1{color} There are no new bugs found in [core].
.{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/hive2].
.{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/streaming].
.{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/git].
.{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/pig].
.{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/sqoop].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:green}+1{color} There are no new bugs found in [examples].
{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:red}-1 TESTS{color}
.Tests run: 2860
.Tests failed : 0
.Tests in error : 95
.Tests timed out : 1
{color:red}-1{color} [ERROR] There are [95] test errors in [core]. Listing only
the first [5] ones
testCoordActionsGetByActionNumber:org.apache.oozie.executor.jpa.TestCoordJobGetActionByActionNumberJPAExecutor
Check console output for the full list of errors/failures
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/154/
> Add default value to custom configuration of all the supported file systems
> in Oozie
>
>
> Key: OOZIE-3680
> URL: https://issues.apache.org/jira/browse/OOZIE-3680
> Project: Oozie
> Issue Type: Improvement
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3680-001.patch
>
>
> The default supported file systems now include: hdfs, hftp, webhdfs, s3a,
> abfs, abfss.
> The goal of this ticket is to make sure the users don't have to set
> explicitely the oozie.service.HadoopAccessorService.supported.filesystems
> property if they want to use any of the above mentioned supported file
> systems.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3682) Prepare ssh-wrapper script to handle callback specific arguments with quotes
[
https://issues.apache.org/jira/browse/OOZIE-3682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642059#comment-17642059
]
Hadoop QA commented on OOZIE-3682:
--
Testing JIRA OOZIE-3682
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch does not add/modify any testcase
{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:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/streaming].
.{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/spark].
.{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/git].
.{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/oozie].
.{color:green}+1{color} There are no new bugs found in [sharelib/pig].
.{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 [client].
.{color:green}+1{color} There are no new bugs found in [server].
.{color:green}+1{color} There are no new bugs found in [docs].
{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: 3253
.{color:orange}Tests failed at first run:{color}
TestCoordActionsKillXCommand#testActionKillCommandDate
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/156/
> Prepare ssh-wrapper script to handle callback specific arguments with quotes
>
>
> Key: OOZIE-3682
> URL: https://issues.apache.org/jira/browse/OOZIE-3682
> Project: Oozie
> Issue Type: Bug
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3682-001.patch
>
>
> In case someone runs an SSH action which connects from Oozie server (linux)
> to an AIX host, then the ssh-wrapper process is showing up on the remote
> host, but it hangs forever.
> This happens because the quotes around the callback URL are being retained in
> the arguments taken by ssh-base and sent to ssh-wrapper, causing an infinite
> loop.
> The goal of this ticket is to track the fix of this issue in the callback
> mechanism.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3681) Revise yarn.app and mapreduce property overrides in Oozie
[
https://issues.apache.org/jira/browse/OOZIE-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642043#comment-17642043
]
Hadoop QA commented on OOZIE-3681:
--
Testing JIRA OOZIE-3681
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch contains 6 line(s) longer than 132
characters
.{color:red}-1{color} the patch does not add/modify any testcase
{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:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [examples].
.{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 [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/distcp].
.{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/sqoop].
.{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/oozie].
.{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/streaming].
.{color:green}+1{color} There are no new bugs found in [server].
.{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{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [client].
{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: 3249
.{color:orange}Tests failed at first run:{color}
TestCoordActionsKillXCommand#testActionKillCommandDate
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/155/
> Revise yarn.app and mapreduce property overrides in Oozie
> -
>
> Key: OOZIE-3681
> URL: https://issues.apache.org/jira/browse/OOZIE-3681
> Project: Oozie
> Issue Type: Improvement
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3681-001.patch
>
>
> According to the following documentation
> [https://hadoop.apache.org/docs/r3.1.2/hadoop-yarn/hadoop-yarn-site/ResourceModel.html]
> oozie.launcher.override.memory.mb and oozie.launcher.override.vcores are
> outdated so the goal is to extend them with currently accepted property keys.
> The current keys should be in the beginning of the list to have the highest
> priority. Legacy overrides need to at end of the lists:
> oozie.launcher.mapreduce.map.memory.mb &
> oozie.launcher.mapreduce.map.cpu.vcores &
> oozie.launcher.mapreduce.map.java.opts
> The old keys should *not* be deleted to preserve backward compatibility of
> Oozie and workflow configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3682) Prepare ssh-wrapper script to handle callback specific arguments with quotes
[ https://issues.apache.org/jira/browse/OOZIE-3682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642004#comment-17642004 ] Hadoop QA commented on OOZIE-3682: -- PreCommit-OOZIE-Build started > Prepare ssh-wrapper script to handle callback specific arguments with quotes > > > Key: OOZIE-3682 > URL: https://issues.apache.org/jira/browse/OOZIE-3682 > Project: Oozie > Issue Type: Bug >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3682-001.patch > > > In case someone runs an SSH action which connects from Oozie server (linux) > to an AIX host, then the ssh-wrapper process is showing up on the remote > host, but it hangs forever. > This happens because the quotes around the callback URL are being retained in > the arguments taken by ssh-base and sent to ssh-wrapper, causing an infinite > loop. > The goal of this ticket is to track the fix of this issue in the callback > mechanism. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3681) Revise yarn.app and mapreduce property overrides in Oozie
[ https://issues.apache.org/jira/browse/OOZIE-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641958#comment-17641958 ] Hadoop QA commented on OOZIE-3681: -- PreCommit-OOZIE-Build started > Revise yarn.app and mapreduce property overrides in Oozie > - > > Key: OOZIE-3681 > URL: https://issues.apache.org/jira/browse/OOZIE-3681 > Project: Oozie > Issue Type: Improvement >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3681-001.patch > > > According to the following documentation > [https://hadoop.apache.org/docs/r3.1.2/hadoop-yarn/hadoop-yarn-site/ResourceModel.html] > oozie.launcher.override.memory.mb and oozie.launcher.override.vcores are > outdated so the goal is to extend them with currently accepted property keys. > The current keys should be in the beginning of the list to have the highest > priority. Legacy overrides need to at end of the lists: > oozie.launcher.mapreduce.map.memory.mb & > oozie.launcher.mapreduce.map.cpu.vcores & > oozie.launcher.mapreduce.map.java.opts > The old keys should *not* be deleted to preserve backward compatibility of > Oozie and workflow configuration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3679) Correct maximum wait time between database retry attempts property
[
https://issues.apache.org/jira/browse/OOZIE-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641900#comment-17641900
]
Hadoop QA commented on OOZIE-3679:
--
Testing JIRA OOZIE-3679
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 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} 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 [16] new bugs found below threshold in total
that must be fixed.
.{color:green}+1{color} There are no new bugs found in [examples].
.{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 [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/distcp].
.{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/sqoop].
.{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/oozie].
.{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/streaming].
.{color:green}+1{color} There are no new bugs found in [server].
.{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:red}-1{color} There are [1] 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 SLAEmailEventListener.java:[line 294]: Possible injection that can lead
to Source spoofing, header override and email body injection.
.At SLAEmailEventListener.java:[line 287]: At
SLAEmailEventListener.java:[line 286]
.At SLAEmailEventListener.java:[line 289]: At
SLAEmailEventListener.java:[line 288]
.At SLAEmailEventListener.java:[line 294]
.{color:red}-1{color} There are [15] new bugs found below threshold in
[tools] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
tools/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At OozieDBCLI.java:[line 584]: This use of
java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be vulnerable to SQL
injection
.At OozieDBCLI.java:[line 574]: At OozieDBCLI.java:[line 573]
.At OozieDBCLI.java:[line 577]: At OozieDBCLI.java:[line 575]
.At OozieDBCLI.java:[line 579]: At OozieDBCLI.java:[line 578]
.At OozieDBCLI.java:[line 584]: At OozieDBCLI.java:[line 581]
.{color:green}+1{color} There are no new bugs found in [client].
{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: 3250
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/153/
> Correct maximum wait time between database retry attempts property
> --
>
> Key: OOZIE-3679
> URL: https://issues.apache.org/jira/browse/OOZIE-3679
> Project: Oozie
> Issue Type: Bug
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority:
[jira] [Commented] (OOZIE-3680) Add default value to custom configuration of all the supported file systems in Oozie
[ https://issues.apache.org/jira/browse/OOZIE-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641850#comment-17641850 ] Hadoop QA commented on OOZIE-3680: -- PreCommit-OOZIE-Build started > Add default value to custom configuration of all the supported file systems > in Oozie > > > Key: OOZIE-3680 > URL: https://issues.apache.org/jira/browse/OOZIE-3680 > Project: Oozie > Issue Type: Improvement >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3680-001.patch > > > The default supported file systems now include: hdfs, hftp, webhdfs, s3a, > abfs, abfss. > The goal of this ticket is to make sure the users don't have to set > explicitely the oozie.service.HadoopAccessorService.supported.filesystems > property if they want to use any of the above mentioned supported file > systems. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3679) Correct maximum wait time between database retry attempts property
[
https://issues.apache.org/jira/browse/OOZIE-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641831#comment-17641831
]
Hadoop QA commented on OOZIE-3679:
--
PreCommit-OOZIE-Build started
> Correct maximum wait time between database retry attempts property
> --
>
> Key: OOZIE-3679
> URL: https://issues.apache.org/jira/browse/OOZIE-3679
> Project: Oozie
> Issue Type: Bug
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3679-001.patch
>
>
> Based on the oozie-default.xml:
> {code:xml}
>
> oozie.service.JPAService.retry.maximum-wait-time.ms
> 3
>
> Maximum wait time between database retry attempts.
>
>
> {code}
> it looks like we are missing a "{_}retry{_}" string before the maximum wait
> time between database retry attempts static string in Oozie's JPAService:
> {code:java}
> public static final String MAX_WAIT_TIME = CONF_PREFIX +
> "maximum-wait-time.ms";
> {code}
> {color:#172b4d}The goal of this change is to sync the config names between
> oozie-default.xml and Oozie but we should also support the old, invalid
> config name.{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3678) Reduce the number of NameNode access when starting the Yarn job
[
https://issues.apache.org/jira/browse/OOZIE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641506#comment-17641506
]
Hadoop QA commented on OOZIE-3678:
--
Testing JIRA OOZIE-3678
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 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} 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 [6] new bugs found below threshold in total that
must be fixed.
.{color:red}-1{color} There are [6] new bugs found below threshold in
[core] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
core/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At BulkJPAExecutor.java:[line 206]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175]
.At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199]
.This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206]
.At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127]
.{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
[fluent-job/fluent-job-api].
.{color:green}+1{color} There are no new bugs found in [server].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{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/spark].
.{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/hcatalog].
.{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/hive2].
.{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/hive].
.{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/git].
{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: 3249
.{color:orange}Tests failed at first run:{color}
TestBatchQueryExecutor#testExecuteBatchUpdateInsertDelete
TestJMSAccessorService#testConnectionRetry
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/152/
> Reduce the number of NameNode access when starting the Yarn job
> ---
>
> Key: OOZIE-3678
> URL: https://issues.apache.org/jira/browse/OOZIE-3678
> Project: Oozie
> Issue Type: Improvement
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3678-001.patch, OOZIE-3678-002.patch
>
>
> Before Oozie starts the
[jira] [Commented] (OOZIE-3606) Extend file system EL functions to use custom file system properties
[
https://issues.apache.org/jira/browse/OOZIE-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641483#comment-17641483
]
Hadoop QA commented on OOZIE-3606:
--
Testing JIRA OOZIE-3606
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 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} 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 [20] new bugs found below threshold in total
that must be fixed.
.{color:green}+1{color} There are no new bugs found in [examples].
.{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 [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/distcp].
.{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/sqoop].
.{color:green}+1{color} There are no new bugs found in [sharelib/spark].
.{color:red}-1{color} There are [1] new bugs found below threshold in
[sharelib/oozie] that must be fixed.
.You can find the SpotBugs diff here (look for the red and orange ones):
sharelib/oozie/findbugs-new.html
.The most important SpotBugs errors are:
.At ShellMain.java:[line 93]: This usage of
java/lang/ProcessBuilder.init(Ljava/util/List;)V can be vulnerable to
Command Injection
.At ShellMain.java:[line 91]: At ShellMain.java:[line 90]
.At ShellMain.java:[line 92]
.{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/streaming].
.{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 [docs].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{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 BulkJPAExecutor.java:[line 206]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175]
.At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199]
.java/io/File.init(Ljava/lang/String;Ljava/lang/String;)V reads a
file whose location might be specified by user input: At
BulkJPAExecutor.java:[line 206]
.At AuthorizationService.java:[line 189]: At
AuthorizationService.java:[line 192]
.{color:red}-1{color} There are [15] new bugs found below threshold in
[tools] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
tools/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At OozieDBCLI.java:[line 584]: This use of
java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be vulnerable to SQL
injection
.At OozieDBCLI.java:[line 574]: At OozieDBCLI.java:[line 573]
.At OozieDBCLI.java:[line 577]: At OozieDBCLI.java:[line 575]
.At OozieDBCLI.java:[line 579]: At OozieDBCLI.java:[line 578]
.At OozieDBCLI.java:[line 584]: At OozieDBCLI.java:[line 581]
.{color:green}+1{color} There are no new bugs found in [client].
{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: 3250
.
[jira] [Commented] (OOZIE-3678) Reduce the number of NameNode access when starting the Yarn job
[
https://issues.apache.org/jira/browse/OOZIE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641451#comment-17641451
]
Hadoop QA commented on OOZIE-3678:
--
PreCommit-OOZIE-Build started
> Reduce the number of NameNode access when starting the Yarn job
> ---
>
> Key: OOZIE-3678
> URL: https://issues.apache.org/jira/browse/OOZIE-3678
> Project: Oozie
> Issue Type: Improvement
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3678-001.patch, OOZIE-3678-002.patch
>
>
> Before Oozie starts the Yarn application it assembles the class path which's
> elements' paths are resolved with
> {code:java}
> remoteFS.resolvePath(p){code}
> which can cause slowness and high NameNode load.
> The intention is to make this path resolution configurable (ability to turn
> it on/off) via an Oozie configuration thus customers can turn it off when
> they experience job start slowness. Default value should result the new
> behaviour is active.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3678) Reduce the number of NameNode access when starting the Yarn job
[
https://issues.apache.org/jira/browse/OOZIE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641447#comment-17641447
]
Hadoop QA commented on OOZIE-3678:
--
Testing JIRA OOZIE-3678
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 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} 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 [6] new bugs found below threshold in total that
must be fixed.
.{color:red}-1{color} There are [6] new bugs found below threshold in
[core] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
core/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At BulkJPAExecutor.java:[line 206]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175]
.At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199]
.This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206]
.At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127]
.{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
[fluent-job/fluent-job-api].
.{color:green}+1{color} There are no new bugs found in [server].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{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/spark].
.{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/hcatalog].
.{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/hive2].
.{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/hive].
.{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/git].
{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: 3249
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/150/
> Reduce the number of NameNode access when starting the Yarn job
> ---
>
> Key: OOZIE-3678
> URL: https://issues.apache.org/jira/browse/OOZIE-3678
> Project: Oozie
> Issue Type: Improvement
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3678-001.patch
>
>
> Before Oozie starts the Yarn application it assembles the class path which's
> elements' paths are resolved with
> {code:java}
> remoteFS.resolvePath(p){code}
> which can cause slowness and high NameNode load.
> The intention is to make this path resolution configurable
[jira] [Commented] (OOZIE-3606) Extend file system EL functions to use custom file system properties
[ https://issues.apache.org/jira/browse/OOZIE-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641431#comment-17641431 ] Hadoop QA commented on OOZIE-3606: -- PreCommit-OOZIE-Build started > Extend file system EL functions to use custom file system properties > > > Key: OOZIE-3606 > URL: https://issues.apache.org/jira/browse/OOZIE-3606 > Project: Oozie > Issue Type: Improvement > Components: core >Affects Versions: 5.2.0 >Reporter: Dénes Bodó >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3606-001.patch, OOZIE-3606-002.patch, > OOZIE-3606-003.patch > > > In case we want to check file availability on abfss file system in scope of a > decision node and we have access to that file system only using a key file > which is password protected then currently we are blocked as we cannot allow > configuring hadoop.security.credstore.java-keystore-provider.password-file > globally. > This is why this ticket is created to propose a solution for this issue: > * allow special file system configurations only for file system EL functions > * let them configure globally via oozie-site.xml and for every workflow > independently -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3678) Reduce the number of NameNode access when starting the Yarn job
[
https://issues.apache.org/jira/browse/OOZIE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641372#comment-17641372
]
Hadoop QA commented on OOZIE-3678:
--
PreCommit-OOZIE-Build started
> Reduce the number of NameNode access when starting the Yarn job
> ---
>
> Key: OOZIE-3678
> URL: https://issues.apache.org/jira/browse/OOZIE-3678
> Project: Oozie
> Issue Type: Improvement
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3678-001.patch
>
>
> Before Oozie starts the Yarn application it assembles the class path which's
> elements' paths are resolved with
> {code:java}
> remoteFS.resolvePath(p){code}
> which can cause slowness and high NameNode load.
> The intention is to make this path resolution configurable (ability to turn
> it on/off) via an Oozie configuration thus customers can turn it off when
> they experience job start slowness. Default value should result the new
> behaviour is active.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3677) Oozie should accept a keyStoreType and trustStoreType property in oozie-site.xml
[
https://issues.apache.org/jira/browse/OOZIE-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641251#comment-17641251
]
Hadoop QA commented on OOZIE-3677:
--
Testing JIRA OOZIE-3677
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:orange}0{color} There are [4] new bugs found in total that would be nice
to have fixed.
.{color:green}+1{color} There are no new bugs found in [examples].
.{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 [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/distcp].
.{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/sqoop].
.{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/oozie].
.{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/streaming].
.{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 [docs].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{color:green}+1{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [client].
{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: 3251
.{color:orange}Tests failed at first run:{color}
TestCoordActionsKillXCommand#testActionKillCommandActionNumbers
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:green}*+1 Overall result, good!, no -1s*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/149/
> Oozie should accept a keyStoreType and trustStoreType property in
> oozie-site.xml
>
>
> Key: OOZIE-3677
> URL: https://issues.apache.org/jira/browse/OOZIE-3677
> Project: Oozie
> Issue Type: Improvement
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3677-001.patch
>
>
> In scope of making Oozie FIPS compliant, when TLS is enabled, the Oozie
> server expects a JKS KeyStore type even though the following Java system
> properties are being set:
> {code:java}
> -Djavax.net.ssl.keyStoreType=bcfks -Djavax.net.ssl.trustStoreType=bcfks{code}
> The goal of ticket is to make Oozie capable of setting _keyStoreType_ and
> _trustStoreType_ in oozie-site.xml if it's not already set by the user.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3677) Oozie should accept a keyStoreType and trustStoreType property in oozie-site.xml
[ https://issues.apache.org/jira/browse/OOZIE-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641197#comment-17641197 ] Hadoop QA commented on OOZIE-3677: -- PreCommit-OOZIE-Build started > Oozie should accept a keyStoreType and trustStoreType property in > oozie-site.xml > > > Key: OOZIE-3677 > URL: https://issues.apache.org/jira/browse/OOZIE-3677 > Project: Oozie > Issue Type: Improvement >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3677-001.patch > > > The goal of ticket is to make Oozie capable of setting _keyStoreType_ and > _trustStoreType_ in oozie-site.xml if it's not already set by the user. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3670) Actions can stuck while running in a Fork-Join workflow
[
https://issues.apache.org/jira/browse/OOZIE-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17640866#comment-17640866
]
Hadoop QA commented on OOZIE-3670:
--
Testing JIRA OOZIE-3670
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 3 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 [6] new bugs found below threshold in total that
must be fixed.
.{color:green}+1{color} There are no new bugs found in [examples].
.{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 [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/distcp].
.{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/sqoop].
.{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/oozie].
.{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/streaming].
.{color:green}+1{color} There are no new bugs found in [server].
.{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:red}-1{color} There are [6] new bugs found below threshold in
[core] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
core/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At BulkJPAExecutor.java:[line 206]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175]
.At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199]
.This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206]
.At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127]
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [client].
{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: 3246
.{color:orange}Tests failed at first run:{color}
TestCoordActionsKillXCommand#testActionKillCommandActionNumbers
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/148/
> Actions can stuck while running in a Fork-Join workflow
> ---
>
> Key: OOZIE-3670
> URL: https://issues.apache.org/jira/browse/OOZIE-3670
> Project: Oozie
> Issue Type: Bug
> Components: core
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3670-001.patch, forkjoin.xml, helloworld.sh,
> job.properties
>
>
> Fork node splits one path of
[jira] [Commented] (OOZIE-3670) Actions can stuck while running in a Fork-Join workflow
[
https://issues.apache.org/jira/browse/OOZIE-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17640785#comment-17640785
]
Hadoop QA commented on OOZIE-3670:
--
PreCommit-OOZIE-Build started
> Actions can stuck while running in a Fork-Join workflow
> ---
>
> Key: OOZIE-3670
> URL: https://issues.apache.org/jira/browse/OOZIE-3670
> Project: Oozie
> Issue Type: Bug
> Components: core
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3670-001.patch, forkjoin.xml, helloworld.sh,
> job.properties
>
>
> Fork node splits one path of execution into multiple concurrent paths of
> execution and the join node waits until every concurrent execution path of a
> previous fork node arrives to it. Given a scenario, when one of the paths
> [action] fails for some exotic reason - in our case (see attachment) with an
> EL Error - then the workflow job itself will fail as well, however the other
> actions running parallelly under the same workflow job will stuck in RUNNING
> state until they are purged, which can lead to Oozie slow-down in extreme
> cases.
> This behaviour can be reproduced using the attached
> [forkjoin.xml{^}!https://jira.cloudera.com/images/icons/link_attachment_7.gif|width=7,height=7,align=absmiddle!{^}|https://jira.cloudera.com/secure/attachment/531918/531918_forkjoin.xml],
>
> [job.properties{^}!https://jira.cloudera.com/images/icons/link_attachment_7.gif|width=7,height=7,align=absmiddle!{^}|https://jira.cloudera.com/secure/attachment/531916/531916_job.properties],
> and
> [helloworld.sh{^}!https://jira.cloudera.com/images/icons/link_attachment_7.gif|width=7,height=7,align=absmiddle!{^}|https://jira.cloudera.com/secure/attachment/531917/531917_helloworld.sh].
> In the above workflow, [action2] will fail due to ELError because
> {code:java}
> ${variableThatWillCauseELError} {code}
> could not be evaluated, but at the same time [action1] tries to complete
> itself but remains in RUNNING state.
> We have examined the situation at surface level, but we need to get a deeper
> understanding regarding the mechanism of fork-join workflows to proceed
> further.
> Suspected classes are for starting point:
> - org.apache.oozie.workflow.lite.LiteWorkflowInstance
> - org.apache.oozie.command.wf.ActionCheckXCommand
> - what if we do not throw Exception in
> org.apache.oozie.command.wf.ActionCheckXCommand#verifyPrecondition ?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3676) Remove all non FIPS compliant encoding algorithms from Oozie or make them configurable
[
https://issues.apache.org/jira/browse/OOZIE-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17640760#comment-17640760
]
Hadoop QA commented on OOZIE-3676:
--
Testing JIRA OOZIE-3676
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 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} 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 [5] new bugs found below threshold in total that
must be fixed.
.{color:green}+1{color} There are no new bugs found in [examples].
.{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 [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/distcp].
.{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/sqoop].
.{color:green}+1{color} There are no new bugs found in [sharelib/spark].
.{color:red}-1{color} There are [1] new bugs found below threshold in
[sharelib/oozie] that must be fixed.
.You can find the SpotBugs diff here (look for the red and orange ones):
sharelib/oozie/findbugs-new.html
.The most important SpotBugs errors are:
.At ShellMain.java:[line 93]: This usage of
java/lang/ProcessBuilder.init(Ljava/util/List;)V can be vulnerable to
Command Injection
.At ShellMain.java:[line 91]: At ShellMain.java:[line 90]
.At ShellMain.java:[line 92]
.{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/streaming].
.{color:green}+1{color} There are no new bugs found in [server].
.{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: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 BulkJPAExecutor.java:[line 206]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175]
.At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199]
.This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206]
.At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127]
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [client].
{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: 3227
.{color:orange}Tests failed at first run:{color}
TestCLIParser#testCommandParserShowHelpWithOptions
TestLocalOozieClientCoord#testJobsOperations
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/147/
> Remove all non FIPS compliant encoding algorithms from Oozie or make them
> configurable
>
[jira] [Commented] (OOZIE-3676) Remove all non FIPS compliant encoding algorithms from Oozie or make them configurable
[
https://issues.apache.org/jira/browse/OOZIE-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17640678#comment-17640678
]
Hadoop QA commented on OOZIE-3676:
--
PreCommit-OOZIE-Build started
> Remove all non FIPS compliant encoding algorithms from Oozie or make them
> configurable
> --
>
> Key: OOZIE-3676
> URL: https://issues.apache.org/jira/browse/OOZIE-3676
> Project: Oozie
> Issue Type: Task
> Components: core
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3676-001.patch
>
>
> The goal of this Jira is to replace non-FIPS compliant encoding algorithm(s)
> to FIPS compliant algorithm(s) in Oozie.
> At this moment only `org.apache.oozie.action.hadoop.LauncherHelper#getTag`
> has non-FIPS compliant algorithm, namely MD-5.
> In scope of this ticket, this algorithm will be changed to FIPS compliant
> SHA-384.
> ({_}read more about the FIPS compliant algorithms below{_})
>
> h2. Using FIPS-Compliant Crypto Libraries
> This should not need much code change. Ensure that when you are performing
> crypto operations (e.g. generating keys, encrypting/decrypting data,
> computing hashes, storing/verifying passwords), you are using either OpenSSL
> or the standard Java crypto API to do so.
> When running in a FIPS environment, the OpenSSL library and Java crypto
> provider will be replaced with their CryptoComply equivalents. This
> replacement should be API-compatible.
> h2. Using FIPS-Approved Algorithms
> Only certain algorithms and key sizes are allowed by FIPS.
> Common allowed algorithms are shown below for convenience:
> Symmetric Algorithms
> * AES
> * 3DES
> Public Key Algorithms
> * RSA
> * ElGamal
> Key Agreement Algorithms
> * DH
> * MQV
> * ECDH
> * ECCDH
> * ECMQV
> SSL/TLS
> * TLS 1.0, 1.1, 1.2
> Hash Functions
> * SHA-1 _(avoid this as it is soon to be deprecated)_
> * SHA-224, SHA-256 {_}(avoid these as they are soon to be deprecated){_},
> SHA-384, SHA-512
> * SHA3-224, SHA3-256, SHA3-384, SHA3-512
> * SHAKE128, SHAKE256
> Message Authentication
> * AES CCM, CMAC, GMAC
> * HMAC with SHA-1, SHA-224, SHA-256, SHA-384, SHA-512
> * 3DES CMAC
> Password Derivation Functions
> * PBKDF2 with SHA-1, SHA-224, SHA-256, SHA-384, SHA-512
> Random Number Generators
> * HASH DRBG
> * HMAC DRBG
> * CTR DRBG
> Signature Algorithms
> * DSA using SHA-1, SHA-224, SHA-256, SHA-384, SHA-512
> * ECDSA using SHA-1, SHA-224, SHA-256, SHA-384, SHA-512
> * RSA using SHA-1, SHA-224, SHA-256, SHA-384, SHA-512
> Keep in mind that the following common algorithms are *disallowed* and will
> likely cause a crash if invoked in FIPS mode:
> * MD5: use SHA-384 instead
> * RC4 (also called arcfour): use AES-256 instead
> * SSL: use TLS instead
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3670) Actions can stuck while running in a Fork-Join workflow
[
https://issues.apache.org/jira/browse/OOZIE-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17640660#comment-17640660
]
Hadoop QA commented on OOZIE-3670:
--
Testing JIRA OOZIE-3670
Cleaning local git workspace
{color:red}-1{color} Patch failed to apply to head of branch
> Actions can stuck while running in a Fork-Join workflow
> ---
>
> Key: OOZIE-3670
> URL: https://issues.apache.org/jira/browse/OOZIE-3670
> Project: Oozie
> Issue Type: Bug
> Components: core
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3670-001.patch, OOZIE-3670-002.patch,
> forkjoin.xml, helloworld.sh, job.properties
>
>
> Fork node splits one path of execution into multiple concurrent paths of
> execution and the join node waits until every concurrent execution path of a
> previous fork node arrives to it. Given a scenario, when one of the paths
> [action] fails for some exotic reason - in our case (see attachment) with an
> EL Error - then the workflow job itself will fail as well, however the other
> actions running parallelly under the same workflow job will stuck in RUNNING
> state until they are purged, which can lead to Oozie slow-down in extreme
> cases.
> This behaviour can be reproduced using the attached
> [forkjoin.xml{^}!https://jira.cloudera.com/images/icons/link_attachment_7.gif|width=7,height=7,align=absmiddle!{^}|https://jira.cloudera.com/secure/attachment/531918/531918_forkjoin.xml],
>
> [job.properties{^}!https://jira.cloudera.com/images/icons/link_attachment_7.gif|width=7,height=7,align=absmiddle!{^}|https://jira.cloudera.com/secure/attachment/531916/531916_job.properties],
> and
> [helloworld.sh{^}!https://jira.cloudera.com/images/icons/link_attachment_7.gif|width=7,height=7,align=absmiddle!{^}|https://jira.cloudera.com/secure/attachment/531917/531917_helloworld.sh].
> In the above workflow, [action2] will fail due to ELError because
> {code:java}
> ${variableThatWillCauseELError} {code}
> could not be evaluated, but at the same time [action1] tries to complete
> itself but remains in RUNNING state.
> We have examined the situation at surface level, but we need to get a deeper
> understanding regarding the mechanism of fork-join workflows to proceed
> further.
> Suspected classes are for starting point:
> - org.apache.oozie.workflow.lite.LiteWorkflowInstance
> - org.apache.oozie.command.wf.ActionCheckXCommand
> - what if we do not throw Exception in
> org.apache.oozie.command.wf.ActionCheckXCommand#verifyPrecondition ?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3670) Actions can stuck while running in a Fork-Join workflow
[
https://issues.apache.org/jira/browse/OOZIE-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17640649#comment-17640649
]
Hadoop QA commented on OOZIE-3670:
--
PreCommit-OOZIE-Build started
> Actions can stuck while running in a Fork-Join workflow
> ---
>
> Key: OOZIE-3670
> URL: https://issues.apache.org/jira/browse/OOZIE-3670
> Project: Oozie
> Issue Type: Bug
> Components: core
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3670-001.patch, OOZIE-3670-002.patch,
> forkjoin.xml, helloworld.sh, job.properties
>
>
> Fork node splits one path of execution into multiple concurrent paths of
> execution and the join node waits until every concurrent execution path of a
> previous fork node arrives to it. Given a scenario, when one of the paths
> [action] fails for some exotic reason - in our case (see attachment) with an
> EL Error - then the workflow job itself will fail as well, however the other
> actions running parallelly under the same workflow job will stuck in RUNNING
> state until they are purged, which can lead to Oozie slow-down in extreme
> cases.
> This behaviour can be reproduced using the attached
> [forkjoin.xml{^}!https://jira.cloudera.com/images/icons/link_attachment_7.gif|width=7,height=7,align=absmiddle!{^}|https://jira.cloudera.com/secure/attachment/531918/531918_forkjoin.xml],
>
> [job.properties{^}!https://jira.cloudera.com/images/icons/link_attachment_7.gif|width=7,height=7,align=absmiddle!{^}|https://jira.cloudera.com/secure/attachment/531916/531916_job.properties],
> and
> [helloworld.sh{^}!https://jira.cloudera.com/images/icons/link_attachment_7.gif|width=7,height=7,align=absmiddle!{^}|https://jira.cloudera.com/secure/attachment/531917/531917_helloworld.sh].
> In the above workflow, [action2] will fail due to ELError because
> {code:java}
> ${variableThatWillCauseELError} {code}
> could not be evaluated, but at the same time [action1] tries to complete
> itself but remains in RUNNING state.
> We have examined the situation at surface level, but we need to get a deeper
> understanding regarding the mechanism of fork-join workflows to proceed
> further.
> Suspected classes are for starting point:
> - org.apache.oozie.workflow.lite.LiteWorkflowInstance
> - org.apache.oozie.command.wf.ActionCheckXCommand
> - what if we do not throw Exception in
> org.apache.oozie.command.wf.ActionCheckXCommand#verifyPrecondition ?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3674) Add a --insecure like parameter to Oozie client so it can ignore certificate errors
[
https://issues.apache.org/jira/browse/OOZIE-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17640296#comment-17640296
]
Hadoop QA commented on OOZIE-3674:
--
Testing JIRA OOZIE-3674
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 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} 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 [21] new bugs found below threshold in total
that must be fixed.
.{color:red}-1{color} There are [6] new bugs found below threshold in
[core] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
core/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At BulkJPAExecutor.java:[line 206]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175]
.At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199]
.This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206]
.At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127]
.{color:orange}0{color} There are [2] new bugs found in [client] that would
be nice to have fixed.
.You can find the SpotBugs diff here: client/findbugs-new.html
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
.{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 [15] new bugs found below threshold in
[tools] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
tools/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At OozieDBCLI.java:[line 584]: This use of
java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be vulnerable to SQL
injection
.At OozieDBCLI.java:[line 574]: At OozieDBCLI.java:[line 573]
.At OozieDBCLI.java:[line 577]: At OozieDBCLI.java:[line 575]
.At OozieDBCLI.java:[line 579]: At OozieDBCLI.java:[line 578]
.At OozieDBCLI.java:[line 584]: At OozieDBCLI.java:[line 581]
.{color:green}+1{color} There are no new bugs found in [webapp].
.{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/spark].
.{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/hcatalog].
.{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/hive2].
.{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/hive].
.{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/git].
{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: 3244
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is
[jira] [Commented] (OOZIE-3674) Add a --insecure like parameter to Oozie client so it can ignore certificate errors
[
https://issues.apache.org/jira/browse/OOZIE-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17640267#comment-17640267
]
Hadoop QA commented on OOZIE-3674:
--
PreCommit-OOZIE-Build started
> Add a --insecure like parameter to Oozie client so it can ignore certificate
> errors
> ---
>
> Key: OOZIE-3674
> URL: https://issues.apache.org/jira/browse/OOZIE-3674
> Project: Oozie
> Issue Type: Task
> Components: client
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3674-001.patch, OOZIE-3674-002.patch,
> OOZIE-3674-003.patch, OOZIE-3674-004.patch, OOZIE-3674-005.patch,
> OOZIE-3674-006.patch, OOZIE-3674-007.patch
>
>
> Currently when SSL is enabled you need to pass the -Djavax.net.ssl.trustStore
> and -Djavax.net.ssl.trustStorePassword system properties to the Oozie client
> or you need to import the certificate into the JDK's cert store otherwise
> Oozie client won't be able to connect to the Oozie server. Always passing
> these variables is very inconvenient, and another solution might be to allow
> certificate errors in the client. This would be like the curl
> *{color:#0747a6}--insecure{color}* option. The data would still be encrypted,
> but the client would not check the certificate. This should not be turned on
> by default in the Oozie client, but this could be a new command line
> parameter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3674) Add a --insecure like parameter to Oozie client so it can ignore certificate errors
[
https://issues.apache.org/jira/browse/OOZIE-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17640226#comment-17640226
]
Hadoop QA commented on OOZIE-3674:
--
Testing JIRA OOZIE-3674
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch contains 2 line(s) longer than 132
characters
.{color:green}+1{color} the patch 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} 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 [22] new bugs found below threshold in total
that must be fixed.
.{color:red}-1{color} There are [6] new bugs found below threshold in
[core] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
core/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At BulkJPAExecutor.java:[line 206]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175]
.At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199]
.This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206]
.At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127]
.{color:red}-1{color} There are [1] new bugs found below threshold in
[client] that must be fixed.
.You can find the SpotBugs diff here (look for the red and orange ones):
client/findbugs-new.html
.The most important SpotBugs errors are:
.At InsecureConnectionHelper.java:[line 64]: SSLContext needs to be
compatible with TLS 1.2
.{color:green}+1{color} There are no new bugs found in [docs].
.{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 [server].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:red}-1{color} There are [15] new bugs found below threshold in
[tools] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
tools/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At OozieDBCLI.java:[line 584]: This use of
java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be vulnerable to SQL
injection
.At OozieDBCLI.java:[line 574]: At OozieDBCLI.java:[line 573]
.At OozieDBCLI.java:[line 577]: At OozieDBCLI.java:[line 575]
.At OozieDBCLI.java:[line 579]: At OozieDBCLI.java:[line 578]
.At OozieDBCLI.java:[line 584]: At OozieDBCLI.java:[line 581]
.{color:green}+1{color} There are no new bugs found in [webapp].
.{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/spark].
.{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/hcatalog].
.{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/hive2].
.{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/hive].
.{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/git].
{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: 3244
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please
[jira] [Commented] (OOZIE-3674) Add a --insecure like parameter to Oozie client so it can ignore certificate errors
[
https://issues.apache.org/jira/browse/OOZIE-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17640162#comment-17640162
]
Hadoop QA commented on OOZIE-3674:
--
PreCommit-OOZIE-Build started
> Add a --insecure like parameter to Oozie client so it can ignore certificate
> errors
> ---
>
> Key: OOZIE-3674
> URL: https://issues.apache.org/jira/browse/OOZIE-3674
> Project: Oozie
> Issue Type: Task
> Components: client
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3674-001.patch, OOZIE-3674-002.patch,
> OOZIE-3674-003.patch, OOZIE-3674-004.patch, OOZIE-3674-005.patch,
> OOZIE-3674-006.patch
>
>
> Currently when SSL is enabled you need to pass the -Djavax.net.ssl.trustStore
> and -Djavax.net.ssl.trustStorePassword system properties to the Oozie client
> or you need to import the certificate into the JDK's cert store otherwise
> Oozie client won't be able to connect to the Oozie server. Always passing
> these variables is very inconvenient, and another solution might be to allow
> certificate errors in the client. This would be like the curl
> *{color:#0747a6}--insecure{color}* option. The data would still be encrypted,
> but the client would not check the certificate. This should not be turned on
> by default in the Oozie client, but this could be a new command line
> parameter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3674) Add a --insecure like parameter to Oozie client so it can ignore certificate errors
[
https://issues.apache.org/jira/browse/OOZIE-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17640014#comment-17640014
]
Hadoop QA commented on OOZIE-3674:
--
Testing JIRA OOZIE-3674
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch contains 2 line(s) longer than 132
characters
.{color:green}+1{color} the patch 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} 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 [22] new bugs found below threshold in total
that must be fixed.
.{color:red}-1{color} There are [6] new bugs found below threshold in
[core] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
core/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At BulkJPAExecutor.java:[line 206]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175]
.At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199]
.This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206]
.At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127]
.{color:red}-1{color} There are [1] new bugs found below threshold in
[client] that must be fixed.
.You can find the SpotBugs diff here (look for the red and orange ones):
client/findbugs-new.html
.The most important SpotBugs errors are:
.At InsecureConnectionHelper.java:[line 64]: SSLContext needs to be
compatible with TLS 1.2
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
.{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 [15] new bugs found below threshold in
[tools] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
tools/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At OozieDBCLI.java:[line 584]: This use of
java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be vulnerable to SQL
injection
.At OozieDBCLI.java:[line 574]: At OozieDBCLI.java:[line 573]
.At OozieDBCLI.java:[line 577]: At OozieDBCLI.java:[line 575]
.At OozieDBCLI.java:[line 579]: At OozieDBCLI.java:[line 578]
.At OozieDBCLI.java:[line 584]: At OozieDBCLI.java:[line 581]
.{color:green}+1{color} There are no new bugs found in [webapp].
.{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/spark].
.{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/hcatalog].
.{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/hive2].
.{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/hive].
.{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/git].
{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: 18
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
[jira] [Commented] (OOZIE-3674) Add a --insecure like parameter to Oozie client so it can ignore certificate errors
[
https://issues.apache.org/jira/browse/OOZIE-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639982#comment-17639982
]
Hadoop QA commented on OOZIE-3674:
--
PreCommit-OOZIE-Build started
> Add a --insecure like parameter to Oozie client so it can ignore certificate
> errors
> ---
>
> Key: OOZIE-3674
> URL: https://issues.apache.org/jira/browse/OOZIE-3674
> Project: Oozie
> Issue Type: Task
> Components: client
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3674-001.patch, OOZIE-3674-002.patch,
> OOZIE-3674-003.patch, OOZIE-3674-004.patch, OOZIE-3674-005.patch
>
>
> Currently when SSL is enabled you need to pass the -Djavax.net.ssl.trustStore
> and -Djavax.net.ssl.trustStorePassword system properties to the Oozie client
> or you need to import the certificate into the JDK's cert store otherwise
> Oozie client won't be able to connect to the Oozie server. Always passing
> these variables is very inconvenient, and another solution might be to allow
> certificate errors in the client. This would be like the curl
> *{color:#0747a6}--insecure{color}* option. The data would still be encrypted,
> but the client would not check the certificate. This should not be turned on
> by default in the Oozie client, but this could be a new command line
> parameter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3674) Add a --insecure like parameter to Oozie client so it can ignore certificate errors
[
https://issues.apache.org/jira/browse/OOZIE-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639720#comment-17639720
]
Hadoop QA commented on OOZIE-3674:
--
Testing JIRA OOZIE-3674
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch contains 2 line(s) longer than 132
characters
.{color:green}+1{color} the patch 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} 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:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{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 [server].
.{color:green}+1{color} There are no new bugs found in [core].
.{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/hive2].
.{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/streaming].
.{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/git].
.{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/pig].
.{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/sqoop].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:green}+1{color} There are no new bugs found in [examples].
{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:red}-1 TESTS{color}
.Tests run: 2895
.Tests failed : 0
.Tests in error : 86
.Tests timed out : 1
{color:red}-1{color} [ERROR] There are [86] test errors in [core]. Listing only
the first [5] ones
testCoordActionsGetByActionNumber:org.apache.oozie.executor.jpa.TestCoordJobGetActionByActionNumberJPAExecutor
Check console output for the full list of errors/failures
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/142/
> Add a --insecure like parameter to Oozie client so it can ignore certificate
> errors
> ---
>
> Key: OOZIE-3674
> URL: https://issues.apache.org/jira/browse/OOZIE-3674
> Project: Oozie
> Issue Type: Task
> Components: client
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3674-001.patch, OOZIE-3674-002.patch,
> OOZIE-3674-003.patch, OOZIE-3674-004.patch
>
>
> Currently when SSL is enabled you need to pass the -Djavax.net.ssl.trustStore
> and -Djavax.net.ssl.trustStorePassword system properties to the Oozie client
> or you need to import the certificate into the JDK's cert store otherwise
> Oozie client won't be able to connect to the Oozie server. Always passing
> these variables is very inconvenient, and another solution might be to allow
> certificate errors in the client. This would be like the curl
> *{color:#0747a6}--insecure{color}* option. The data would still be encrypted,
> but the client would not check the certificate. This should not be turned on
> by default in
[jira] [Commented] (OOZIE-3674) Add a --insecure like parameter to Oozie client so it can ignore certificate errors
[
https://issues.apache.org/jira/browse/OOZIE-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639670#comment-17639670
]
Hadoop QA commented on OOZIE-3674:
--
PreCommit-OOZIE-Build started
> Add a --insecure like parameter to Oozie client so it can ignore certificate
> errors
> ---
>
> Key: OOZIE-3674
> URL: https://issues.apache.org/jira/browse/OOZIE-3674
> Project: Oozie
> Issue Type: Task
> Components: client
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3674-001.patch, OOZIE-3674-002.patch,
> OOZIE-3674-003.patch, OOZIE-3674-004.patch
>
>
> Currently when SSL is enabled you need to pass the -Djavax.net.ssl.trustStore
> and -Djavax.net.ssl.trustStorePassword system properties to the Oozie client
> or you need to import the certificate into the JDK's cert store otherwise
> Oozie client won't be able to connect to the Oozie server. Always passing
> these variables is very inconvenient, and another solution might be to allow
> certificate errors in the client. This would be like the curl
> *{color:#0747a6}--insecure{color}* option. The data would still be encrypted,
> but the client would not check the certificate. This should not be turned on
> by default in the Oozie client, but this could be a new command line
> parameter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3674) Add a --insecure like parameter to Oozie client so it can ignore certificate errors
[
https://issues.apache.org/jira/browse/OOZIE-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638432#comment-17638432
]
Hadoop QA commented on OOZIE-3674:
--
Testing JIRA OOZIE-3674
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch contains 2 line(s) longer than 132
characters
.{color:green}+1{color} the patch 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} 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:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [examples].
.{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 [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/distcp].
.{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/sqoop].
.{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/oozie].
.{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/streaming].
.{color:green}+1{color} There are no new bugs found in [server].
.{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{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [client].
{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:red}-1 TESTS{color}
.Tests run: 2749
.Tests failed : 0
.Tests in error : 0
.Tests timed out : 1
Check console output for the full list of errors/failures
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/141/
> Add a --insecure like parameter to Oozie client so it can ignore certificate
> errors
> ---
>
> Key: OOZIE-3674
> URL: https://issues.apache.org/jira/browse/OOZIE-3674
> Project: Oozie
> Issue Type: Task
> Components: client
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3674-001.patch, OOZIE-3674-002.patch,
> OOZIE-3674-003.patch
>
>
> Currently when SSL is enabled you need to pass the -Djavax.net.ssl.trustStore
> and -Djavax.net.ssl.trustStorePassword system properties to the Oozie client
> or you need to import the certificate into the JDK's cert store otherwise
> Oozie client won't be able to connect to the Oozie server. Always passing
> these variables is very inconvenient, and another solution might be to allow
> certificate errors in the client. This would be like the curl
> *{color:#0747a6}--insecure{color}* option. The data would still be encrypted,
> but the client would not check the certificate. This should not be turned on
> by default in the Oozie client, but this could be a new command line
> parameter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3674) Add a --insecure like parameter to Oozie client so it can ignore certificate errors
[
https://issues.apache.org/jira/browse/OOZIE-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638421#comment-17638421
]
Hadoop QA commented on OOZIE-3674:
--
PreCommit-OOZIE-Build started
> Add a --insecure like parameter to Oozie client so it can ignore certificate
> errors
> ---
>
> Key: OOZIE-3674
> URL: https://issues.apache.org/jira/browse/OOZIE-3674
> Project: Oozie
> Issue Type: Task
> Components: client
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3674-001.patch, OOZIE-3674-002.patch,
> OOZIE-3674-003.patch
>
>
> Currently when SSL is enabled you need to pass the -Djavax.net.ssl.trustStore
> and -Djavax.net.ssl.trustStorePassword system properties to the Oozie client
> or you need to import the certificate into the JDK's cert store otherwise
> Oozie client won't be able to connect to the Oozie server. Always passing
> these variables is very inconvenient, and another solution might be to allow
> certificate errors in the client. This would be like the curl
> *{color:#0747a6}--insecure{color}* option. The data would still be encrypted,
> but the client would not check the certificate. This should not be turned on
> by default in the Oozie client, but this could be a new command line
> parameter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3674) Add a --insecure like parameter to Oozie client so it can ignore certificate errors
[
https://issues.apache.org/jira/browse/OOZIE-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638420#comment-17638420
]
Hadoop QA commented on OOZIE-3674:
--
Testing JIRA OOZIE-3674
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch contains 2 line(s) longer than 132
characters
.{color:green}+1{color} the patch 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} 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:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [examples].
.{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 [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/distcp].
.{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/sqoop].
.{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/oozie].
.{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/streaming].
.{color:green}+1{color} There are no new bugs found in [server].
.{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{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [client].
{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:red}-1 TESTS{color}
.Tests run: 2674
.Tests failed : 0
.Tests in error : 0
.Tests timed out : 1
Check console output for the full list of errors/failures
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/140/
> Add a --insecure like parameter to Oozie client so it can ignore certificate
> errors
> ---
>
> Key: OOZIE-3674
> URL: https://issues.apache.org/jira/browse/OOZIE-3674
> Project: Oozie
> Issue Type: Task
> Components: client
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3674-001.patch, OOZIE-3674-002.patch,
> OOZIE-3674-003.patch
>
>
> Currently when SSL is enabled you need to pass the -Djavax.net.ssl.trustStore
> and -Djavax.net.ssl.trustStorePassword system properties to the Oozie client
> or you need to import the certificate into the JDK's cert store otherwise
> Oozie client won't be able to connect to the Oozie server. Always passing
> these variables is very inconvenient, and another solution might be to allow
> certificate errors in the client. This would be like the curl
> *{color:#0747a6}--insecure{color}* option. The data would still be encrypted,
> but the client would not check the certificate. This should not be turned on
> by default in the Oozie client, but this could be a new command line
> parameter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3674) Add a --insecure like parameter to Oozie client so it can ignore certificate errors
[
https://issues.apache.org/jira/browse/OOZIE-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638398#comment-17638398
]
Hadoop QA commented on OOZIE-3674:
--
PreCommit-OOZIE-Build started
> Add a --insecure like parameter to Oozie client so it can ignore certificate
> errors
> ---
>
> Key: OOZIE-3674
> URL: https://issues.apache.org/jira/browse/OOZIE-3674
> Project: Oozie
> Issue Type: Task
> Components: client
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3674-001.patch, OOZIE-3674-002.patch
>
>
> Currently when SSL is enabled you need to pass the -Djavax.net.ssl.trustStore
> and -Djavax.net.ssl.trustStorePassword system properties to the Oozie client
> or you need to import the certificate into the JDK's cert store otherwise
> Oozie client won't be able to connect to the Oozie server. Always passing
> these variables is very inconvenient, and another solution might be to allow
> certificate errors in the client. This would be like the curl
> *{color:#0747a6}--insecure{color}* option. The data would still be encrypted,
> but the client would not check the certificate. This should not be turned on
> by default in the Oozie client, but this could be a new command line
> parameter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3674) Add a --insecure like parameter to Oozie client so it can ignore certificate errors
[
https://issues.apache.org/jira/browse/OOZIE-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638397#comment-17638397
]
Hadoop QA commented on OOZIE-3674:
--
Testing JIRA OOZIE-3674
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch contains 2 line(s) longer than 132
characters
.{color:green}+1{color} the patch 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} 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:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [examples].
.{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 [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/distcp].
.{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/sqoop].
.{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/oozie].
.{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/streaming].
.{color:green}+1{color} There are no new bugs found in [server].
.{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{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [client].
{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:red}-1 TESTS{color}
.Tests run: 2714
.Tests failed : 0
.Tests in error : 0
.Tests timed out : 1
Check console output for the full list of errors/failures
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/139/
> Add a --insecure like parameter to Oozie client so it can ignore certificate
> errors
> ---
>
> Key: OOZIE-3674
> URL: https://issues.apache.org/jira/browse/OOZIE-3674
> Project: Oozie
> Issue Type: Task
> Components: client
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3674-001.patch, OOZIE-3674-002.patch
>
>
> Currently when SSL is enabled you need to pass the -Djavax.net.ssl.trustStore
> and -Djavax.net.ssl.trustStorePassword system properties to the Oozie client
> or you need to import the certificate into the JDK's cert store otherwise
> Oozie client won't be able to connect to the Oozie server. Always passing
> these variables is very inconvenient, and another solution might be to allow
> certificate errors in the client. This would be like the curl
> *{color:#0747a6}--insecure{color}* option. The data would still be encrypted,
> but the client would not check the certificate. This should not be turned on
> by default in the Oozie client, but this could be a new command line
> parameter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3674) Add a --insecure like parameter to Oozie client so it can ignore certificate errors
[
https://issues.apache.org/jira/browse/OOZIE-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638357#comment-17638357
]
Hadoop QA commented on OOZIE-3674:
--
PreCommit-OOZIE-Build started
> Add a --insecure like parameter to Oozie client so it can ignore certificate
> errors
> ---
>
> Key: OOZIE-3674
> URL: https://issues.apache.org/jira/browse/OOZIE-3674
> Project: Oozie
> Issue Type: Task
> Components: client
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3674-001.patch, OOZIE-3674-002.patch
>
>
> Currently when SSL is enabled you need to pass the -Djavax.net.ssl.trustStore
> and -Djavax.net.ssl.trustStorePassword system properties to the Oozie client
> or you need to import the certificate into the JDK's cert store otherwise
> Oozie client won't be able to connect to the Oozie server. Always passing
> these variables is very inconvenient, and another solution might be to allow
> certificate errors in the client. This would be like the curl
> *{color:#0747a6}--insecure{color}* option. The data would still be encrypted,
> but the client would not check the certificate. This should not be turned on
> by default in the Oozie client, but this could be a new command line
> parameter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[
https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638290#comment-17638290
]
Hadoop QA commented on OOZIE-3675:
--
Testing JIRA OOZIE-3675
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 5 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:orange}0{color} There are [4] new bugs found in total that would be nice
to have fixed.
.{color:green}+1{color} There are no new bugs found in [examples].
.{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 [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/distcp].
.{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/sqoop].
.{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/oozie].
.{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/streaming].
.{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 [docs].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{color:green}+1{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [client].
{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: 3226
.{color:orange}Tests failed at first run:{color}
TestLocalOozieClientCoord#testJobsOperations
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:green}*+1 Overall result, good!, no -1s*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/138/
> Upgrade Mockito from 2 to 3.11.2
>
>
> Key: OOZIE-3675
> URL: https://issues.apache.org/jira/browse/OOZIE-3675
> Project: Oozie
> Issue Type: Task
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch,
> OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch,
> OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch,
> OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch,
> OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch,
> OOZIE-3675-015.patch, OOZIE-3675-016.patch, OOZIE-3675-017.patch,
> OOZIE-3675-018.patch, OOZIE-3675-019.patch, OOZIE-3675-020.patch
>
>
> The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[ https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638255#comment-17638255 ] Hadoop QA commented on OOZIE-3675: -- PreCommit-OOZIE-Build started > Upgrade Mockito from 2 to 3.11.2 > > > Key: OOZIE-3675 > URL: https://issues.apache.org/jira/browse/OOZIE-3675 > Project: Oozie > Issue Type: Task >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch, > OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch, > OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch, > OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch, > OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch, > OOZIE-3675-015.patch, OOZIE-3675-016.patch, OOZIE-3675-017.patch, > OOZIE-3675-018.patch, OOZIE-3675-019.patch, OOZIE-3675-020.patch > > > The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[
https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638153#comment-17638153
]
Hadoop QA commented on OOZIE-3675:
--
Testing JIRA OOZIE-3675
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 5 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:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [examples].
.{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 [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/distcp].
.{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/sqoop].
.{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/oozie].
.{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/streaming].
.{color:green}+1{color} There are no new bugs found in [server].
.{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{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [client].
{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: 3226
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:green}*+1 Overall result, good!, no -1s*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/137/
> Upgrade Mockito from 2 to 3.11.2
>
>
> Key: OOZIE-3675
> URL: https://issues.apache.org/jira/browse/OOZIE-3675
> Project: Oozie
> Issue Type: Task
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch,
> OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch,
> OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch,
> OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch,
> OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch,
> OOZIE-3675-015.patch, OOZIE-3675-016.patch, OOZIE-3675-017.patch,
> OOZIE-3675-018.patch, OOZIE-3675-019.patch
>
>
> The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[ https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638107#comment-17638107 ] Hadoop QA commented on OOZIE-3675: -- PreCommit-OOZIE-Build started > Upgrade Mockito from 2 to 3.11.2 > > > Key: OOZIE-3675 > URL: https://issues.apache.org/jira/browse/OOZIE-3675 > Project: Oozie > Issue Type: Task >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch, > OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch, > OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch, > OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch, > OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch, > OOZIE-3675-015.patch, OOZIE-3675-016.patch, OOZIE-3675-017.patch, > OOZIE-3675-018.patch, OOZIE-3675-019.patch > > > The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[
https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638000#comment-17638000
]
Hadoop QA commented on OOZIE-3675:
--
Testing JIRA OOZIE-3675
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 5 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:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [examples].
.{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 [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/distcp].
.{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/sqoop].
.{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/oozie].
.{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/streaming].
.{color:green}+1{color} There are no new bugs found in [server].
.{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{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [client].
{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: 3226
.{color:orange}Tests failed at first run:{color}
TestCLIParser#testCommandParserShowHelpWithOptions
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:green}*+1 Overall result, good!, no -1s*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/136/
> Upgrade Mockito from 2 to 3.11.2
>
>
> Key: OOZIE-3675
> URL: https://issues.apache.org/jira/browse/OOZIE-3675
> Project: Oozie
> Issue Type: Task
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch,
> OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch,
> OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch,
> OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch,
> OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch,
> OOZIE-3675-015.patch, OOZIE-3675-016.patch, OOZIE-3675-017.patch,
> OOZIE-3675-018.patch, OOZIE-3675-019.patch
>
>
> The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[ https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637969#comment-17637969 ] Hadoop QA commented on OOZIE-3675: -- PreCommit-OOZIE-Build started > Upgrade Mockito from 2 to 3.11.2 > > > Key: OOZIE-3675 > URL: https://issues.apache.org/jira/browse/OOZIE-3675 > Project: Oozie > Issue Type: Task >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch, > OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch, > OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch, > OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch, > OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch, > OOZIE-3675-015.patch, OOZIE-3675-016.patch, OOZIE-3675-017.patch, > OOZIE-3675-018.patch, OOZIE-3675-019.patch > > > The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[
https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637940#comment-17637940
]
Hadoop QA commented on OOZIE-3675:
--
Testing JIRA OOZIE-3675
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 5 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:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [examples].
.{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 [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/distcp].
.{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/sqoop].
.{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/oozie].
.{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/streaming].
.{color:green}+1{color} There are no new bugs found in [server].
.{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{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [client].
{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: 3226
.{color:orange}Tests failed at first run:{color}
TestCoordActionsKillXCommand#testActionKillCommandDate
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:green}*+1 Overall result, good!, no -1s*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/135/
> Upgrade Mockito from 2 to 3.11.2
>
>
> Key: OOZIE-3675
> URL: https://issues.apache.org/jira/browse/OOZIE-3675
> Project: Oozie
> Issue Type: Task
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch,
> OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch,
> OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch,
> OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch,
> OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch,
> OOZIE-3675-015.patch, OOZIE-3675-016.patch, OOZIE-3675-017.patch,
> OOZIE-3675-018.patch, OOZIE-3675-019.patch
>
>
> The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[ https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637893#comment-17637893 ] Hadoop QA commented on OOZIE-3675: -- PreCommit-OOZIE-Build started > Upgrade Mockito from 2 to 3.11.2 > > > Key: OOZIE-3675 > URL: https://issues.apache.org/jira/browse/OOZIE-3675 > Project: Oozie > Issue Type: Task >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch, > OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch, > OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch, > OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch, > OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch, > OOZIE-3675-015.patch, OOZIE-3675-016.patch, OOZIE-3675-017.patch, > OOZIE-3675-018.patch, OOZIE-3675-019.patch > > > The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[
https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637879#comment-17637879
]
Hadoop QA commented on OOZIE-3675:
--
Testing JIRA OOZIE-3675
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 5 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:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [examples].
.{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 [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/distcp].
.{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/sqoop].
.{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/oozie].
.{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/streaming].
.{color:green}+1{color} There are no new bugs found in [server].
.{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{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [client].
{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: 3226
.{color:orange}Tests failed at first run:{color}
TestCoordActionsKillXCommand#testActionKillCommandDate
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:green}*+1 Overall result, good!, no -1s*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/134/
> Upgrade Mockito from 2 to 3.11.2
>
>
> Key: OOZIE-3675
> URL: https://issues.apache.org/jira/browse/OOZIE-3675
> Project: Oozie
> Issue Type: Task
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch,
> OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch,
> OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch,
> OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch,
> OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch,
> OOZIE-3675-015.patch, OOZIE-3675-016.patch, OOZIE-3675-017.patch,
> OOZIE-3675-018.patch, OOZIE-3675-019.patch
>
>
> The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[ https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637819#comment-17637819 ] Hadoop QA commented on OOZIE-3675: -- PreCommit-OOZIE-Build started > Upgrade Mockito from 2 to 3.11.2 > > > Key: OOZIE-3675 > URL: https://issues.apache.org/jira/browse/OOZIE-3675 > Project: Oozie > Issue Type: Task >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch, > OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch, > OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch, > OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch, > OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch, > OOZIE-3675-015.patch, OOZIE-3675-016.patch, OOZIE-3675-017.patch, > OOZIE-3675-018.patch, OOZIE-3675-019.patch > > > The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[
https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637605#comment-17637605
]
Hadoop QA commented on OOZIE-3675:
--
Testing JIRA OOZIE-3675
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 3 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 [1] new bugs found below threshold in total that
must be fixed.
.{color:green}+1{color} There are no new bugs found in [examples].
.{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 [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/distcp].
.{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/sqoop].
.{color:green}+1{color} There are no new bugs found in [sharelib/spark].
.{color:red}-1{color} There are [1] new bugs found below threshold in
[sharelib/oozie] that must be fixed.
.You can find the SpotBugs diff here (look for the red and orange ones):
sharelib/oozie/findbugs-new.html
.The most important SpotBugs errors are:
.At ShellMain.java:[line 93]: This usage of
java/lang/ProcessBuilder.init(Ljava/util/List;)V can be vulnerable to
Command Injection
.At ShellMain.java:[line 91]: At ShellMain.java:[line 90]
.At ShellMain.java:[line 92]
.{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/streaming].
.{color:green}+1{color} There are no new bugs found in [server].
.{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{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [client].
{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:red}-1 TESTS{color}
.Tests run: 3226
.Tests failed : 0
.Tests in error : 2
.Tests timed out : 0
{color:red}-1{color} [ERROR] There are [2] test errors in [tools]. Listing only
the first [5] ones
testHelpCommand:org.apache.oozie.tools.TestOozieSharelibCLI
testFakeCommand:org.apache.oozie.tools.TestOozieSharelibCLI
Check console output for the full list of errors/failures
.{color:orange}Tests failed at first run:{color}
TestLauncherMain#testLog4jPropertiesPresentAndReadable
TestCoordActionsKillXCommand#testActionKillCommandDate
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/133/
> Upgrade Mockito from 2 to 3.11.2
>
>
> Key: OOZIE-3675
> URL: https://issues.apache.org/jira/browse/OOZIE-3675
> Project: Oozie
> Issue Type: Task
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch,
> OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch,
> OOZIE-3675-006.patch, OOZIE-3675-007.patch,
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[ https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637573#comment-17637573 ] Hadoop QA commented on OOZIE-3675: -- PreCommit-OOZIE-Build started > Upgrade Mockito from 2 to 3.11.2 > > > Key: OOZIE-3675 > URL: https://issues.apache.org/jira/browse/OOZIE-3675 > Project: Oozie > Issue Type: Task >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch, > OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch, > OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch, > OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch, > OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch, > OOZIE-3675-015.patch, OOZIE-3675-016.patch, OOZIE-3675-017.patch, > OOZIE-3675-018.patch > > > The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[
https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637499#comment-17637499
]
Hadoop QA commented on OOZIE-3675:
--
Testing JIRA OOZIE-3675
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 3 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:orange}0{color} There are [4] new bugs found in total that would be nice
to have fixed.
.{color:green}+1{color} There are no new bugs found in [core].
.{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
[fluent-job/fluent-job-api].
.{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:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{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/spark].
.{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/hcatalog].
.{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/hive2].
.{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/hive].
.{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/git].
{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: 3226
.{color:orange}Tests failed at first run:{color}
TestLauncherMain#testLog4jPropertiesPresentAndReadable
TestOozieSharelibCLI#testFakeCommand
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:green}*+1 Overall result, good!, no -1s*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/132/
> Upgrade Mockito from 2 to 3.11.2
>
>
> Key: OOZIE-3675
> URL: https://issues.apache.org/jira/browse/OOZIE-3675
> Project: Oozie
> Issue Type: Task
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch,
> OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch,
> OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch,
> OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch,
> OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch,
> OOZIE-3675-015.patch, OOZIE-3675-016.patch, OOZIE-3675-017.patch,
> OOZIE-3675-018.patch
>
>
> The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[ https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637455#comment-17637455 ] Hadoop QA commented on OOZIE-3675: -- PreCommit-OOZIE-Build started > Upgrade Mockito from 2 to 3.11.2 > > > Key: OOZIE-3675 > URL: https://issues.apache.org/jira/browse/OOZIE-3675 > Project: Oozie > Issue Type: Task >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch, > OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch, > OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch, > OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch, > OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch, > OOZIE-3675-015.patch, OOZIE-3675-016.patch, OOZIE-3675-017.patch, > OOZIE-3675-018.patch > > > The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[
https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637451#comment-17637451
]
Hadoop QA commented on OOZIE-3675:
--
Testing JIRA OOZIE-3675
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 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} 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:orange}0{color} There are [4] new bugs found in total that would be nice
to have fixed.
.{color:green}+1{color} There are no new bugs found in [core].
.{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
[fluent-job/fluent-job-api].
.{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:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{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/spark].
.{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/hcatalog].
.{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/hive2].
.{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/hive].
.{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/git].
{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:red}-1 TESTS{color}
.Tests run: 3188
.Tests failed : 1
.Tests in error : 0
.Tests timed out : 0
{color:red}-1{color} [ERROR] There are [1] test failures in [client]. Listing
only the first [5] ones
testValidationPrintBundleJobsOutput:org.apache.oozie.cli.TestOozieCLIMethods
Check console output for the full list of errors/failures
.{color:orange}Tests failed at first run:{color}
TestOozieCLIMethods#testValidatePrintCoordJobMethodOutput
TestOozieCLIMethods#testValidatePrintCoordJobsOutput
TestOozieCLIMethods#testValidatePrintJobsOutput
TestOozieCLIMethods#testValidatePrintWorkflowActionOutput
TestDateUtils#testOozieInOtherTZ
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/131/
> Upgrade Mockito from 2 to 3.11.2
>
>
> Key: OOZIE-3675
> URL: https://issues.apache.org/jira/browse/OOZIE-3675
> Project: Oozie
> Issue Type: Task
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch,
> OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch,
> OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch,
> OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch,
> OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch,
> OOZIE-3675-015.patch, OOZIE-3675-016.patch,
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[ https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637419#comment-17637419 ] Hadoop QA commented on OOZIE-3675: -- PreCommit-OOZIE-Build started > Upgrade Mockito from 2 to 3.11.2 > > > Key: OOZIE-3675 > URL: https://issues.apache.org/jira/browse/OOZIE-3675 > Project: Oozie > Issue Type: Task >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch, > OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch, > OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch, > OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch, > OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch, > OOZIE-3675-015.patch, OOZIE-3675-016.patch, OOZIE-3675-017.patch > > > The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[
https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637415#comment-17637415
]
Hadoop QA commented on OOZIE-3675:
--
Testing JIRA OOZIE-3675
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 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} 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:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [core].
.{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
[fluent-job/fluent-job-api].
.{color:green}+1{color} There are no new bugs found in [server].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{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/spark].
.{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/hcatalog].
.{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/hive2].
.{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/hive].
.{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/git].
{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: 3226
.{color:orange}Tests failed at first run:{color}
TestOozieCLIMethods#testValidatePrintCoordJobsOutput
TestOozieCLIMethods#testValidatePrintJobOutput
TestLauncherMain#testLog4jPropertiesPresentAndReadable
TestDateUtils#testOozieInOtherTZ
TestOozieSharelibCLI#testFakeCommand
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:green}*+1 Overall result, good!, no -1s*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/130/
> Upgrade Mockito from 2 to 3.11.2
>
>
> Key: OOZIE-3675
> URL: https://issues.apache.org/jira/browse/OOZIE-3675
> Project: Oozie
> Issue Type: Task
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch,
> OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch,
> OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch,
> OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch,
> OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch,
> OOZIE-3675-015.patch, OOZIE-3675-016.patch, OOZIE-3675-017.patch
>
>
> The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[ https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637360#comment-17637360 ] Hadoop QA commented on OOZIE-3675: -- PreCommit-OOZIE-Build started > Upgrade Mockito from 2 to 3.11.2 > > > Key: OOZIE-3675 > URL: https://issues.apache.org/jira/browse/OOZIE-3675 > Project: Oozie > Issue Type: Task >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch, > OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch, > OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch, > OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch, > OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch, > OOZIE-3675-015.patch, OOZIE-3675-016.patch, OOZIE-3675-017.patch > > > The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[
https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637304#comment-17637304
]
Hadoop QA commented on OOZIE-3675:
--
Testing JIRA OOZIE-3675
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 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} 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:orange}0{color} There are [4] new bugs found in total that would be nice
to have fixed.
.{color:green}+1{color} There are no new bugs found in [core].
.{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
[fluent-job/fluent-job-api].
.{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:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{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/spark].
.{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/hcatalog].
.{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/hive2].
.{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/hive].
.{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/git].
{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:red}-1 TESTS{color}
.Tests run: 3226
.Tests failed : 0
.Tests in error : 26
.Tests timed out : 0
{color:red}-1{color} [ERROR] There are [26] test errors in [core]. Listing only
the first [5] ones
testSubmissionSuccessfulAfterDelay:org.apache.oozie.service.TestAsyncXCommandExecutor
testCannotSubmitDueToFiltering:org.apache.oozie.service.TestAsyncXCommandExecutor
testPendingCommandSubmissionWhenMaxConcurrencyReached:org.apache.oozie.service.TestAsyncXCommandExecutor
testSubmitCallableWithDelay:org.apache.oozie.service.TestAsyncXCommandExecutor
testQueueDump:org.apache.oozie.service.TestAsyncXCommandExecutor
Check console output for the full list of errors/failures
.{color:orange}Tests failed at first run:{color}
TestHdfsOperations#testActionDataUploadToHdfsFailsWhenAppendingToWriter
TestHdfsOperations#testActionDataUploadToHdfsFailsWhenWriterIsNull
TestLauncherAM#testActionThrowsSecurityExceptionWithExitCode0AndDoesNotPrintStackTrace
TestLauncherAM#testActionThrowsSecurityExceptionWithExitCode1AndPrintsStackTrace
TestLauncherAM#testActionThrowsSecurityExceptionWithoutSystemExit
TestLauncherAM#testActionThrowsThrowableAndAsyncErrorReceived
TestLauncherAM#testMainIsSuccessfullyInvokedAndAsyncErrorReceived
TestLauncherAM#testMainIsSuccessfullyInvokedWithActionData
TestLauncherAM#testMainIsSuccessfullyInvokedWithoutActionData
TestLauncherAM#testRecoveryIdExistsAndRecoveryIdsDoNotMatch
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/129/
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[ https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637246#comment-17637246 ] Hadoop QA commented on OOZIE-3675: -- PreCommit-OOZIE-Build started > Upgrade Mockito from 2 to 3.11.2 > > > Key: OOZIE-3675 > URL: https://issues.apache.org/jira/browse/OOZIE-3675 > Project: Oozie > Issue Type: Task >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch, > OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch, > OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch, > OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch, > OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch, > OOZIE-3675-015.patch, OOZIE-3675-016.patch > > > The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[
https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637229#comment-17637229
]
Hadoop QA commented on OOZIE-3675:
--
Testing JIRA OOZIE-3675
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 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} 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:orange}0{color} There are [4] new bugs found in total that would be nice
to have fixed.
.{color:green}+1{color} There are no new bugs found in [core].
.{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
[fluent-job/fluent-job-api].
.{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:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{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/spark].
.{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/hcatalog].
.{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/hive2].
.{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/hive].
.{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/git].
{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: 3226
.{color:orange}Tests failed at first run:{color}
TestHdfsOperations#testActionDataUploadToHdfsFailsWhenAppendingToWriter
TestHdfsOperations#testActionDataUploadToHdfsFailsWhenWriterIsNull
TestLauncherAM#testActionThrowsSecurityExceptionWithExitCode0AndDoesNotPrintStackTrace
TestLauncherAM#testActionThrowsSecurityExceptionWithExitCode1AndPrintsStackTrace
TestLauncherAM#testActionThrowsSecurityExceptionWithoutSystemExit
TestLauncherAM#testActionThrowsThrowableAndAsyncErrorReceived
TestLauncherAM#testMainIsSuccessfullyInvokedAndAsyncErrorReceived
TestLauncherAM#testMainIsSuccessfullyInvokedWithActionData
TestLauncherAM#testMainIsSuccessfullyInvokedWithoutActionData
TestLauncherAM#testRecoveryIdExistsAndRecoveryIdsDoNotMatch
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:green}*+1 Overall result, good!, no -1s*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/128/
> Upgrade Mockito from 2 to 3.11.2
>
>
> Key: OOZIE-3675
> URL: https://issues.apache.org/jira/browse/OOZIE-3675
> Project: Oozie
> Issue Type: Task
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch,
> OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch,
> OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch,
> OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch,
> OOZIE-3675-012.patch,
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[ https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637153#comment-17637153 ] Hadoop QA commented on OOZIE-3675: -- PreCommit-OOZIE-Build started > Upgrade Mockito from 2 to 3.11.2 > > > Key: OOZIE-3675 > URL: https://issues.apache.org/jira/browse/OOZIE-3675 > Project: Oozie > Issue Type: Task >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch, > OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch, > OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch, > OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch, > OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch, > OOZIE-3675-015.patch, OOZIE-3675-016.patch > > > The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[
https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637137#comment-17637137
]
Hadoop QA commented on OOZIE-3675:
--
Testing JIRA OOZIE-3675
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 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} 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:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [examples].
.{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 [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/distcp].
.{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/sqoop].
.{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/oozie].
.{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/streaming].
.{color:green}+1{color} There are no new bugs found in [server].
.{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{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [client].
{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: 3226
.{color:orange}Tests failed at first run:{color}
TestHdfsOperations#testActionDataUploadToHdfsFailsWhenAppendingToWriter
TestHdfsOperations#testActionDataUploadToHdfsFailsWhenWriterIsNull
TestLauncherAM#testActionThrowsSecurityExceptionWithExitCode0AndDoesNotPrintStackTrace
TestLauncherAM#testActionThrowsSecurityExceptionWithExitCode1AndPrintsStackTrace
TestLauncherAM#testActionThrowsSecurityExceptionWithoutSystemExit
TestLauncherAM#testActionThrowsThrowableAndAsyncErrorReceived
TestLauncherAM#testMainIsSuccessfullyInvokedAndAsyncErrorReceived
TestLauncherAM#testMainIsSuccessfullyInvokedWithActionData
TestLauncherAM#testMainIsSuccessfullyInvokedWithoutActionData
TestLauncherAM#testRecoveryIdExistsAndRecoveryIdsDoNotMatch
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:green}*+1 Overall result, good!, no -1s*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/127/
> Upgrade Mockito from 2 to 3.11.2
>
>
> Key: OOZIE-3675
> URL: https://issues.apache.org/jira/browse/OOZIE-3675
> Project: Oozie
> Issue Type: Task
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch,
> OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch,
> OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch,
> OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch,
> OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch,
> OOZIE-3675-015.patch, OOZIE-3675-016.patch
>
>
> The goal of this Jira is to upgrade Mockito version to
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[ https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637068#comment-17637068 ] Hadoop QA commented on OOZIE-3675: -- PreCommit-OOZIE-Build started > Upgrade Mockito from 2 to 3.11.2 > > > Key: OOZIE-3675 > URL: https://issues.apache.org/jira/browse/OOZIE-3675 > Project: Oozie > Issue Type: Task >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch, > OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch, > OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch, > OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch, > OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch, > OOZIE-3675-015.patch, OOZIE-3675-016.patch > > > The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[
https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17636933#comment-17636933
]
Hadoop QA commented on OOZIE-3675:
--
Testing JIRA OOZIE-3675
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch does not add/modify any testcase
{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:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [examples].
.{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 [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/distcp].
.{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/sqoop].
.{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/oozie].
.{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/streaming].
.{color:green}+1{color} There are no new bugs found in [server].
.{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{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [client].
{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:red}-1 TESTS{color}
.Tests run: 3226
.Tests failed : 0
.Tests in error : 2
.Tests timed out : 0
{color:red}-1{color} [ERROR] There are [2] test errors in [core]. Listing only
the first [5] ones
multibyteInputsAreAcceptedInScripts:org.apache.oozie.action.hadoop.TestScriptLanguageActionExecutor
Check console output for the full list of errors/failures
.{color:orange}Tests failed at first run:{color}
TestHdfsOperations#testActionDataUploadToHdfsFailsWhenAppendingToWriter
TestHdfsOperations#testActionDataUploadToHdfsFailsWhenWriterIsNull
TestLauncherAM#testActionThrowsSecurityExceptionWithExitCode0AndDoesNotPrintStackTrace
TestLauncherAM#testActionThrowsSecurityExceptionWithExitCode1AndPrintsStackTrace
TestLauncherAM#testActionThrowsSecurityExceptionWithoutSystemExit
TestLauncherAM#testActionThrowsThrowableAndAsyncErrorReceived
TestLauncherAM#testMainIsSuccessfullyInvokedAndAsyncErrorReceived
TestLauncherAM#testMainIsSuccessfullyInvokedWithActionData
TestLauncherAM#testMainIsSuccessfullyInvokedWithoutActionData
TestLauncherAM#testRecoveryIdExistsAndRecoveryIdsDoNotMatch
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/126/
> Upgrade Mockito from 2 to 3.11.2
>
>
> Key: OOZIE-3675
> URL: https://issues.apache.org/jira/browse/OOZIE-3675
> Project: Oozie
> Issue Type: Task
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch,
> OOZIE-3675-003.patch,
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[ https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17636898#comment-17636898 ] Hadoop QA commented on OOZIE-3675: -- PreCommit-OOZIE-Build started > Upgrade Mockito from 2 to 3.11.2 > > > Key: OOZIE-3675 > URL: https://issues.apache.org/jira/browse/OOZIE-3675 > Project: Oozie > Issue Type: Task >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch, > OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch, > OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch, > OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch, > OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch, > OOZIE-3675-015.patch > > > The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[
https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17636856#comment-17636856
]
Hadoop QA commented on OOZIE-3675:
--
Testing JIRA OOZIE-3675
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 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} 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 [1] new bugs found below threshold in total that
must be fixed.
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{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 [server].
.{color:green}+1{color} There are no new bugs found in [core].
.{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/hive2].
.{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/streaming].
.{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/git].
.{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/pig].
.{color:red}-1{color} There are [1] new bugs found below threshold in
[sharelib/oozie] that must be fixed.
.You can find the SpotBugs diff here (look for the red and orange ones):
sharelib/oozie/findbugs-new.html
.The most important SpotBugs errors are:
.At ShellMain.java:[line 93]: This usage of
java/lang/ProcessBuilder.init(Ljava/util/List;)V can be vulnerable to
Command Injection
.At ShellMain.java:[line 91]: At ShellMain.java:[line 90]
.At ShellMain.java:[line 92]
.{color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:green}+1{color} There are no new bugs found in [examples].
{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:red}-1 TESTS{color}
.Tests run: 2833
.Tests failed : 0
.Tests in error : 897
.Tests timed out : 1
{color:red}-1{color} [ERROR] There are [897] test errors in [core]. Listing
only the first [5] ones
testCoordActionsGetByActionNumber:org.apache.oozie.executor.jpa.TestCoordJobGetActionByActionNumberJPAExecutor
Check console output for the full list of errors/failures
.{color:orange}Tests failed at first run:{color}
TestHdfsOperations#testActionDataUploadToHdfsFailsWhenAppendingToWriter
TestHdfsOperations#testActionDataUploadToHdfsFailsWhenWriterIsNull
TestLauncherAM#testActionThrowsSecurityExceptionWithExitCode0AndDoesNotPrintStackTrace
TestLauncherAM#testActionThrowsSecurityExceptionWithExitCode1AndPrintsStackTrace
TestLauncherAM#testActionThrowsSecurityExceptionWithoutSystemExit
TestLauncherAM#testActionThrowsThrowableAndAsyncErrorReceived
TestLauncherAM#testMainIsSuccessfullyInvokedAndAsyncErrorReceived
TestLauncherAM#testMainIsSuccessfullyInvokedWithActionData
TestLauncherAM#testMainIsSuccessfullyInvokedWithoutActionData
TestLauncherAM#testRecoveryIdExistsAndRecoveryIdsDoNotMatch
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
.
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[ https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17636717#comment-17636717 ] Hadoop QA commented on OOZIE-3675: -- PreCommit-OOZIE-Build started > Upgrade Mockito from 2 to 3.11.2 > > > Key: OOZIE-3675 > URL: https://issues.apache.org/jira/browse/OOZIE-3675 > Project: Oozie > Issue Type: Task >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch, > OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch, > OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch, > OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch, > OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch > > > The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[ https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17636655#comment-17636655 ] Hadoop QA commented on OOZIE-3675: -- PreCommit-OOZIE-Build started > Upgrade Mockito from 2 to 3.11.2 > > > Key: OOZIE-3675 > URL: https://issues.apache.org/jira/browse/OOZIE-3675 > Project: Oozie > Issue Type: Task >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch, > OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch, > OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch, > OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch, > OOZIE-3675-012.patch, OOZIE-3675-013.patch, OOZIE-3675-014.patch > > > The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[
https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17636634#comment-17636634
]
Hadoop QA commented on OOZIE-3675:
--
Testing JIRA OOZIE-3675
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch does not add/modify any testcase
{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:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{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 [server].
.{color:green}+1{color} There are no new bugs found in [core].
.{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/hive2].
.{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/streaming].
.{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/git].
.{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/pig].
.{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/sqoop].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:green}+1{color} There are no new bugs found in [examples].
{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:red}-1 TESTS{color}
.Tests run: 3226
.Tests failed : 0
.Tests in error : 2
.Tests timed out : 0
{color:red}-1{color} [ERROR] There are [2] test errors in [core]. Listing only
the first [5] ones
multibyteInputsAreAcceptedInScripts:org.apache.oozie.action.hadoop.TestScriptLanguageActionExecutor
Check console output for the full list of errors/failures
.{color:orange}Tests failed at first run:{color}
TestHdfsOperations#testActionDataUploadToHdfsFailsWhenAppendingToWriter
TestHdfsOperations#testActionDataUploadToHdfsFailsWhenWriterIsNull
TestLauncherAM#testActionThrowsSecurityExceptionWithExitCode0AndDoesNotPrintStackTrace
TestLauncherAM#testActionThrowsSecurityExceptionWithExitCode1AndPrintsStackTrace
TestLauncherAM#testActionThrowsSecurityExceptionWithoutSystemExit
TestLauncherAM#testActionThrowsThrowableAndAsyncErrorReceived
TestLauncherAM#testMainIsSuccessfullyInvokedAndAsyncErrorReceived
TestLauncherAM#testMainIsSuccessfullyInvokedWithActionData
TestLauncherAM#testMainIsSuccessfullyInvokedWithoutActionData
TestLauncherAM#testRecoveryIdExistsAndRecoveryIdsDoNotMatch
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/123/
> Upgrade Mockito from 2 to 3.11.2
>
>
> Key: OOZIE-3675
> URL: https://issues.apache.org/jira/browse/OOZIE-3675
> Project: Oozie
> Issue Type: Task
>Affects Versions: 5.2.1
>Reporter: Janos Makai
>Assignee: Janos Makai
>Priority: Major
> Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch,
> OOZIE-3675-003.patch,
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[ https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17636576#comment-17636576 ] Hadoop QA commented on OOZIE-3675: -- PreCommit-OOZIE-Build started > Upgrade Mockito from 2 to 3.11.2 > > > Key: OOZIE-3675 > URL: https://issues.apache.org/jira/browse/OOZIE-3675 > Project: Oozie > Issue Type: Task >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch, > OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch, > OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch, > OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch, > OOZIE-3675-012.patch, OOZIE-3675-013.patch > > > The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[
https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17636367#comment-17636367
]
Hadoop QA commented on OOZIE-3675:
--
Testing JIRA OOZIE-3675
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 6 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 [1] new bugs found below threshold in total that
must be fixed.
.{color:green}+1{color} There are no new bugs found in [core].
.{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
[fluent-job/fluent-job-api].
.{color:green}+1{color} There are no new bugs found in [server].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{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/spark].
.{color:red}-1{color} There are [1] new bugs found below threshold in
[sharelib/oozie] that must be fixed.
.You can find the SpotBugs diff here (look for the red and orange ones):
sharelib/oozie/findbugs-new.html
.The most important SpotBugs errors are:
.At ShellMain.java:[line 93]: This usage of
java/lang/ProcessBuilder.init(Ljava/util/List;)V can be vulnerable to
Command Injection
.At ShellMain.java:[line 91]: At ShellMain.java:[line 90]
.At ShellMain.java:[line 92]
.{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/streaming].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{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/hive].
.{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/git].
{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:red}-1 TESTS{color}
.Tests run: 3188
.Tests failed : 1
.Tests in error : 1238
.Tests timed out : 1
{color:red}-1{color} [ERROR] There are [1] test failures in [client]. Listing
only the first [5] ones
testValidatePrintWorkflowActionOutput:org.apache.oozie.cli.TestOozieCLIMethods
{color:red}-1{color} [ERROR] There are [1238] test errors in [core]. Listing
only the first [5] ones
testJobs:org.apache.oozie.servlet.TestJobsServlet
testDiffUser:org.apache.oozie.servlet.TestJobsServlet
testSubmit:org.apache.oozie.servlet.TestJobsServlet
Check console output for the full list of errors/failures
.{color:orange}Tests failed at first run:{color}
TestOozieCLIMethods#testValidatePrintCoordJobMethodOutput
TestOozieCLIMethods#testValidationPrintBundleJobOutput
TestLauncherMain#testLog4jPropertiesPresentAndReadable
TestDateUtils#testOozieInOtherTZ
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/122/
> Upgrade Mockito from 2 to 3.11.2
>
>
> Key: OOZIE-3675
> URL: https://issues.apache.org/jira/browse/OOZIE-3675
> Project: Oozie
> Issue Type:
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[ https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17636346#comment-17636346 ] Hadoop QA commented on OOZIE-3675: -- PreCommit-OOZIE-Build started > Upgrade Mockito from 2 to 3.11.2 > > > Key: OOZIE-3675 > URL: https://issues.apache.org/jira/browse/OOZIE-3675 > Project: Oozie > Issue Type: Task >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch, > OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch, > OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch, > OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch, > OOZIE-3675-012.patch > > > The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[
https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17636341#comment-17636341
]
Hadoop QA commented on OOZIE-3675:
--
Testing JIRA OOZIE-3675
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 6 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:orange}0{color} There are [4] new bugs found in total that would be nice
to have fixed.
.{color:green}+1{color} There are no new bugs found in [core].
.{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
[fluent-job/fluent-job-api].
.{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:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{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/spark].
.{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/hcatalog].
.{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/hive2].
.{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/hive].
.{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/git].
{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:red}-1 TESTS{color}
.Tests run: 3226
.Tests failed : 3
.Tests in error : 1
.Tests timed out : 0
{color:red}-1{color} [ERROR] There are [1] test failures in [core]. Listing
only the first [5] ones
testNotify:org.apache.oozie.action.hadoop.TestLauncherAMCallbackNotifier
{color:red}-1{color} [ERROR] There are [2] test failures in [sharelib]. Listing
only the first [5] ones
testLocalClientArgsParsing:org.apache.oozie.action.hadoop.TestSparkArgsExtractor
testYarnClientExecutorAndDriverExtraClasspathsArgsParsing:org.apache.oozie.action.hadoop.TestSparkArgsExtractor
{color:red}-1{color} [ERROR] There are [1] test errors in [sharelib]. Listing
only the first [5] ones
testPropertiesFileMerging:org.apache.oozie.action.hadoop.TestSparkArgsExtractor
Check console output for the full list of errors/failures
.{color:orange}Tests failed at first run:{color}
TestOozieCLIMethods#testValidatePrintCoordJobMethodOutput
TestOozieCLIMethods#testValidatePrintCoordJobsOutput
TestOozieCLIMethods#testValidatePrintJobsOutput
TestOozieCLIMethods#testValidationPrintBulkJobsOutput
TestLauncherMain#testLog4jPropertiesPresentAndReadable
TestLauncherAMCallbackNotifier#testNotifyBackgroundActionWhenSubmitSucceeds
TestZKUUIDService#testFallback
TestDateUtils#testOozieInOtherTZ
TestSparkArgsExtractor#testHashMarkInArchivesPath
TestSparkArgsExtractor#testQuotedPlainDriverJavaOptions
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/121/
> Upgrade Mockito from 2 to
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[ https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17636323#comment-17636323 ] Hadoop QA commented on OOZIE-3675: -- PreCommit-OOZIE-Build started > Upgrade Mockito from 2 to 3.11.2 > > > Key: OOZIE-3675 > URL: https://issues.apache.org/jira/browse/OOZIE-3675 > Project: Oozie > Issue Type: Task >Affects Versions: 5.2.1 >Reporter: Janos Makai >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3675-001.patch, OOZIE-3675-002.patch, > OOZIE-3675-003.patch, OOZIE-3675-004.patch, OOZIE-3675-005.patch, > OOZIE-3675-006.patch, OOZIE-3675-007.patch, OOZIE-3675-008.patch, > OOZIE-3675-009.patch, OOZIE-3675-010.patch, OOZIE-3675-011.patch > > > The goal of this Jira is to upgrade Mockito version to 3.11.2 in Oozie. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3675) Upgrade Mockito from 2 to 3.11.2
[
https://issues.apache.org/jira/browse/OOZIE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17636321#comment-17636321
]
Hadoop QA commented on OOZIE-3675:
--
Testing JIRA OOZIE-3675
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 6 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:orange}0{color} There are [4] new bugs found in total that would be nice
to have fixed.
.{color:green}+1{color} There are no new bugs found in [core].
.{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
[fluent-job/fluent-job-api].
.{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:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{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/spark].
.{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/hcatalog].
.{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/hive2].
.{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/hive].
.{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/git].
{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:red}-1 TESTS{color}
.Tests run: 3226
.Tests failed : 1
.Tests in error : 898
.Tests timed out : 1
{color:red}-1{color} [ERROR] There are [1] test failures in [core]. Listing
only the first [5] ones
{color:red}-1{color} [ERROR] There are [898] test errors in [core]. Listing
only the first [5] ones
testJobs:org.apache.oozie.servlet.TestJobsServlet
testDiffUser:org.apache.oozie.servlet.TestJobsServlet
testSubmit:org.apache.oozie.servlet.TestJobsServlet
Check console output for the full list of errors/failures
.{color:orange}Tests failed at first run:{color}
TestHdfsOperations#testActionDataUploadToHdfsFailsWhenAppendingToWriter
TestHdfsOperations#testActionDataUploadToHdfsFailsWhenWriterIsNull
TestLauncherAM#testActionThrowsSecurityExceptionWithExitCode0AndDoesNotPrintStackTrace
TestLauncherAM#testActionThrowsSecurityExceptionWithExitCode1AndPrintsStackTrace
TestLauncherAM#testActionThrowsSecurityExceptionWithoutSystemExit
TestLauncherAM#testActionThrowsThrowableAndAsyncErrorReceived
TestLauncherAM#testMainIsSuccessfullyInvokedAndAsyncErrorReceived
TestLauncherAM#testMainIsSuccessfullyInvokedWithActionData
TestLauncherAM#testMainIsSuccessfullyInvokedWithoutActionData
TestLauncherAM#testRecoveryIdExistsAndRecoveryIdsDoNotMatch
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/120/
> Upgrade Mockito from 2 to 3.11.2
>
>
> Key: OOZIE-3675
> URL:
