[ 
https://issues.apache.org/jira/browse/NIFI-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089663#comment-15089663
 ] 

Aldrin Piri commented on NIFI-1368:
-----------------------------------

Thad,
Thanks for the additional details. 

I think the test errors I provided were from me not following directions for 
Windows and did not have my git checkout configured correctly.
Checked the code out again using 
{quote}
git config --global core.longpaths true
git config --global core.autocrlf false
{quote}

However, this still had some, seemingly arbitrary problems.  I have now just 
gotten a build to pass with the previous environment but upgraded Maven to the 
latest version, 3.3.9.

I looked through the release notes between versions and nothing immediately 
jumped out at me.  If you have a spare moment and are able, would you be able 
to see if that also clears things up for you?

Thanks!


> 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: hs_err_pid11228.log, nifi-debug-build-on-windows.txt
>
>
> 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)

Reply via email to