Actually from the output you are running Windows, not Linux. I've only built on Windows. But it's possible that someone updated the tests since I last built.
Sent from my iPhone > On Dec 14, 2014, at 11:34 AM, Joe Witt <[email protected]> wrote: > > Building on Linux is all I've done. >> On Dec 14, 2014 11:32 AM, "Mark Payne" <[email protected]> wrote: >> >> Based on the error message, it looks like a problem with line endings. >> expecting \r\n and only getting a \n. So it will likely fail if running in >> Linux? Have others had issues running this in Linux? >> >> I'm not at a computer right now, but I can look into it Monday morning if >> nobody else has addressed it by then. >> >> In the mean time, you could just ignore the tests if you want to get it >> built >> >> Sent from my iPhone >> >>> On Dec 14, 2014, at 10:35 AM, Joe Gresock <[email protected]> wrote: >>> >>> Well, it turns out I get the exact same 19 failures in the develop >> branch. >>> My next step will be to try to build with Java 7. >>> >>> FYI, here is the maven -version: >>> >>> Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; >>> 2014-08-11T16:58:10-04:00) >>> Maven home: c:\Program Files\apache-maven-3.2.3 >>> Java version: 1.8.0_25, vendor: Oracle Corporation >>> Java home: c:\Program Files\Java\jdk1.8.0_25\jre >>> Default locale: en_US, platform encoding: Cp1252 >>> OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos" >>> >>> Also, as I mentioned above, this happens both on the command line and as >> a >>> Junit test from Eclipse Luna. I'll let you know what happens when I try >>> with Java 7. >>> >>> On Sun, Dec 14, 2014 at 7:32 AM, Karl Heinz Marbaise <[email protected]> >>> wrote: >>> >>>> Hi Joe, >>>> >>>>> On 12/14/14 1:07 PM, Joe Witt wrote: >>>>> >>>>> The 'master' branch is just the code as initially contributed. It will >>>>> be updated once we have a release. >>>>> >>>>> The branch you will wan to work with to stay up to date with the >>>>> progress is 'develop'. Java 8 is expected to work but not tested yet. >>>>> Maven 3.2.3 is required at this moment but am testing/working with a >>>>> patch from Karl-Heinz that may help relax the requirement to 3.x >>>> >>>> If you need further help for that please just ask... >>>> >>>> Kind regards >>>> Karl Heinz Marbaise >>>> >>>> >>>>> The test failure Karl-Heinz notes is fixed on the develop branch. >>>>> >>>>> So for develop branch here is the current guidance: >>>>> http://nifi.incubator.apache.org/development/quickstart.html >>>>> >>>>> Thanks >>>>> Joe >>>>> >>>>> >>>>> >>>>> On Sun, Dec 14, 2014 at 3:15 AM, Karl Heinz Marbaise < >> [email protected] >>>>> <mailto:[email protected]>> wrote: >>>>> >>>>> Hi, >>>>> >>>>> have you tested that on command line only ? >>>>> >>>>> I have run the test on Mac OS by using misc/build-order.sh which >>>>> produces exactly a single test failure... >>>>> >>>>> testImportTemplate(org.apache.__nifi.integration.__accesscontrol.__ >>>>> DfmAccessControlTest) >>>>> Time elapsed: 0.271 sec <<< FAILURE! >>>>> java.lang.AssertionError: expected:<201> but was:<200> >>>>> at org.junit.Assert.fail(Assert.__java:88) >>>>> at org.junit.Assert.__failNotEquals(Assert.java:743) >>>>> at org.junit.Assert.assertEquals(__Assert.java:118) >>>>> at org.junit.Assert.assertEquals(__Assert.java:555) >>>>> at org.junit.Assert.assertEquals(__Assert.java:542) >>>>> at >>>>> >> org.apache.nifi.integration.__accesscontrol.__DfmAccessControlTest.__ >>>>> testImportTemplate(__DfmAccessControlTest.java:__1310) >>>>> >>>>> Running >>>>> org.apache.nifi.integration.__accesscontrol.__ >>>>> ReadOnlyAccessControlTest >>>>> Tests run: 39, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: >>>>> 9.53 sec - in >>>>> org.apache.nifi.integration.__accesscontrol.__ >>>>> ReadOnlyAccessControlTest >>>>> >>>>> Results : >>>>> >>>>> Failed tests: >>>>> DfmAccessControlTest.__testImportTemplate:1310 expected:<201> but >>>>> was:<200> >>>>> >>>>> Running with Java 1.7. >>>>> >>>>> Kind regards >>>>> Karl Heinz Marbaise >>>>> >>>>> >>>>> >>>>> On 12/14/14 5:15 AM, Joe Gresock wrote: >>>>> >>>>> Hi guys, >>>>> >>>>> I just checked out master and tried to run misc/build-order.sh. >>>>> It got up >>>>> to standard-processors and then had 19 unit test failures. Is >>>>> the build >>>>> supposed to be working now? >>>>> >>>>> I'm running Java 1.8 u25 on Windows. I get the same test >>>>> failures running >>>>> both from maven 3.2.3 and in JUnit within Eclipse. Here's one >>>>> example: >>>>> >>>>> java.lang.AssertionError: FlowFile content differs from input at >>>>> byte 20 >>>>> with input having value 13 and FlowFile having value 10 >>>>> at org.junit.Assert.fail(Assert.__java:88) >>>>> at >>>>> org.apache.nifi.util.__MockFlowFile.__assertContentEquals(__ >>>>> MockFlowFile.java:252) >>>>> at >>>>> org.apache.nifi.util.__MockFlowFile.__assertContentEquals(__ >>>>> MockFlowFile.java:204) >>>>> at >>>>> org.apache.nifi.util.__MockFlowFile.__assertContentEquals(__ >>>>> MockFlowFile.java:192) >>>>> at >>> >>> >>> -- >>> I know what it is to be in need, and I know what it is to have plenty. I >>> have learned the secret of being content in any and every situation, >>> whether well fed or hungry, whether living in plenty or in want. I can >> do >>> all this through him who gives me strength. *-Philippians 4:12-13* >>
