[jira] [Commented] (OOZIE-3596) When the SSH action is killed, it must be changed to the kill command that can terminate the related subprocess.
[
https://issues.apache.org/jira/browse/OOZIE-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238690#comment-17238690
]
Hadoop QA commented on OOZIE-3596:
--
Testing JIRA OOZIE-3596
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: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 [6] new bugs found below threshold in total that
must be fixed.
.{color:green}+1{color} There are no new bugs found in [tools].
.{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: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: 3215
.{color:orange}Tests failed at first run:{color}
TestCoordActionsKillXCommand#testActionKillCommandDate
TestBlockingInputStream#testFastWritingBlockingInputStream
TestPriorityDelayQueue#testPeek
.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/8/
> When the SSH action is killed, it must be changed to the kill command that
> can terminate the related subprocess.
>
>
> Key: OOZIE-3596
> URL: https://issues.apache.org/jira/browse/OOZIE-3596
> Project: Oozie
> Issue Type: Improvement
> Components: core
>Reporter: Suekyoung L
[jira] [Commented] (OOZIE-3596) When the SSH action is killed, it must be changed to the kill command that can terminate the related subprocess.
[ https://issues.apache.org/jira/browse/OOZIE-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238635#comment-17238635 ] Hadoop QA commented on OOZIE-3596: -- PreCommit-OOZIE-Build started > When the SSH action is killed, it must be changed to the kill command that > can terminate the related subprocess. > > > Key: OOZIE-3596 > URL: https://issues.apache.org/jira/browse/OOZIE-3596 > Project: Oozie > Issue Type: Improvement > Components: core >Reporter: Suekyoung Lee >Priority: Major > Attachments: OOZIE-3596-001.patch, OOZIE-3596-002.patch, > OOZIE-3596-003.patch > > > When the SSH action is terminated via the kill API, only the ssh-wrapper.sh > file (created for ssh execution in oozie) is terminated, and the > child-processes that has occurred is still running. > For example, if the shell file for running spark-shell (e.g. called > "run-spark.sh") runs and exits as an SSH action, only the ssh-wrapper.sh file > exits and the child-processes (run-spark.sh and spark-shell) are still > running. > Therefore, when the SSH action is killed, it must be changed to the kill > command that can terminate the related subprocess. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3596) When the SSH action is killed, it must be changed to the kill command that can terminate the related subprocess.
[ https://issues.apache.org/jira/browse/OOZIE-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238629#comment-17238629 ] Andras Salamon commented on OOZIE-3596: --- This looks rather similar to OOZIE-3362. > When the SSH action is killed, it must be changed to the kill command that > can terminate the related subprocess. > > > Key: OOZIE-3596 > URL: https://issues.apache.org/jira/browse/OOZIE-3596 > Project: Oozie > Issue Type: Improvement > Components: core >Reporter: Suekyoung Lee >Priority: Major > Attachments: OOZIE-3596-001.patch, OOZIE-3596-002.patch, > OOZIE-3596-003.patch > > > When the SSH action is terminated via the kill API, only the ssh-wrapper.sh > file (created for ssh execution in oozie) is terminated, and the > child-processes that has occurred is still running. > For example, if the shell file for running spark-shell (e.g. called > "run-spark.sh") runs and exits as an SSH action, only the ssh-wrapper.sh file > exits and the child-processes (run-spark.sh and spark-shell) are still > running. > Therefore, when the SSH action is killed, it must be changed to the kill > command that can terminate the related subprocess. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3596) When the SSH action is killed, it must be changed to the kill command that can terminate the related subprocess.
[ https://issues.apache.org/jira/browse/OOZIE-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074163#comment-17074163 ] Suekyoung Lee commented on OOZIE-3596: -- [~zuston] Do you mean that this is an already resolved issue? > When the SSH action is killed, it must be changed to the kill command that > can terminate the related subprocess. > > > Key: OOZIE-3596 > URL: https://issues.apache.org/jira/browse/OOZIE-3596 > Project: Oozie > Issue Type: Improvement > Components: core >Reporter: Suekyoung Lee >Priority: Major > Attachments: OOZIE-3596-001.patch, OOZIE-3596-002.patch, > OOZIE-3596-003.patch > > > When the SSH action is terminated via the kill API, only the ssh-wrapper.sh > file (created for ssh execution in oozie) is terminated, and the > child-processes that has occurred is still running. > For example, if the shell file for running spark-shell (e.g. called > "run-spark.sh") runs and exits as an SSH action, only the ssh-wrapper.sh file > exits and the child-processes (run-spark.sh and spark-shell) are still > running. > Therefore, when the SSH action is killed, it must be changed to the kill > command that can terminate the related subprocess. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3596) When the SSH action is killed, it must be changed to the kill command that can terminate the related subprocess.
[ https://issues.apache.org/jira/browse/OOZIE-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073619#comment-17073619 ] Junfan Zhang commented on OOZIE-3596: - Oozie does have this problem and we have made corresponding changes in production env samely. > When the SSH action is killed, it must be changed to the kill command that > can terminate the related subprocess. > > > Key: OOZIE-3596 > URL: https://issues.apache.org/jira/browse/OOZIE-3596 > Project: Oozie > Issue Type: Improvement > Components: core >Reporter: Suekyoung Lee >Priority: Major > Attachments: OOZIE-3596-001.patch, OOZIE-3596-002.patch, > OOZIE-3596-003.patch > > > When the SSH action is terminated via the kill API, only the ssh-wrapper.sh > file (created for ssh execution in oozie) is terminated, and the > child-processes that has occurred is still running. > For example, if the shell file for running spark-shell (e.g. called > "run-spark.sh") runs and exits as an SSH action, only the ssh-wrapper.sh file > exits and the child-processes (run-spark.sh and spark-shell) are still > running. > Therefore, when the SSH action is killed, it must be changed to the kill > command that can terminate the related subprocess. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3596) When the SSH action is killed, it must be changed to the kill command that can terminate the related subprocess.
[
https://issues.apache.org/jira/browse/OOZIE-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073616#comment-17073616
]
Hadoop QA commented on OOZIE-3596:
--
Testing JIRA OOZIE-3596
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: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 [6] new bugs found below threshold in total that
must be fixed.
.{color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
.{color:green}+1{color} There are no new bugs found in [docs].
.{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 [sharelib/spark].
.{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/hive2].
.{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/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/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [server].
.{color:green}+1{color} There are no new bugs found in [client].
.{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 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: 3215
.{color:orange}Tests failed at first run:{color}
TestCallableQueueService#testQueueSizeWhenMaxConcurrencyIsReached
TestBlockingInputStream#testFastWritingBlockingInputStream
TestParamChecker#testCheckUTC
.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://builds.apache.org/job/PreCommit-OOZIE-Build/1320/
> When the SSH action is killed, it must be changed to the kill command that
> can terminate the related subprocess.
>
>
> Key: OOZIE-3596
> URL: https://issues.apache.org/jira/browse/OOZIE-3596
> Project: Oozie
> Issue Type: Improvement
> Components: core
>Reporter: Su
[jira] [Commented] (OOZIE-3596) When the SSH action is killed, it must be changed to the kill command that can terminate the related subprocess.
[ https://issues.apache.org/jira/browse/OOZIE-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073530#comment-17073530 ] Hadoop QA commented on OOZIE-3596: -- PreCommit-OOZIE-Build started > When the SSH action is killed, it must be changed to the kill command that > can terminate the related subprocess. > > > Key: OOZIE-3596 > URL: https://issues.apache.org/jira/browse/OOZIE-3596 > Project: Oozie > Issue Type: Improvement > Components: core >Reporter: Suekyoung Lee >Priority: Major > Attachments: OOZIE-3596-001.patch, OOZIE-3596-002.patch, > OOZIE-3596-003.patch > > > When the SSH action is terminated via the kill API, only the ssh-wrapper.sh > file (created for ssh execution in oozie) is terminated, and the > child-processes that has occurred is still running. > For example, if the shell file for running spark-shell (e.g. called > "run-spark.sh") runs and exits as an SSH action, only the ssh-wrapper.sh file > exits and the child-processes (run-spark.sh and spark-shell) are still > running. > Therefore, when the SSH action is killed, it must be changed to the kill > command that can terminate the related subprocess. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3596) When the SSH action is killed, it must be changed to the kill command that can terminate the related subprocess.
[
https://issues.apache.org/jira/browse/OOZIE-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073452#comment-17073452
]
Hadoop QA commented on OOZIE-3596:
--
Testing JIRA OOZIE-3596
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: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 [6] new bugs found below threshold in total that
must be fixed.
.{color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
.{color:green}+1{color} There are no new bugs found in [docs].
.{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 [sharelib/spark].
.{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/hive2].
.{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/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/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{color:green}+1{color} There are no new bugs found in [tools].
.{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 [client].
.{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 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: 3215
.{color:orange}Tests failed at first run:{color}
TestBlockingInputStream#testLimitedWritingBlockingInputStream
.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://builds.apache.org/job/PreCommit-OOZIE-Build/1319/
> When the SSH action is killed, it must be changed to the kill command that
> can terminate the related subprocess.
>
>
> Key: OOZIE-3596
> URL: https://issues.apache.org/jira/browse/OOZIE-3596
> Project: Oozie
> Issue Type: Improvement
> Components: core
>Rep
[jira] [Commented] (OOZIE-3596) When the SSH action is killed, it must be changed to the kill command that can terminate the related subprocess.
[ https://issues.apache.org/jira/browse/OOZIE-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073387#comment-17073387 ] Hadoop QA commented on OOZIE-3596: -- PreCommit-OOZIE-Build started > When the SSH action is killed, it must be changed to the kill command that > can terminate the related subprocess. > > > Key: OOZIE-3596 > URL: https://issues.apache.org/jira/browse/OOZIE-3596 > Project: Oozie > Issue Type: Improvement > Components: core >Reporter: Suekyoung Lee >Priority: Major > Attachments: OOZIE-3596-001.patch, OOZIE-3596-002.patch > > > When the SSH action is terminated via the kill API, only the ssh-wrapper.sh > file (created for ssh execution in oozie) is terminated, and the > child-processes that has occurred is still running. > For example, if the shell file for running spark-shell (e.g. called > "run-spark.sh") runs and exits as an SSH action, only the ssh-wrapper.sh file > exits and the child-processes (run-spark.sh and spark-shell) are still > running. > Therefore, when the SSH action is killed, it must be changed to the kill > command that can terminate the related subprocess. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3596) When the SSH action is killed, it must be changed to the kill command that can terminate the related subprocess.
[
https://issues.apache.org/jira/browse/OOZIE-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073327#comment-17073327
]
Hadoop QA commented on OOZIE-3596:
--
Testing JIRA OOZIE-3596
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:red}-1{color} the patch contains 1 line(s) with 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 [6] new bugs found below threshold in total that
must be fixed.
.{color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
.{color:green}+1{color} There are no new bugs found in [docs].
.{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 [sharelib/spark].
.{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/hive2].
.{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/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/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [server].
.{color:green}+1{color} There are no new bugs found in [client].
.{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 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: 3215
.{color:orange}Tests failed at first run:{color}
TestBlockingInputStream#testFastWritingBlockingInputStream
TestBlockingInputStream#testLimitedWritingBlockingInputStream
.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://builds.apache.org/job/PreCommit-OOZIE-Build/1318/
> When the SSH action is killed, it must be changed to the kill command that
> can terminate the related subprocess.
>
>
> Key: OOZIE-3596
> URL: https://issues.apache.org/jira/browse/OOZIE-3596
> Project: Oozie
> Issue Type: Improvement
> Components: core
>Reporter: Suekyoung Lee
>Priority:
[jira] [Commented] (OOZIE-3596) When the SSH action is killed, it must be changed to the kill command that can terminate the related subprocess.
[ https://issues.apache.org/jira/browse/OOZIE-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073280#comment-17073280 ] Hadoop QA commented on OOZIE-3596: -- PreCommit-OOZIE-Build started > When the SSH action is killed, it must be changed to the kill command that > can terminate the related subprocess. > > > Key: OOZIE-3596 > URL: https://issues.apache.org/jira/browse/OOZIE-3596 > Project: Oozie > Issue Type: Improvement > Components: core >Reporter: Suekyoung Lee >Priority: Major > Attachments: OOZIE-3596-001.patch > > > When the SSH action is terminated via the kill API, only the ssh-wrapper.sh > file (created for ssh execution in oozie) is terminated, and the > child-processes that has occurred is still running. > For example, if the shell file for running spark-shell (e.g. called > "run-spark.sh") runs and exits as an SSH action, only the ssh-wrapper.sh file > exits and the child-processes (run-spark.sh and spark-shell) are still > running. > Therefore, when the SSH action is killed, it must be changed to the kill > command that can terminate the related subprocess. -- This message was sent by Atlassian Jira (v8.3.4#803005)
