I have intermittent failures caused by
"PIRK-35 Execute Tests in Parallel"
such as
<snip/>
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Error occurred during initialization of VM
java.lang.OutOfMemoryError: unable to create new native thread
Error occurred during initialization of VM
java.lang.OutOfMemoryError: unable to create new native thread
Running org.apache.pirk.schema.data.LoadDataSchemaTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.434
sec - in org.apache.pirk.schema.data.LoadDataSchemaTest
Running org.apache.pirk.schema.query.LoadQuerySchemaTest
<snip/>
and
<snip/>
Error occurred during initialization of VM
Cannot create VM thread. Out of system resources.
Error occurred during initialization of VM
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:714)
at java.lang.ref.Finalizer.<clinit>(Finalizer.java:226)
Running org.apache.pirk.schema.data.LoadDataSchemaTest
<snip/>
My laptop is an 8-way machine with 24GB RAM, without ulimits.
I've been running with Oracle Java 8 b102, which defaults to
-XX:InitialHeapSize=387619456 -XX:MaxHeapSize=6201911296, and IBM Java 8
SR3fp10.
Spinning up all tests simultaneously, especially with the
new KafkaStorm tests is too much.
I'm working around it by deleting the PIRK-35 changes, and I get a full
test run in 2mins.
Do other see similar problems? An objection to me reverting PIRK-35 now
that the tests are running faster anyway?
Regards,
Tim
