[
https://issues.apache.org/jira/browse/FLINK-34465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Pohl closed FLINK-34465.
---------------------------------
Resolution: Duplicate
Thanks for creating this issue, [~lincoln] . For the python stage, it's a bit
tedious to find the actual issue because the actual hints are located further
up in the log output. The description you're giving in this ticket is quite
general. That makes it harder to pinpoint the actual cause.
Just as a hint for Python test instabilities: You can search in the logs for
the term "FAILURES". Usually, this term only appears once at the start of the
actual failure log (e.g. [here for the build
above|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=57580&view=logs&j=3e4dd1a2-fe2f-5e5d-a581-48087e718d53&t=b4612f28-e3b5-5853-8a8b-610ae894217a&l=24260]).
Anything below that line shows the actual failure and reveals that it's
actually FLINK-26644 rather than a new failure. I hope this helps. :)
I'm going to close this one in favor of FLINK-26644
> Python py38-cython: commands failed, Bash exited with code '1
> -------------------------------------------------------------
>
> Key: FLINK-34465
> URL: https://issues.apache.org/jira/browse/FLINK-34465
> Project: Flink
> Issue Type: Bug
> Components: API / Python
> Reporter: Lincoln Lee
> Priority: Major
> Labels: test-stability
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=57580&view=logs&j=3e4dd1a2-fe2f-5e5d-a581-48087e718d53&t=b4612f28-e3b5-5853-8a8b-610ae894217a&l=28104
> {noformat}
> Feb 18 03:18:05 ERROR: py38-cython: commands failed
> Feb 18 03:18:05 py39-cython: commands succeeded
> Feb 18 03:18:05 py310-cython: commands succeeded
> Feb 18 03:18:05 py311-cython: commands succeeded
> Feb 18 03:18:05 cleanup
> /__w/2/s/flink-python/.tox/.tmp/package/1/apache-flink-1.20.dev0.zip
> Feb 18 03:18:06 ============tox checks... [FAILED]============
> Feb 18 03:18:06 Process exited with EXIT CODE: 1.
> Feb 18 03:18:06 Trying to KILL watchdog (18662).
> /__w/2/s/tools/ci/watchdog.sh: line 100: 18662 Terminated
> watchdog
> Feb 18 03:18:06 Searching for .dump, .dumpstream and related files in
> '/__w/2/s'
> The STDIO streams did not close within 10 seconds of the exit event from
> process '/bin/bash'. This may indicate a child process inherited the STDIO
> streams and has not yet exited.
> ##[error]Bash exited with code '1'.
> Finishing: Test - python
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
