[YANGTOOLS-514] java.lang.NoSuchMethodError when calling CrossSourceStatementReactor$BuildAction.buildEffective from ModuleInfoBackedContext Created: 30/Sep/15  Updated: 10/Apr/22  Resolved: 16/Oct/15

Status: Resolved
Project: yangtools
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Jeff Liu Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 4372

 Description   

The following error encountered when running test cases extended from AbstractSchemaAwareTest.java.

java.lang.NoSuchMethodError when calling CrossSourceStatementReactor$BuildAction.buildEffective from ModuleInfoBackedContext.

Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.613 sec <<< FAILURE! - in org.opendaylight.protocol.bmp.impl.app.BmpMonitorImplTest
testMonitoringStation(org.opendaylight.protocol.bmp.impl.app.BmpMonitorImplTest) Time elapsed: 0.55 sec <<< ERROR!
java.lang.NoSuchMethodError: org.opendaylight.yangtools.yang.parser.stmt.reactor.CrossSourceStatementReactor$BuildAction.buildEffective(Ljava/util/Collection;)Lorg/opendaylight/yangtools/yang/model/api/S
chemaContext;
at org.opendaylight.yangtools.sal.binding.generator.impl.ModuleInfoBackedContext.recreateSchemaContext(ModuleInfoBackedContext.java:89)
at org.opendaylight.yangtools.sal.binding.generator.impl.ModuleInfoBackedContext.tryToCreateSchemaContext(ModuleInfoBackedContext.java:102)
at org.opendaylight.controller.md.sal.binding.test.AbstractSchemaAwareTest.setup(AbstractSchemaAwareTest.java:32)
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:47)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)



 Comments   
Comment by Peter Kajsa [ 30/Sep/15 ]

Hi Jeff,

do you have builded to most recent version of yangtools master branch ?

BR.
Peter.

Comment by Jeff Liu [ 30/Sep/15 ]

yes, I git pull the latest from master and still have this error.

Comment by Robert Varga [ 01/Oct/15 ]

Jenkins verification seems to be working just fine. Is this failing for a proposed patch?

Comment by Martin Ciglan [ 15/Oct/15 ]

Hi Jeff

Can you confirm this is still issue with freshly pulled and built Yangtools & MD-SAL projects? Thank you.

Comment by Jeff Liu [ 15/Oct/15 ]

I think this issue has been resolved a while ago and I haven't been able to reproduce it. Please consider this is fixed.

Generated at Wed Feb 07 20:53:28 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.