the only items under .plxarc classes generated-sources generated-test-sources maven-archiver maven-shared-archive-resources maven-status nifi-framework-core-0.3.1-SNAPSHOT.jar test-classes
I searched for *FileQueue*.txt but no files found. I can create a new VM and try again. I do have a few things on this server. > On Nov 4, 2015, at 9:01 AM, Mark Payne <[email protected]> wrote: > > Jeff, > > I just checked out a fresh build from master, running on CentOS 7 and was > able to build without any problems. > So I don't think it is specifically a problem with CentOS 7. Can you provide > the output of the unit tests? > > They should be in > ${NIFI_SRC_DIR}/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports > > The two files of interest are > org.apache.nifi.controller.TestStandardFlowFileQueue.txt and > org.apache.nifi.controller.TestStandardFlowFileQueue-output.txt > > Thanks! > -Mark > > >> On Nov 4, 2015, at 8:53 AM, Jeff <[email protected]> wrote: >> >> Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 28.916 sec >> <<< FAILURE! - in org.apache.nifi.controller.TestStandardFlowFileQueue >> testDropSwappedFlowFiles(org.apache.nifi.controller.TestStandardFlowFileQueue) >> Time elapsed: 21.825 sec <<< ERROR! >> org.junit.runners.model.TestTimedOutException: test timed out after 20000 >> milliseconds >> at java.lang.Throwable.fillInStackTrace(Native Method) >> at java.lang.Throwable.fillInStackTrace(Throwable.java:783) >> at java.lang.Throwable.<init>(Throwable.java:250) >> at >> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:24) >> at >> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:19) >> at >> org.mockito.internal.invocation.InvocationImpl.<init>(InvocationImpl.java:50) >> at >> org.mockito.internal.creation.cglib.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:58) >> at >> org.apache.nifi.connectable.Connection$$EnhancerByMockitoWithCGLIB$$8aa704ad.getDestination(<generated>) >> at >> org.apache.nifi.controller.StandardFlowFileQueue.put(StandardFlowFileQueue.java:315) >> at >> org.apache.nifi.controller.TestStandardFlowFileQueue.testDropSwappedFlowFiles(TestStandardFlowFileQueue.java:169) >> >>> On Nov 4, 2015, at 7:51 AM, Brandon DeVries <[email protected]> wrote: >>> >>> Jeff, >>> >>> Can you see what tests had failures? Also, if you just want to verify that >>> your system can do the build, you could do something like "mvn clean >>> install -DskipTests". Let us know what you see. Thanks. >>> >>> Brandon >>> >>> On Wed, Nov 4, 2015 at 8:46 AM, Jeff <[email protected]> wrote: >>> >>>> >>>> Well, the build got much further with the Oracle JDK but still failed; >>>> >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] BUILD FAILURE >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] Total time: 07:47 min (Wall Clock) >>>> [INFO] Finished at: 2015-11-03T17:07:40-06:00 >>>> [INFO] Final Memory: 183M/564M >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [ERROR] Failed to execute goal >>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on >>>> project nifi-framework-core: There are test failures. >>>> [ERROR] >>>> [ERROR] Please refer to >>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports >>>> for the individual test results. >>>> >>>> >>>> >>>>> On Nov 3, 2015, at 6:54 PM, Cerulean Blue <[email protected]> wrote: >>>>> >>>>> Oh, I also adjusted the memory! >>>>> >>>>> Sent from my iPhone >>>>> >>>>>> On Nov 3, 2015, at 6:50 PM, Joe Witt <[email protected]> wrote: >>>>>> >>>>>> Jeff - can you please send another note telling Tony that it turns out >>>>>> it was memory settings :-) >>>>>> >>>>>> He is making fun of me off-list. He should totally do that on-list! >>>>>> >>>>>> Glad you're in business now and sorry for my terrible misdirection. >>>>>> >>>>>> Joe >>>>>> >>>>>>> On Wed, Nov 4, 2015 at 12:49 AM, Tony Kurc <[email protected]> wrote: >>>>>>> Huzzah >>>>>>> >>>>>>>> On Tue, Nov 3, 2015 at 7:48 PM, Jeff <[email protected]> wrote: >>>>>>>> >>>>>>>> >>>>>>>> I removed openjdk and installed the Oracle jdk and it now works. >>>>>>>> >>>>>>>> Thanks for the help!! >>>>>>>> >>>>>>>>> On Nov 3, 2015, at 6:40 PM, Tony Kurc <[email protected]> wrote: >>>>>>>>> >>>>>>>>> it is entirely possible that you only have the jre installed. 'yum >>>>>>>>> whatprovides "*/bin/javac"' may tell you packages which you can >>>> install >>>>>>>>> which include a compiler. >>>>>>>>> >>>>>>>>>> On Tue, Nov 3, 2015 at 7:35 PM, Jeff <[email protected]> wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> find / -name javac did not return anything >>>>>>>>>> >>>>>>>>>> I had JAVA_HOME set to >>>>>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> On Nov 3, 2015, at 6:30 PM, Tony Kurc <[email protected]> wrote: >>>>>>>>>>> >>>>>>>>>>> Jeff, >>>>>>>>>>> Were you able to run that find command? >>>>>>>>>>> >>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <[email protected]> wrote: >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> [INFO] BUILD FAILURE >>>>>>>>>>>> [INFO] >>>>>>>> >>>> ------------------------------------------------------------------------ >>>>>>>>>>>> [INFO] Total time: 8.091 s >>>>>>>>>>>> [INFO] Finished at: 2015-11-03T12:08:59-06:00 >>>>>>>>>>>> [INFO] Final Memory: 76M/365M >>>>>>>>>>>> [INFO] >>>>>>>> >>>> ------------------------------------------------------------------------ >>>>>>>>>>>> [ERROR] Failed to execute goal >>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile >>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure -> >>>> [Help 1] >>>>>>>>>>>> [ERROR] >>>>>>>>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven >>>> with >>>>>>>> the >>>>>>>>>>>> -e switch. >>>>>>>>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug >>>> logging. >>>>>>>>>>>> [ERROR] >>>>>>>>>>>> [ERROR] For more information about the errors and possible >>>> solutions, >>>>>>>>>>>> please read the following articles: >>>>>>>>>>>> [ERROR] [Help 1] >>>>>>>>>>>> >>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException >>>>>>>>>>>> [ERROR] >>>>>>>>>>>> [ERROR] After correcting the problems, you can resume the build >>>> with >>>>>>>> the >>>>>>>>>>>> command >>>>>>>>>>>> [ERROR] mvn <goals> -rf :nifi-api >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> On Nov 3, 2015, at 6:07 PM, Joe Witt <[email protected]> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> Can you go ahead and try just plain ol' >>>>>>>>>>>>> >>>>>>>>>>>>> mvn clean install >>>>>>>>>>>>> >>>>>>>>>>>>> I am curious if there is a memory/settings issue that is >>>> manifesting >>>>>>>>>>>>> as an exception during compilation but that it isn't actually a >>>>>>>>>>>>> compilation problem at all... >>>>>>>>>>>>> >>>>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <[email protected]> >>>> wrote: >>>>>>>>>>>>>> The only other message I see is >>>>>>>>>>>>>> >>>>>>>>>>>>>> [WARNING] Unable to autodetect 'javac' path, using 'javac' from >>>> the >>>>>>>>>>>> environment. >>>>>>>>>>>>>> >>>>>>>>>>>>>> No worries, it can wait. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <[email protected]> >>>> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> if i weren't on horrible hotel wifi right now i'd try to pull >>>> down >>>>>>>>>>>>>>> centos. Is there anymore that can be found with those stack >>>>>>>> traces . >>>>>>>>>>>>>>> They're not saying much. Your java and maven versions seem >>>> quite >>>>>>>>>> good >>>>>>>>>>>>>>> so need to dig further. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <[email protected]> >>>> wrote: >>>>>>>>>>>>>>>> JAVA_HOME is currently not set but I’ve tried both ways. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> [root@localhost nifi]# java -version >>>>>>>>>>>>>>>> openjdk version "1.8.0_65" >>>>>>>>>>>>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17) >>>>>>>>>>>>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode) >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> [root@localhost nifi]# mvn -version >>>>>>>>>>>>>>>> which: no javac in >>>>>>>> >>>> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin) >>>>>>>>>>>>>>>> Warning: JAVA_HOME environment variable is not set. >>>>>>>>>>>>>>>> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; >>>>>>>>>>>> 2015-04-22T06:57:37-05:00) >>>>>>>>>>>>>>>> Maven home: /opt/apache-maven-3.3.3 >>>>>>>>>>>>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation >>>>>>>>>>>>>>>> Java home: >>>>>>>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre >>>>>>>>>>>>>>>> Default locale: en_US, platform encoding: UTF-8 >>>>>>>>>>>>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64", arch: >>>>>>>>>>>> "amd64", family: "unix" >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <[email protected]> >>>> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Jeff >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> When you run 'java -version' and 'mvn -version' what do you >>>> get >>>>>>>>>> back? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Thanks >>>>>>>>>>>>>>>>> Joe >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <[email protected]> >>>>>>>> wrote: >>>>>>>>>>>>>>>>>> I’m getting the below on a VM. It does build successfully >>>> on my >>>>>>>>>>>> Mac, though. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> mvn -e -X -T 2.0C clean install >>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal >>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile >>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure -> >>>> [Help 1] >>>>>>>>>>>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: >>>> Failed >>>>>>>> to >>>>>>>>>>>> execute goal >>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile >>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure >>>>>>>>>>>>>>>>>> at >>>>>>>> >>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) >>>>>>>>>>>>>>>>>> at >>>>>>>> >>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) >>>>>>>>>>>>>>>>>> at >>>>>>>> >>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) >>>>>>>>>>>>>>>>>> at >>>>>>>> >>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) >>>>>>>>>>>>>>>>>> at >>>>>>>> >>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189) >>>>>>>>>>>>>>>>>> at >>>>>>>> >>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185) >>>>>>>>>>>>>>>>>> at java.util.concurrent.FutureTask.run(FutureTask.java:266) >>>>>>>>>>>>>>>>>> at >>>>>>>> >>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) >>>>>>>>>>>>>>>>>> at java.util.concurrent.FutureTask.run(FutureTask.java:266) >>>>>>>>>>>>>>>>>> at >>>>>>>> >>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >>>>>>>>>>>>>>>>>> at >>>>>>>> >>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >>>>>>>>>>>>>>>>>> at java.lang.Thread.run(Thread.java:745) >>>>>>>>>>>>>>>>>> Caused by: >>>>>>>>>>>> org.apache.maven.plugin.compiler.CompilationFailureException: >>>>>>>>>> Compilation >>>>>>>>>>>> failure >>>>>>>>>>>>>>>>>> at >>>>>>>> >>>> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913) >>>>>>>>>>>>>>>>>> at >>>>>>>> >>>> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129) >>>>>>>>>>>>>>>>>> at >>>>>>>> >>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) >>>>>>>>>>>>>>>>>> at >>>>>>>> >>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) >>>>>>>>>>>>>>>>>> ... 11 more >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>>>>> Jeff >>>>>>>> >>>>>>>> >>>> >>>> >> >
