linikujp / owltools

Automatically exported from code.google.com/p/owltools
0 stars 0 forks source link

owltools maven build failure #107

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. svn checkout http://owltools.googlecode.com/svn/trunk/ owltools-read-only
2. cd ./owltools-read-only/OWLTools-Parent
3. mvn clean package

What is the expected output? What do you see instead?

Expect a successful owltools build.

I got a build failure with essentially the same symptoms reported in ticket 103 
(https://code.google.com/p/owltools/issues/detail?id=103).

end of output:
Results :

Failed tests:   testLineageShuntGraph(owltools.graph.OWLGraphShuntTest): e?? 
expected:<false> but was:<true>

Tests run: 151, Failures: 1, Errors: 0, Skipped: 4

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] OWLTools-Parent .................................... SUCCESS [  1.900 s]
[INFO] OWLTools-Core ...................................... FAILURE [12:57 min]
[INFO] Lego ............................................... SKIPPED
[INFO] OWLTools-Annotation ................................ SKIPPED
[INFO] OWLTools-Oort ...................................... SKIPPED
[INFO] OWLTools-Sim ....................................... SKIPPED
[INFO] OWLTools-Web ....................................... SKIPPED
[INFO] OWLTools-Solr ...................................... SKIPPED
[INFO] OWLTools-Runner .................................... SKIPPED
[INFO] OWLTools-NCBI ...................................... SKIPPED
[INFO] MolecularModelServer ............................... SKIPPED
[INFO] Golr-Client ........................................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 13:00 min
[INFO] Finished at: 2014-11-20T11:09:44+00:00
[INFO] Final Memory: 18M/81M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.12.2:test (default-test) on 
project OWLTools-Core: There are test failures.
[ERROR] 
[ERROR] Please refer to 
/Applications/owltools-read-only/OWLTools-Core/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 :OWLTools-Core

What version of the product are you using? On what operating system?
owltools - checked out Nov. 14, 2014
maven - Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 
2014-08-11T21:58:10+01:00)

OS - Mac OS X Yosemite Version 10.10

Please provide any additional information below.

New laptop; I have permissions to install to /Applications/; it also has Java 
1.8.0_25 installed

Tried this build last week with same results (or lack thereof)

I see that http://build.berkeleybop.org/job/owltools/ is reporting test 
failures, and that the last successful build was a couple weeks ago. Could that 
be connected?

thanks,
midori

Original issue reported on code.google.com by midori.h...@gmail.com on 20 Nov 2014 at 11:16

GoogleCodeExporter commented 9 years ago
Hello,
Thank you for reporting the issue. Yes your problem is directly related to 
these failing integration tests. I have committed multiple changes to address 
the failing tests.

Original comment by HDie...@lbl.gov on 21 Nov 2014 at 7:02

GoogleCodeExporter commented 9 years ago
Thanks -- I had to delete owltools and do a fresh svn checkout (svn update 
didn't do the trick), and then the build succeeded.

m

Original comment by midori.h...@gmail.com on 24 Nov 2014 at 2:18

GoogleCodeExporter commented 9 years ago

Original comment by HDie...@lbl.gov on 4 Dec 2014 at 9:55