Skip to content
This repository has been archived by the owner on Sep 24, 2019. It is now read-only.

Build failure for common #63

Open
huangxc2013 opened this issue Nov 13, 2014 · 2 comments
Open

Build failure for common #63

huangxc2013 opened this issue Nov 13, 2014 · 2 comments

Comments

@huangxc2013
Copy link

Passed OpenBEL Framework, BEL, but failed when installing common. The error is "Test set: org.openbel.framework.common.BELUtilitiesTest failed"

Test set: org.openbel.framework.common.BELUtilitiesTest

Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec <<< FAILURE!
testSHA256Hash(org.openbel.framework.common.BELUtilitiesTest) Time elapsed: 0.013 sec <<< FAILURE!
org.junit.ComparisonFailure: expected:<[e96530c04be684f1a468a98d8ab8174bba704503fb69e1ccb5376bfe3f8390c6]> but was:<[70f2e893cc69e8c8b9ead537cc587a4ac22ce22ddebdeaf85e3a663e18fb0321]>
at org.junit.Assert.assertEquals(Assert.java:125)
at org.junit.Assert.assertEquals(Assert.java:147)
at org.openbel.framework.common.BELUtilitiesTest.testSHA256Hash(BELUtilitiesTest.java:83)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)

What should I do?

@abargnesi
Copy link
Member

You are seeing a test failure in BELUtilitiesTest.java:83. The strange thing is that this test passes for me.

What operating system are you building openbel-framework on? Are you building the experimental branch from the github repository?

In a pinch you can always disable tests in maven with the -DskipTests option.

@huangxc2013
Copy link
Author

I am using windows 7 professional, service pack 1, 64 bit. java is JDK 1.7.0. And yes, I am building the experimental branch from the github repository.

I rebuild it using -DskipTests option, now it says all success. Thank you!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants