Adalennis opened a new issue, #9355:
URL: https://github.com/apache/hop/issues/9355
### Apache Hop version?
2.20.0
### Java version?
Java 21
### Operating system
macOS
### What happened?
Reproduced on 2.20.0; the code involved is unchanged on main.
`hop run` ends with exit code `0` when the pipeline has errors or the
workflow ends with a false result. `hop-run.sh` ends with `1` for the same
file. A scheduler, CI job or script that calls `hop run` therefore sees a
failed run as successful. The Getting started page "The Hop toolbox" presents
`hop run` as "what a scheduler, a CI job or a container calls", and the
"Possible exit codes" table on the Hop Run page says `1` means "There was an
error executing the workflow or pipeline".
Steps, with the samples project:
```
./hop run -j samples -r local -f
'${PROJECT_HOME}/transforms/abort-basic.hpl'; echo $?
./hop-run.sh -j samples -r local -f
'${PROJECT_HOME}/transforms/abort-basic.hpl'; echo $?
```
Both runs log the same errors:
```
Abort.0 - ERROR: Aborting after having seen 1 rows.
Abort.0 - Finished processing (I=0, O=0, R=1, W=1, U=0, E=1)
abort-basic - Pipeline detected one or more transforms with errors.
```
`hop run` prints `0` and `hop-run.sh` prints `1`. Only the `hop-run.sh` run
prints `HopRun exit.`. A workflow with Start → Abort gives the same result:
`hop run` ends with `0` and `hop-run.sh` with `1`.
### Issue Priority
Priority: 3
### Issue Component
Component: Hop Gui, Component: Hop Run
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]