所有playOrm测试失败

Question

我刚刚下载了最后一个版本的代码，并尝试了"ant testCheckin“。

所有测试都失败了。我做错什么了？我尝试了IN_MEMORY和CASSANDRA在factorySingleton中的配置

T、E、S、T、S

运行com.alvazan.test.TestColumnSlice SLF4J:类路径包含多个SLF4J绑定。jar:file:/home/mvalle/.m2/repository/org/slf4j/slf4j-log4j12/1.6.1/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class :在jar:file:/home/mvalle/.m2/repository/ch/qos/logback/logback-classic/1.0.1/logback-classic-1.0.1.jar!/org/slf4j/impl/StaticLoggerBinder.class SLF4J中找到绑定:在jar:file:/home/mvalle/.m2/repository/ch/qos/logback/logback-classic/1.0.1/logback-classic-1.0.1.jar！/org/slf4j/impl/StaticLoggerBinder.class SLF4J中找到绑定:有关解释，请参见bindings。Log4j:没有为记录器(com.alvazan.test.FactorySingleton)找到任何附加程序。log4j :警告请正确初始化log4j系统。Log4j:警告参见http://logging.apache.org/log4j/1.2/faq.html#noconfig以获得更多信息。测试运行: 4，失败: 0，错误: 4，跳过: 0，时间流逝: 2.075秒<<<失败！testDecimalColumnSlice(com.alvazan.test.TestColumnSlice)时间流逝:1993年秒<<<错误！com.alvazan.orm.impl.meta.data.MetaClassSingle不能被投到com.alvazan.orm.impl.meta.scan.ScannerForField.processToOne(ScannerForField.java:342)，com.alvazan.orm.impl.meta.scan.ScannerForField.processManyToOne(ScannerForField.java:202)，com.alvazan.orm.impl.meta.scan.ScannerForClass.inspectField(ScannerForClass.java:185)，com.alvazan.orm。impl.meta.scan.ScannerForClass.scanFields(ScannerForClass.java:169) at com.alvazan.orm.impl.meta.scan.ScannerForClass.scanSingle(ScannerForClass.java:108) at com.alvazan.orm.impl.meta.scan.ScannerForClass.addClass(ScannerForClass.java:67) at com.alvazan.orm.layer0.base.MyClassAnnotationDiscoveryListener.scanClass(MyClassAnnotationDiscoveryListener.java:41) at com.alvazan.orm.layer0.base.MyClassAnnotationDiscoveryListener.discovered(MyClassAnnotationDiscoveryListener.java:34) at com.impetus.annovention.Discoverer.discoverAndIntimateForClassAnnotations(Discoverer.java:197) at com.impetus.annovention.Discoverer.discover(Discoverer.java:155) at com.alvazan.orm.layer0.base.BaseEntityManagerFactoryImpl.rescan(BaseEntityManagerFactoryImpl.java:80) at com.alvazan.orm.layer0.base.BaseEntityManagerFactoryImpl.setup(BaseEntityManagerFactoryImpl.java:131) at com.alvazan.orm.impl.bindings.BootstrapImpl.createInstance(BootstrapImpl.java:51) at com.alvazan.orm.api.base.Bootstrap.create(Bootstrap.java：26)在com.alvazan.orm.api.base.Bootstrap.create(Bootstrap.java:21) at com.alvazan.test.FactorySingleton.createFactory(FactorySingleton.java:56) at com.alvazan.test.FactorySingleton.createFactoryOnce(FactorySingleton.java:37) at com.alvazan.test.TestColumnSlice.createEntityManager(TestColumnSlice.java:32) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)在sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect。DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27) atorg.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org。junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) 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( sun.reflect.NativeMethodAccessorImpl.invoke0(Native方法)在sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)，sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)，java.lang.reflect.Method.invoke(Method.java:601)，org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)，org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)，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)

Answer 1

好吧，我们找到了。这个bug现在在PlayOrm中被修复了。结果是，扫描以不同的顺序扫描类，当以不同的顺序扫描时会发现一个错误。这个错误不是固定的，所以仍然可以按任何顺序扫描。

我让别人检查并运行。/build和他的运行很好，所以可以调试你的问题.

1. 运行git状态并查看所做的更改。
2. 我添加了一些“调试”级别的日志，并打开了调试，所以更新到最新(这些将帮助我进一步调试，而且我需要更多的日志在这些领域)
3. 运行TestKeyTypes.testIntegerType，剪切并粘贴问题中的日志，这样我就可以进一步调试它

我的猜测是，您对某些继承实体进行了更改，这些更改没有正确地抛出“您不能这样做”的例外(而且我有大量的继承实体，但可能缺少一个)。

院长