From 58d2279e8f3d13787927a462e162cf30c81e3ef9 Mon Sep 17 00:00:00 2001 From: Seth Tisue Date: Fri, 26 Aug 2016 19:07:34 -0700 Subject: increase stack size when running JUnit tests scala.collection.immutable.PagedSeqTest.test_SI6615 was failing intermittently during PR validation I verified that this change fixes the problem by: - changing the PageSize constant in PagedSeq (as shown by Jason Zaugg) until the test failed every time locally - making this build change and seeing the test pass again 5M is just an arbitrary number, considerably over the default (which varies according to platform & CPU). 5M is a lot of stack, but not so vastly much that it appreciably eats into the heap --- build.sbt | 1 + 1 file changed, 1 insertion(+) (limited to 'build.sbt') diff --git a/build.sbt b/build.sbt index 3ceff35b45..76ffe52728 100644 --- a/build.sbt +++ b/build.sbt @@ -556,6 +556,7 @@ lazy val junit = project.in(file("test") / "junit") .settings(disablePublishing: _*) .settings( fork in Test := true, + javaOptions in Test += "-Xss5M", libraryDependencies ++= Seq(junitDep, junitInterfaceDep, jolDep), testOptions += Tests.Argument(TestFrameworks.JUnit, "-a", "-v"), testFrameworks -= new TestFramework("org.scalacheck.ScalaCheckFramework"), -- cgit v1.2.3