[infinispan-issues] [JBoss JIRA] (ISPN-4489) TestNG OOME on large number of failures

TestNG OOME on large number of failures --------------------------------------- Key: ISPN-4489 URL: https://issues.jboss.org/browse/ISPN-4489 Project: Infinispan Issue Type: Task Security Level: Public(Everyone can see) Reporter: Ion Savin Assignee: Ion Savin If for some reason several tests fail testng will throw an OOME. {noformat} java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf(Arrays.java:2367) at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:130) at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:114) at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:415) at java.lang.StringBuilder.append(StringBuilder.java:132) at org.testng.reporters.Files.readFile(Files.java:28) at org.testng.reporters.Files.readFile(Files.java:20) at org.testng.reporters.FileStringBuffer.toString(FileStringBuffer.java:137) at org.testng.reporters.XMLStringBuffer.toXML(XMLStringBuffer.java:331) at org.testng.reporters.jq.ChronologicalPanel.getContent(ChronologicalPanel.java:93) at org.testng.reporters.jq.BaseMultiSuitePanel.generate(BaseMultiSuitePanel.java:24) at org.testng.reporters.jq.Main.generateReport(Main.java:63) at org.testng.TestNG.generateReports(TestNG.java:1115) at org.testng.TestNG.run(TestNG.java:1074) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107) at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) {noformat} This particular error is triggered by one of the reports enabled by default by testng which is producing a more user friendly version using jquery. Since we are probably don't need this report look into disabling it.