[
https://issues.apache.org/jira/browse/FLINK-17336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17104453#comment-17104453
]
Robert Metzger edited comment on FLINK-17336 at 5/11/20, 1:28 PM:
------------------------------------------------------------------
I think I understood of build #965 (the previous link):
- The HadoopS3FileSystemITCase doesn't produce any output for more than 10
minutes (probably because of the Ali network)
- the "travis watchdog" detects that there's no output
- the watchdog is supposed to kill the maven process, but it fails to do so.
There is this message
{code}
2020-05-11T10:57:09.3176283Z ./tools/travis_watchdog.sh: line 247: 2434
Terminated $cmd
{code}
It implies that something was killed, but not maven.
- the test continues (after 1549 seconds ~ 25 minutes)
- maven finishes with a "Build Success"
Current theory:
We recently introduced the {{run_mvn}} function. Maybe the bash running that
function gets killed, and reports 143 (that's what a process returns when it
receives a sigterm.).
was (Author: rmetzger):
I think I understood of build #965 (the previous link):
- The HadoopS3FileSystemITCase doesn't produce any output for more than 10
minutes (probably because of the Ali network)
- the "travis watchdog" detects that there's no output
- the watchdog is supposed to kill the maven process, but it fails to do so.
There is this message
{code}
2020-05-11T10:57:09.3176283Z ./tools/travis_watchdog.sh: line 247: 2434
Terminated $cmd
{code}
It implies that something was killed, but not maven.
- the test continues (after 1549 seconds ~ 25 minutes)
- maven finishes with a "Build Success"
Current theory:
We recently introduced the {run_mvn} function. Maybe the bash running that
function gets killed, and reports 143 (that's what a process returns when it
receives a sigterm.).
> MVN exited with EXIT CODE: 143. in "libraries" test job
> -------------------------------------------------------
>
> Key: FLINK-17336
> URL: https://issues.apache.org/jira/browse/FLINK-17336
> Project: Flink
> Issue Type: Bug
> Components: Build System / Azure Pipelines, Tests
> Affects Versions: 1.11.0
> Reporter: Robert Metzger
> Assignee: Robert Metzger
> Priority: Major
>
> CI:https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=89&view=logs&j=56781494-ebb0-5eae-f732-b9c397ec6ede&t=32b25b6b-f46f-5bca-b5eb-2c6936ee77a4
> maven reports "build success", but the exit code is 143?
> {code}
> [INFO] flink-state-processor-api .......................... SUCCESS [ 0.273
> s]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 19:24 min
> [INFO] Finished at: 2020-04-23T00:46:43+00:00
> [INFO] Final Memory: 246M/4214M
> [INFO]
> ------------------------------------------------------------------------
> [WARNING] The requested profile "e2e-hadoop" could not be activated because
> it does not exist.
> MVN exited with EXIT CODE: 143.
> Trying to KILL watchdog (265).
> ==============================================================================
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
