[
https://issues.apache.org/jira/browse/OOZIE-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14090225#comment-14090225
]
Hadoop QA commented on OOZIE-1920:
----------------------------------
Testing JIRA OOZIE-1920
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:green}+1{color} the patch does 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} 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: 1505
. Tests failed: 4
. Tests errors: 1
. The patch failed the following testcases:
.
testConcurrencyReachedAndChooseNextEligible(org.apache.oozie.service.TestCallableQueueService)
.
testPauseBundleAndCoordinator(org.apache.oozie.service.TestPauseTransitService)
.
testUnpauseBundleAndCoordinator(org.apache.oozie.service.TestPauseTransitService)
.
testCoordMaterializeTriggerService3(org.apache.oozie.service.TestCoordMaterializeTriggerService)
{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/1508/
> Capture Output for SSH Action doesn't work
> ------------------------------------------
>
> Key: OOZIE-1920
> URL: https://issues.apache.org/jira/browse/OOZIE-1920
> Project: Oozie
> Issue Type: Bug
> Components: action
> Affects Versions: 4.0.0
> Environment: CDH 5.0.2
> Reporter: Alessandro Costantino
> Assignee: Richard Williams
> Priority: Blocker
> Labels: cloudera, oozie, ssh
> Fix For: 4.1.0
>
> Attachments: OOZIE-1920.patch, OOZIE-1920.patch.2
>
>
> Running a simple workflow that have a shell action with capture-output
> enabled, the SShActionExecutor look at the wrong stdout file. This is the the
> command that I found in the log:
> ssh -o PasswordAuthentication=no -o KbdInteractiveDevices=no -o
> StrictHostKeyChecking=no -o ConnectTimeout=20 workflow@redhat5 cat
> oozie-oozi/0000008-140708170302737-oozie-oozi-W/fileProcessing--ssh/22350.0000008-140708170302737-oozie-oozi-W@fileProcessing@1.stdout
> But the generated stdout file is
> `/home/instadoc/oozie-oozi/0000008-140708170302737-oozie-oozi-W/fileProcessing--ssh/22350.0000008-140708170302737-oozie-oozi-W@fileProcessing@0.stdout`
> If you relaunch the action the ID that prepend the .stdout extension could
> vary (ie: @9.stdout, @4.stdout) but the SShActionExecutor looks always at
> @0.stdout.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
