Test cases failing for OrientDB on powerpc - orientdb

I am officially porting OrientDB (community release) on powerpc ( ppc64le ) . I have cloned the repo from here and followed build steps as below :
$ git clone https://github.com/orientechnologies/orientdb
$ git checkout develop
$ cd orientdb
$ mvn clean install
However getting test case failures as below
Failed tests:
TestBatchRemoteResultSet.runBatchQuery:59
Tests in error:
OCommandExecutorSQLDeleteVertexTest.testDeleteVertexBatch:87 » ODatabase Datab...
OCommandExecutorSQLDeleteVertexTest.testDeleteVertexFromSubquery:114 » ODatabase
OCommandExecutorSQLDeleteVertexTest.testDeleteVertexFromSubquery2:127 » ODatabase
OCommandExecutorSQLDeleteVertexTest.testDeleteVertexLimit:72 » ODatabase Datab...
SimplePropertyLinkTest.testSimplePropertyLink:27 ClassCast java.lang.String in...
Tests run: 384, Failures: 1, Errors: 5, Skipped: 123
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] OrientDB ........................................... SUCCESS [ 3.305 s]
[INFO] OrientDB Test Commons .............................. SUCCESS [ 5.100 s]
[INFO] OrientDB Core ...................................... SUCCESS [03:11 min]
[INFO] OrientDB Client .................................... SUCCESS [ 7.290 s]
[INFO] OrientDB Object .................................... SUCCESS [ 15.109 s]
[INFO] OrientDB Tools ..................................... SUCCESS [ 9.159 s]
[INFO] OrientDB Server .................................... SUCCESS [ 39.269 s]
[INFO] OrientDB GraphDB ................................... FAILURE [01:11 min]
[INFO] OrientDB Tests ..................................... SKIPPED
[INFO] OrientDB Distributed Server ........................ SKIPPED
[INFO] OrientDB Lucene full text index .................... SKIPPED
[INFO] OrientDB JDBC Driver ............................... SKIPPED
[INFO] OrientDB ETL ....................................... SKIPPED
[INFO] OrientDB Community Distribution .................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 05:43 min
[INFO] Finished at: 2016-06-15T13:25:21+05:30
[INFO] Final Memory: 134M/227M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on project orientdb-graphdb: There are test failures.
[ERROR]
[ERROR] Please refer to /root/amit/rethinkDB/orientDB_dev/graphdb/target/surefire-reports for the individual test results.
[ERROR] -> [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 :orientdb-graphdb
[1]: https://github.com/orientechnologies/orientdb
Any pointers on this , have raised a git issue ticket here , but thought of asking here if anyone has seen such errors.

Related

Apache Zeppelin: Trying to build from from source code but zeppelin-web fails

I cloned the 'master' copy of Apache Zeppelin from https://github.com/apache/zeppelin in my Eclipse workspace and followed the steps for installation given as follows:
Created a new Java project and imported zeppelin.
Converted it into a Maven project
I had previously installed NodeJS and subsequently bower.
Activate Maven repository index updates
Window=>Preferences=>Maven and checked the following:
Download Artifact Sources
Download Artifact JavaDoc
Download repository index updates on startup
Update Maven projects on startup
Made sure I had JDK installed
C:/Program Files (or X86)/Java/.. should have JDK(NOT JRE)
Windows => Preferences => search for ‘jre’
Installed JREs => Add… => Standard VM
JRE home: Installed jdk folder location/jdk1.8.***
Right-click on the Project=>Run As => Run Configurations
Double click Maven Build
Name: clean package
Base directory: the zeppelin directory
Goals: clean package
Check ‘Skip Tests’
JRE tab=> choose JDK(installed above) instead of JRE
Run
Most modules pass except zeppelin-web onward
[INFO] Reactor Summary:
[INFO]
[INFO] Zeppelin ........................................... SUCCESS [ 20.674 s]
[INFO] Zeppelin: Interpreter .............................. SUCCESS [01:55 min]
[INFO] Zeppelin: Zengine .................................. SUCCESS [02:36 min]
[INFO] Zeppelin: Display system apis ...................... SUCCESS [01:21 min]
[INFO] Zeppelin: Spark dependencies ....................... SUCCESS [03:32 min]
[INFO] Zeppelin: Spark .................................... SUCCESS [04:05 min]
[INFO] Zeppelin: Markdown interpreter ..................... SUCCESS [ 6.287 s]
[INFO] Zeppelin: Angular interpreter ...................... SUCCESS [ 3.118 s]
[INFO] Zeppelin: Shell interpreter ........................ SUCCESS [ 3.650 s]
[INFO] Zeppelin: Livy interpreter ......................... SUCCESS [ 30.402 s]
[INFO] Zeppelin: HBase interpreter ........................ SUCCESS [04:02 min]
[INFO] Zeppelin: Apache Pig Interpreter ................... SUCCESS [03:37 min]
[INFO] Zeppelin: PostgreSQL interpreter ................... SUCCESS [ 16.102 s]
[INFO] Zeppelin: JDBC interpreter ......................... SUCCESS [ 17.661 s]
[INFO] Zeppelin: File System Interpreters ................. SUCCESS [ 16.002 s]
[INFO] Zeppelin: Flink .................................... SUCCESS [04:32 min]
[INFO] Zeppelin: Apache Ignite interpreter ................ SUCCESS [02:22 min]
[INFO] Zeppelin: Kylin interpreter ........................ SUCCESS [ 5.049 s]
[INFO] Zeppelin: Python interpreter ....................... SUCCESS [ 4.519 s]
[INFO] Zeppelin: Lens interpreter ......................... SUCCESS [02:00 min]
[INFO] Zeppelin: Apache Cassandra interpreter ............. SUCCESS [03:49 min]
[INFO] Zeppelin: Elasticsearch interpreter ................ SUCCESS [01:47 min]
[INFO] Zeppelin: BigQuery interpreter ..................... SUCCESS [ 24.181 s]
[INFO] Zeppelin: Alluxio interpreter ...................... SUCCESS [02:17 min]
[INFO] Zeppelin: web Application .......................... FAILURE [01:27 min]
[INFO] Zeppelin: Server ................................... SKIPPED
[INFO] Zeppelin: Packaging distribution ................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 41:58 min
[INFO] Finished at: 2016-10-20T10:47:21-05:00
[INFO] Final Memory: 141M/508M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:0.0.25:grunt (grunt build) on project zeppelin-web: Failed to run task: 'grunt build --no-color' failed. (error code 3) -> [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 -rf :zeppelin-web
When I did a -e and -X for a debug and error stack I got this:
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:0.0.25:grunt (grunt build) on project zeppelin-web: Failed to run task: 'grunt build --no-color' failed. (error code 3) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.github.eirslett:frontend-maven-plugin:0.0.25:grunt (grunt build) on project zeppelin-web: Failed to run task
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.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoFailureException: Failed to run task
at com.github.eirslett.maven.plugins.frontend.mojo.AbstractFrontendMojo.execute(AbstractFrontendMojo.java:66)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
... 20 more
Caused by: com.github.eirslett.maven.plugins.frontend.lib.TaskRunnerException: 'grunt build --no-color' failed. (error code 3)
at com.github.eirslett.maven.plugins.frontend.lib.NodeTaskExecutor.execute(NodeTaskExecutor.java:59)
at com.github.eirslett.maven.plugins.frontend.mojo.GruntMojo.execute(GruntMojo.java:64)
at com.github.eirslett.maven.plugins.frontend.mojo.AbstractFrontendMojo.execute(AbstractFrontendMojo.java:64)
... 22 more
[ERROR]
I have been looking through SO for weeks but this is the closest post I found: Apache Zeppelin installation grunt build error and even asked the person if a solution was found, no response. The solution posted in there didn't work for me.
I am doing all this on a Windows Server 2008 R2 Standard box. I'd be deeply grateful if someone could point me in the right direction in terms of a solution.
It looks like the frontend webapp build fails on your windows box.
Please try running npm run build manually on the latest sources - that will give more verbose logs and will help to find the reason.
At least on Linux - there are few pre-requests in order for it to work i.e libfontconfig

Failed to execute goal net.alchim31.maven:scala-maven-plugin:3.2.2

While compiling the Maven project the following error occured:
[INFO] --- scala-maven-plugin:3.2.2:compile (scala-compile-first) # spark-streaming-flume-sink_2.10 ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 6 Scala sources and 3 Java sources to /home/gorlec/Desktop/test/external/flume-sink/target/scala-2.10/classes...
[ERROR] /home/gorlec/Desktop/test/external/flume-sink/src/main/scala/org/apache/spark/streaming/flume/sink/SparkAvroCallbackHandler.scala:47: identifier expected but 'with' found.
[ERROR] with Logging {
[ERROR] ^
[ERROR] one error found
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 7.992s
[INFO] Finished at: Fri Apr 15 17:44:33 CEST 2016
[INFO] Final Memory: 25M/350M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal net.alchim31.maven:scala-maven-plugin:3.2.2:compile (scala-compile-first) on project spark-streaming-flume-sink_2.10: Execution scala-compile-first of goal net.alchim31.maven:scala-maven-plugin:3.2.2:compile failed. CompileFailed ->
[Help 1]
[ERROR]
I removed the property <useZincServer>true</useZincServer> from pom.xml, and still the Logging error persists.
[INFO] --- scala-maven-plugin:3.2.2:compile (scala-compile-first) # spark-streaming-flume-sink_2.10 ---
[INFO] Using incremental compilation
[INFO] Compiling 6 Scala sources and 3 Java sources to /home/gorlec/Desktop/test/external/flume-sink/target/scala-2.10/classes...
[ERROR] /home/gorlec/Desktop/test/external/flume-sink/src/main/scala/org/apache/spark/streaming/flume/sink/SparkAvroCallbackHandler.scala:47: identifier expected but 'with' found.
[ERROR] with Logging {
[ERROR] ^
[ERROR] one error found
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5.814s
[INFO] Finished at: Fri Apr 15 17:41:00 CEST 2016
[INFO] Final Memory: 25M/335M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal net.alchim31.maven:scala-maven-plugin:3.2.2:compile (scala-compile-first) on project spark-streaming-flume-sink_2.10: Execution scala-compile-first of goal net.alchim31.maven:scala-maven-plugin:3.2.2:compile failed. CompileFailed ->
[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.
I checked that PATH and JAVA_HOME are defined in ~/.bashrc as follows:
export PATH=$PATH:/usr/lib/jvm/java-7-openjdk-amd64/bin
export JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64
The only issue that I noticed is that echo $JAVA_HOME gives an empty output, though I did source ~/.bashrc.
Any help is highly appreciated.
The problem could be this [INFO] Using incremental compilation
In your pom.xml try to remove the line <recompileMode>incremental</recompileMode>
and then try again.
It is strange echo $JAVA_HOME gives an empty output.While compling the Spakr Source,I import the mvn clean package success porject into eclipse,I meet the same problem.And I found the solution here:
How to solve “Plugin execution not covered by lifecycle configuration” for Spring Data Maven Builds
I think you were compiling Spark with Scala 2.10. If so, you should do as follows.
cd /path/to/Spark
./dev/change-scala-version.sh 2.10
./build/mvn -Pyarn -Phadoop-2.4 -Dscala-2.10 -DskipTests clean package
Hope this helps.

Cygnus 0.10 Docker container

Following the guidelines provided in GITHub,
I have tried to get the jar files, but I'm getting the following errors.
sudo docker-compose -f ./docker/0.compose.jar-compiler.yml -p cygnus run --rm compiler
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building cygnus 0.10.0
[INFO] ------------------------------------------------------------------------
[WARNING] The artifact xml-apis:xml-apis:jar:1.2.01 has been relocated to xerces:xmlParserAPIs:jar:2.6.2
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) # cygnus ---
[INFO] Deleting /cygnus-compiler/target
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) # cygnus ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) # cygnus ---
[INFO] Compiling 44 source files to /cygnus-compiler/target/classes
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /cygnus-compiler/src/main/java/com/telefonica/iot/cygnus/backends/hdfs/HDFSBackendImpl.java:[40,7] error: HDFSBackendImpl is not abstract and does not override abstract method provisionHiveTable(FileFormat,String,String) in HDFSBackend
[INFO] 1 error
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3.703 s
[INFO] Finished at: 2015-11-23T10:45:31+00:00
[INFO] Final Memory: 30M/352M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project cygnus: Compilation failure
[ERROR] /cygnus-compiler/src/main/java/com/telefonica/iot/cygnus/backends/hdfs/HDFSBackendImpl.java:[40,7] error: HDFSBackendImpl is not abstract and does not override abstract method provisionHiveTable(FileFormat,String,String) in HDFSBackend
[ERROR] -> [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
I run this command from the root of the repository:
docker-compose -f ./docker/0.compose.jar-compiler.yml -p cygnus run --rm compiler
Can anybody help me out on this?

When trying to install jar in local repository using maven

I do not have this SFTP jar in my Nexus Repo & I have add it's dependency into the POM file but now i want to install this JAR in my local repository so that i can use it in my project. But getting access is denied even though i opened command prompt with Administrator rights.
C:\Windows\system32>mvn install:install-file -DgroupId=org.springframework.integration -DartifactId=spring-integration-sftp -Dversion=4.1.5 -Dpackaging=jar -Dfile=C:\Repo
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Stub Project (No POM) 1
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-install-plugin:2.4:install-file (default-cli) # standalone-pom
---
[INFO] Installing C:\Repo to C:\Users\t868396\.m2\repository\org\springframework
\integration\spring-integration-sftp\4.1.5\spring-integration-sftp-4.1.5.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.827 s
[INFO] Finished at: 2015-06-23T11:02:52+05:00
[INFO] Final Memory: 15M/64M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-install-plugin:2.4
:install-file (default-cli) on project standalone-pom: Error installing artifact
'org.springframework.integration:spring-integration-sftp:jar': Failed to instal
l artifact org.springframework.integration:spring-integration-sftp:jar:4.1.5: C:
\Repo (Access is denied) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
ch.
[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 rea
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionE
xception
Mostly likely the -Dfile=your.jar is not correct, check your argument (FYI it was omitted from your posting).
Here is an example:
mvn install:install-file -DlocalRepositoryPath=repo -DcreateChecksum=true
-Dfile=[your-jar] -Dpackaging=jar
-DgroupId=[...] -DartifactId=[...] -Dversion=[...]
See: Can I add jars to maven 2 build classpath without installing them?
And: https://maven.apache.org/general.html#importing-jars

Maven: Failed to resolve dependency: C:\Program Files\Java\lib\tools.jar

I'm trying to use the cargo plugin to run a web application in a local Jetty container from inside Eclipse. This seems to be working for other people with the exact same pom.xml, but I get this error:
[ERROR] Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.0.3:start (default-cli) on project wsc: Failed to resolve dependency: C:\Program Files\Java\lib\tools.jar -> [Help 1]
How do I resolve this? The project is set to use jdk1.7.0 as the "JRE System Library". I am starting Eclipse with "-vm " and even JAVA_HOME is set to the JDK path.
Any ideas? I've been researching on this for a while and getting crazy about that. The documentation on including tools.jar as dependency didn't help me.
Important: This seems to work outside Eclipse, e.g. with mvn -P local cargo:start.
Program output when started from Eclipse:
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Web Services Computing 0.0.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- cargo-maven2-plugin:1.0.3:start (default-cli) # wsc ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.324s
[INFO] Finished at: Sat Oct 22 19:10:18 CEST 2011
[INFO] Final Memory: 15M/107M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.0.3:start (default-cli) on project wsc: Failed to resolve dependency: C:\Program Files\Java\lib\tools.jar -> [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/MojoExecutionException
Dependency tree output (also started from Eclipse):
[INFO] --- maven-dependency-plugin:2.1:tree (default-cli) # wsc ---
[INFO] de.tum.ibis.wsc:wsc:war:0.0.1-SNAPSHOT
[INFO] +- junit:junit:jar:3.8.1:test
[INFO] \- javax.servlet:servlet-api:jar:2.5:compile
[INFO] ------------------------------------------------------------------------
You have to start eclipse with a jdk instead of a jre.
If you edit your eclipse.ini and put a jdk to the vm arguments it should work.
-vm
C:/java_1_6/jdk/bin/javaw.exe