[jira] [Commented] (OOZIE-1705) Enable gc logs and print thread id in logs
[
https://issues.apache.org/jira/browse/OOZIE-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057435#comment-15057435
]
Hadoop QA commented on OOZIE-1705:
--
Testing JIRA OOZIE-1705
Cleaning local git workspace
{color:red}-1{color} Patch failed to apply to head of branch
> Enable gc logs and print thread id in logs
> --
>
> Key: OOZIE-1705
> URL: https://issues.apache.org/jira/browse/OOZIE-1705
> Project: Oozie
> Issue Type: Task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-1705-v2.patch, OOZIE-1705.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-1705) Enable gc logs and print thread id in logs
[
https://issues.apache.org/jira/browse/OOZIE-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589598#comment-14589598
]
Jaydeep Vishwakarma commented on OOZIE-1705:
As mentioned by [~rkanter], current setting of gc logs in CATALINA_OPS have
error, You are trying to access oozie.log.dir before its initialization.
oozie-env.sh is getting called at the beginning of oozied.sh.
You can access oozie log directory in {{setup_catalina_ops()}} method of
oozied.sh. I have tried {code} catalina_opts="${catalina_opts} -verbose:gc
-XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xloggc:${OOZIE_LOG}/gc.log" {code}
in same place it is working for me.
> Enable gc logs and print thread id in logs
> --
>
> Key: OOZIE-1705
> URL: https://issues.apache.org/jira/browse/OOZIE-1705
> Project: Oozie
> Issue Type: Task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-1705-v2.patch, OOZIE-1705.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-1705) Enable gc logs and print thread id in logs
[
https://issues.apache.org/jira/browse/OOZIE-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119297#comment-14119297
]
Hadoop QA commented on OOZIE-1705:
--
Testing JIRA OOZIE-1705
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: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} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1511
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/1845/
> Enable gc logs and print thread id in logs
> --
>
> Key: OOZIE-1705
> URL: https://issues.apache.org/jira/browse/OOZIE-1705
> Project: Oozie
> Issue Type: Task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-1705-v2.patch, OOZIE-1705.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-1705) Enable gc logs and print thread id in logs
[
https://issues.apache.org/jira/browse/OOZIE-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14116078#comment-14116078
]
Robert Kanter commented on OOZIE-1705:
--
{quote}When you have code that logs directly, yes line number and class name
are useful. But for oozie, all logging is done using XLog and the class name
and line numbers in oozie.log always point to XLog code. (Its bad, we should
fix it){quote}
I double-checked and you're right about the line numbers; those are always
wrong. The class name is correct though and I think we should keep that.
I tried running it but didn't see a gc.log anywhere. Are you sure that the
arguments are correct?
Also, when running any of the tools (oozie-setup.sh commands, ooziedb.sh, etc)
I get this error (though the script continues running and works anyway):
{noformat}
$ ooziedb.sh create -run
/Users/rkanter/dev/oozie/conf/oozie-env.sh: line 25: $CATALINA_OPTS -Xmx1024m
-verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps
-Xloggc:${oozie.log.dir}/gc.log: bad substitution
setting CATALINA_OPTS="$CATALINA_OPTS -Xmx1024m -verbose:gc
-XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xloggc:${oozie.log.dir}/gc.log"
Validate DB Connection
...
{noformat}
> Enable gc logs and print thread id in logs
> --
>
> Key: OOZIE-1705
> URL: https://issues.apache.org/jira/browse/OOZIE-1705
> Project: Oozie
> Issue Type: Task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-1705-v2.patch, OOZIE-1705.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (OOZIE-1705) Enable gc logs and print thread id in logs
[
https://issues.apache.org/jira/browse/OOZIE-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14110150#comment-14110150
]
Hadoop QA commented on OOZIE-1705:
--
Testing JIRA OOZIE-1705
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: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} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1508
.Tests failed: 1
.Tests errors: 0
.The patch failed the following testcases:
.
testConcurrencyReachedAndChooseNextEligible(org.apache.oozie.service.TestCallableQueueService)
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/1681/
> Enable gc logs and print thread id in logs
> --
>
> Key: OOZIE-1705
> URL: https://issues.apache.org/jira/browse/OOZIE-1705
> Project: Oozie
> Issue Type: Task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-1705-v2.patch, OOZIE-1705.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (OOZIE-1705) Enable gc logs and print thread id in logs
[
https://issues.apache.org/jira/browse/OOZIE-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107791#comment-14107791
]
Hadoop QA commented on OOZIE-1705:
--
Testing JIRA OOZIE-1705
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: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} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1508
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/1671/
> Enable gc logs and print thread id in logs
> --
>
> Key: OOZIE-1705
> URL: https://issues.apache.org/jira/browse/OOZIE-1705
> Project: Oozie
> Issue Type: Task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-1705-v2.patch, OOZIE-1705.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (OOZIE-1705) Enable gc logs and print thread id in logs
[
https://issues.apache.org/jira/browse/OOZIE-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107672#comment-14107672
]
Hadoop QA commented on OOZIE-1705:
--
Testing JIRA OOZIE-1705
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: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} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1508
.Tests failed: 2
.Tests errors: 0
.The patch failed the following testcases:
.
testMemoryUsageAndSpeed(org.apache.oozie.service.TestPartitionDependencyManagerService)
.
testNone(org.apache.oozie.command.coord.TestCoordActionInputCheckXCommand)
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/1650/
> Enable gc logs and print thread id in logs
> --
>
> Key: OOZIE-1705
> URL: https://issues.apache.org/jira/browse/OOZIE-1705
> Project: Oozie
> Issue Type: Task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-1705-v2.patch, OOZIE-1705.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (OOZIE-1705) Enable gc logs and print thread id in logs
[
https://issues.apache.org/jira/browse/OOZIE-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106470#comment-14106470
]
Hadoop QA commented on OOZIE-1705:
--
Testing JIRA OOZIE-1705
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: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} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1508
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/1575/
> Enable gc logs and print thread id in logs
> --
>
> Key: OOZIE-1705
> URL: https://issues.apache.org/jira/browse/OOZIE-1705
> Project: Oozie
> Issue Type: Task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-1705-v2.patch, OOZIE-1705.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (OOZIE-1705) Enable gc logs and print thread id in logs
[
https://issues.apache.org/jira/browse/OOZIE-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103513#comment-14103513
]
Hadoop QA commented on OOZIE-1705:
--
Testing JIRA OOZIE-1705
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: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} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1508
.Tests failed: 2
.Tests errors: 0
.The patch failed the following testcases:
.
testActionKillCommandDate(org.apache.oozie.command.coord.TestCoordActionsKillXCommand)
.
testConcurrencyReachedAndChooseNextEligible(org.apache.oozie.service.TestCallableQueueService)
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/1560/
> Enable gc logs and print thread id in logs
> --
>
> Key: OOZIE-1705
> URL: https://issues.apache.org/jira/browse/OOZIE-1705
> Project: Oozie
> Issue Type: Task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-1705-v2.patch, OOZIE-1705.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (OOZIE-1705) Enable gc logs and print thread id in logs
[
https://issues.apache.org/jira/browse/OOZIE-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101927#comment-14101927
]
Shwetha G S commented on OOZIE-1705:
{quote}
Will adding the gc log cause a lot of overhead or anything like that?
{quote}
In almost all java applications, gc logging is turned on by default. The
overhead is very small
{quote}
Looks like it's going to default to ${OOZIE_HOME}/logs/gc.log. Is it possible
to put it under ${oozie.log.dir} so it will always be next to the other logs?
Not everyone has the logs dir under ${OOZIE_HOME}.
{quote}
Will do
{quote}
For the log4j pattern change, won't most threads be from the thread pool and
not have a useful name? Perhaps we should add names for each thread we create
in the code?
{quote}
they will have thread id like thread-
{quote}
For the log4j pattern change, I don't think we should remove the %c{1}:%L; this
is really useful because it tells us which class and line number it came from.
{quote}
When you have code that logs directly, yes line number and class name are
useful. But for oozie, all logging is done using XLog and the class name and
line numbers in oozie.log always point to XLog code. (Its bad, we should fix it)
> Enable gc logs and print thread id in logs
> --
>
> Key: OOZIE-1705
> URL: https://issues.apache.org/jira/browse/OOZIE-1705
> Project: Oozie
> Issue Type: Task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-1705.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (OOZIE-1705) Enable gc logs and print thread id in logs
[
https://issues.apache.org/jira/browse/OOZIE-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101265#comment-14101265
]
Robert Kanter commented on OOZIE-1705:
--
A couple of things:
# Will adding the gc log cause a lot of overhead or anything like that?
# Looks like it's going to default to {{$\{OOZIE_HOME}/logs/gc.log}}. Is it
possible to put it under {{$\{oozie.log.dir}}} so it will always be next to the
other logs? Not everyone has the {{logs}} dir under {{$\{OOZIE_HOME}}}.
# For the log4j pattern change, won't most threads be from the thread pool and
not have a useful name? Perhaps we should add names for each thread we create
in the code?
# For the log4j pattern change, I don't think we should remove the
{{%c\{1}:%L}}; this is really useful because it tells us which class and line
number it came from.
> Enable gc logs and print thread id in logs
> --
>
> Key: OOZIE-1705
> URL: https://issues.apache.org/jira/browse/OOZIE-1705
> Project: Oozie
> Issue Type: Task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-1705.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (OOZIE-1705) Enable gc logs and print thread id in logs
[
https://issues.apache.org/jira/browse/OOZIE-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084042#comment-14084042
]
Hadoop QA commented on OOZIE-1705:
--
Testing JIRA OOZIE-1705
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: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} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1505
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/1452/
> Enable gc logs and print thread id in logs
> --
>
> Key: OOZIE-1705
> URL: https://issues.apache.org/jira/browse/OOZIE-1705
> Project: Oozie
> Issue Type: Task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-1705.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (OOZIE-1705) Enable gc logs and print thread id in logs
[
https://issues.apache.org/jira/browse/OOZIE-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008084#comment-14008084
]
Hadoop QA commented on OOZIE-1705:
--
Testing JIRA OOZIE-1705
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: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} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1448
.Tests failed: 4
.Tests errors: 3
.The patch failed the following testcases:
.
testCoordinatorActionCommandsSubmitAndStart(org.apache.oozie.sla.TestSLAEventGeneration)
.
testBundleEngineSuspend(org.apache.oozie.servlet.TestV1JobServletBundleEngine)
.
testBundleEngineReRun(org.apache.oozie.servlet.TestV1JobServletBundleEngine)
.
testTimeoutWithException(org.apache.oozie.command.coord.TestCoordActionInputCheckXCommand)
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/1262/
> Enable gc logs and print thread id in logs
> --
>
> Key: OOZIE-1705
> URL: https://issues.apache.org/jira/browse/OOZIE-1705
> Project: Oozie
> Issue Type: Task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-1705.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
