flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Ewen (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FLINK-1561) Improve build server robustness by not reusing JVMs in integration tests
Date Tue, 17 Feb 2015 10:09:11 GMT
Stephan Ewen created FLINK-1561:

             Summary: Improve build server robustness by not reusing JVMs in integration tests
                 Key: FLINK-1561
                 URL: https://issues.apache.org/jira/browse/FLINK-1561
             Project: Flink
          Issue Type: Improvement
          Components: Build System
    Affects Versions: 0.9
            Reporter: Stephan Ewen
            Assignee: Stephan Ewen
             Fix For: 0.9

Right now, JVM forks are reused across unit and integration tests. While it makes a lot of
sense for the very quick unit tests, the integration tests benefit less.

We also see spurious JVM failures in the integration tests that are most likely related to
JVM issues. An example is the trace below:
java.io.IOException: Cannot allocate memory
	at sun.nio.ch.FileDispatcherImpl.write0(Native Method)
	at sun.nio.ch.FileDispatcherImpl.write(FileDispatcherImpl.java:60)
	at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)
	at sun.nio.ch.IOUtil.write(IOUtil.java:65)
	at sun.nio.ch.FileChannelImpl.write(FileChannelImpl.java:205)
	at org.apache.flink.runtime.io.disk.iomanager.SegmentWriteRequest.write(AsynchronousFileIOChannel.java:270)
	at org.apache.flink.runtime.io.disk.iomanager.IOManagerAsync$WriterThread.run(IOManagerAsync.java:440)

I think we can improve reliability of Travis tests by not reusing forks for integration tests.

This message was sent by Atlassian JIRA

View raw message