Github user f-sander commented on the pull request:

    https://github.com/apache/flink/pull/1565#issuecomment-178487703
  
    Are the build failures related to us? I don't really understand how...
    
    The first failure happens in oraclejd8 with hadoop 2.7.1:
    ```
    Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 351.368 sec 
<<< FAILURE! - in 
org.apache.flink.test.recovery.TaskManagerProcessFailureBatchRecoveryITCase
    
testTaskManagerProcessFailure[0](org.apache.flink.test.recovery.TaskManagerProcessFailureBatchRecoveryITCase)
  Time elapsed: 318.792 sec  <<< FAILURE!
    java.lang.AssertionError: The program did not finish in time
        at org.junit.Assert.fail(Assert.java:88)
        at org.junit.Assert.assertTrue(Assert.java:41)
        at org.junit.Assert.assertFalse(Assert.java:64)
        at 
org.apache.flink.test.recovery.AbstractTaskManagerProcessFailureRecoveryTest.testTaskManagerProcessFailure(AbstractTaskManagerProcessFailureRecoveryTest.java:212)
    ```
    The second on in openjdk 7 with hadoop 1 appears to experience a deadlock 
(?):
    ```
    
==============================================================================
    Maven produced no output for 300 seconds.
    
==============================================================================
    
==============================================================================
    The following Java processes are running (JPS)
    
==============================================================================
    2286 Launcher
    77113 Jps
    76276 surefirebooter4006285424712115006.jar
    
==============================================================================
    Printing stack trace of Java process 2286
    
==============================================================================
    ```
    After that only lots of lots of process stack traces.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to