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

Hadoop QA commented on OOZIE-3373:
----------------------------------


Testing JIRA OOZIE-3373

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:orange}WARNING{color}: the current HEAD has 100 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 [docs].
. {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 [core].
. {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 
[fluent-job/fluent-job-api].
. {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/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/git].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/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/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {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: 3062
.    {color:orange}Tests failed at first run:{color}
TestStatusTransitService#testCoordStatusTransitServiceSuspendAndResume
.    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:red}*-1 Overall result, please check the reported -1(s)*{color}

{color:red}. There is at least one warning, please check{color}

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

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



> Logging of lock information inconsistent
> ----------------------------------------
>
>                 Key: OOZIE-3373
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3373
>             Project: Oozie
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 4.3.0
>            Reporter: Prabhu Joseph
>            Assignee: Prabhu Joseph
>            Priority: Minor
>         Attachments: OOZIE-3373-1.patch
>
>
> The lock resource name getEntityKey() is printed when lock is acquired 
> whereas getName() + "_" + actionId is printed when Could not get lock. This 
> makes difficult to correlate the logs.
> {code}
> LOG.debug("Acquired lock for [{0}] in [{1}]", getEntityKey(), getName());
> LOG.debug("Could not get lock [{0}], timed out [{1}]ms, and requeue itself 
> [{2}]", this.toString(),
> getLockTimeOut(), getName());
> {code}
> Example:
> {code}
> 2018-10-10 12:00:05,698 pool-6-thread-5 DEBUG ActionCheckXCommand:526 - 
> SERVER[dn3-george] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[-] 
> ACTION[0000134-181002155022081-oozie-oozi-W@shell1] Could not get lock 
> [action.check_0000134-181002155022081-oozie-oozi-W@shell1], timed out 
> [5,000]ms, and requeue itself [action.check]
> {code}
> The actual lock it waits is for 0000134-181002155022081-oozie-oozi-W which is 
> not printed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to