[ 
https://issues.apache.org/jira/browse/BEAM-5467?focusedWorklogId=162349&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-162349
 ]

ASF GitHub Bot logged work on BEAM-5467:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 04/Nov/18 20:09
            Start Date: 04/Nov/18 20:09
    Worklog Time Spent: 10m 
      Work Description: tweise commented on issue #6937: [BEAM-5467] Log job 
server termination.
URL: https://github.com/apache/beam/pull/6937#issuecomment-435701467
 
 
   @robertwb since I was suspecting that the segmentation faults may have 
something to do with how we run the job server, I added the logging. I was able 
to reproduce the segmentation fault with this change (you usually get it in one 
of five runs):
   ```
   [flink-runner-job-server] INFO org.apache.beam.runners.flink.FlinkRunner - 
Execution finished in 9755 msecs
   .INFO:root:Job server terminated.
   
   ----------------------------------------------------------------------
   Ran 26 tests in 220.072s
   
   OK (skipped=7)
   Segmentation fault (core dumped)
   
   > Task :beam-sdks-python:flinkCompatibilityMatrixBatchDOCKER FAILED
   :beam-sdks-python:flinkCompatibilityMatrixBatchDOCKER (Thread[Task worker 
for ':' Thread 3,5,main]) completed. Took 3 mins 47.265 secs.
   :beam-sdks-python:flinkCompatibilityMatrixStreamingDOCKER (Thread[Task 
worker for ':' Thread 3,5,main]) started.
   ```
   https://builds.apache.org/job/beam_PostCommit_Python_VR_Flink_PR/71/
   
   This excludes the job server as suspect. It rather points to the Python 
process crashing, after all unit tests run. Please take a look. Is it possible 
that in the Jenkins environment we are loading additional/different 
dependencies that cause this?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 162349)
    Time Spent: 15h 20m  (was: 15h 10m)

> Python Flink ValidatesRunner job issues
> ---------------------------------------
>
>                 Key: BEAM-5467
>                 URL: https://issues.apache.org/jira/browse/BEAM-5467
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-flink
>            Reporter: Thomas Weise
>            Priority: Minor
>              Labels: portability-flink
>          Time Spent: 15h 20m
>  Remaining Estimate: 0h
>
>  
> The job is currently flaky and does not provide a useful signal. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to