Project

General

Profile

Bug #3063

CommandLineExec actor does not generate Exit code

Added by Dan Higgins almost 12 years ago. Updated almost 12 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
actors
Target version:
Start date:
01/11/2008
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
3063

Description

Supposedly, the CommandLineExec actor will generate a '1' on the exitCode output when the execution of the command line is successful. Apparently this does NOT happen under Windows; nothing appears on the output if the command does not send anything to SysOut. This makes it impossible to run a command line operation in the middle of workflow and use it to trigger further actors.

See the example $KEPLER/workflows/eco/maxent.xml

Dan Higgins - Jan 2008

History

#1 Updated by Dan Higgins almost 12 years ago

Fixed the code so that it does return a '1' on the exitCode port when there is no error in executing the Command Line.

It turned out that this was not specifically a Windows problem (also occurred under Mac Unix).

#2 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 3063

Also available in: Atom PDF