[
https://issues.apache.org/jira/browse/NIFI-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097288#comment-15097288
]
Thad Guidry edited comment on NIFI-1368 at 1/13/16 11:39 PM:
-------------------------------------------------------------
Spent the entire day running 100+ builds with tests on Windows 7 64bit
Enterprise HP Zbook15 12GB Ram Core i7 (my work laptop).
Generally found that there are some critical tests that do seem to consume mass
amounts of memory with surefire forking options on a Windows system.
I cannot get a build to complete with basic or advanced options such as,
allocating more memory to surefire (up to 4G), allocating more memory to maven
(up to 4G), even tried updating surefire plugin to 2.19.1 and setting pom.xml
setting to use options like forkCount using 2C, 2, 1, 1C.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.19.1</version>
<configuration>
<forkCount>1C</forkCount>
<reuseForks>true</reuseForks>
<redirectTestOutputToFile>true</redirectTestOutputToFile>
<argLine combine.children="append"> -Xmx1G
-Djava.net.preferIPv4Stack=true</argLine>
</configuration>
</plugin>
See my attached 2 zip files that contain most of all the logs during my
adventures today with various options above:
AppData-Local-Temp.zip
nifi-standard-processors.zip
was (Author: thadguidry):
Spent the entire day running 100+ builds with tests on Windows 7 64bit
Enterprise HP Zbook15 12GB Ram Core i7 (my work laptop).
Generally found that there are some critical tests that do seem to consume mass
amounts of memory with surefire forking options on a Windows system.
I cannot get a build to complete with basic or advanced options such as,
allocating more memory to surefire (up to 4G), allocating more memory to maven
(up to 4G), even tried updating surefire plugin to 2.19.1 and setting pom.xml
setting to use, were forkCount used 2C, 2, 1, 1C.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.19.1</version>
<configuration>
<forkCount>1C</forkCount>
<reuseForks>true</reuseForks>
<redirectTestOutputToFile>true</redirectTestOutputToFile>
<argLine combine.children="append"> -Xmx1G
-Djava.net.preferIPv4Stack=true</argLine>
</configuration>
</plugin>
See my attached 2 zip files that contain most of all the logs during my
adventures today with various options above:
AppData-Local-Temp.zip
nifi-standard-processors.zip
> Test Failures on Windows 7
> --------------------------
>
> Key: NIFI-1368
> URL: https://issues.apache.org/jira/browse/NIFI-1368
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
> Affects Versions: 0.4.1
> Reporter: Aldrin Piri
> Attachments: AppData-Local-Temp.zip, hs_err_pid11228.log,
> nifi-debug-build-on-windows.txt, nifi-standard-processors.zip
>
>
> Environment
> {code}
> C:\dev\code\nifi>mvn -version
> Apache Maven 3.3.1 (cab6659f9874fa96462afef40fcf6bc033d58c1c;
> 2015-03-13T16:10:27-04:00)
> Maven home: C:\dev\apache-maven-3.3.1\bin\..
> Java version: 1.7.0_79, vendor: Oracle Corporation
> Java home: C:\dev\lang\java\jdk1.7.0_79\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> {code}
> Errors included are:
> {code}
> Running org.apache.nifi.controller.scheduling.TestStandardProcessScheduler
> Tests run: 9, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 53.155 sec
> <<< FAILURE! - in
> org.apache.nifi.controller.scheduling.TestStandardProcessScheduler
> testDisableControllerServiceWithProcessorTryingToStartUsingIt(org.apache.nifi.controller.scheduling.TestStandardProcessScheduler)
> Time elapsed: 3.024 sec <<< FAILURE!
> java.lang.AssertionError: null
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.nifi.controller.scheduling.TestStandardProcessScheduler.testDisableControllerServiceWithProcessorTryingToStartUsingIt(TestStandardProcessScheduler.java:139)
> testReportingTaskDoesntKeepRunningAfterStop(org.apache.nifi.controller.scheduling.TestStandardProcessScheduler)
> Time elapsed: 3.75 sec <<< FAILURE!
> java.lang.AssertionError: After unscheduling Reporting Task, task ran an
> additional 3 times
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at
> org.apache.nifi.controller.scheduling.TestStandardProcessScheduler.testReportingTaskDoesntKeepRunningAfterStop(TestStandardProcessScheduler.java:113)
> {code}
> As well as the attached file found by a user trying to build with a similar
> environment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
