Yes, I redid the following: 1) svn up 2) mvn clean install at the root dir 3) run the standalone tck - mvn clean test -Ptck
emailable-report.html: there are many various errors and here are a few of them - org.jboss.jsr299.tck.tests.context.DestroyForSameCreationalContextTest:testDestroyForSameCreationalContextOnly WebBeans context with scope type annotation @SessionScoped does not exist within current thread org.apache.webbeans.container.BeanManagerImpl.getContext(BeanManagerImpl.java:307) at org.apache.webbeans.container.InjectableBeanManager.getContext(InjectableBeanManager.java:103) at org.jboss.jsr299.tck.tests.context.DestroyForSameCreationalContextTest.testDestroyForSameCreationalContextOnly(DestroyForSameCreationalContextTest.java:48) 44 lines not shown ---------- org.jboss.jsr299.tck.tests.context.DestroyedInstanceReturnedByGetTest:testDestroyedInstanceMustNotBeReturnedByGet null org.jboss.jsr299.tck.tests.context.DestroyedInstanceReturnedByGetTest.testDestroyedInstanceMustNotBeReturnedByGet(DestroyedInstanceReturnedByGetTest.java:42) 44 lines not shown ---------- org.jboss.jsr299.tck.tests.context.GetFromContextualTest:testGetMayNotCreateNewInstanceUnlessCreationalContextGiven null java.util.HashMap$HashIterator.nextEntry(HashMap.java:796) at java.util.HashMap$KeyIterator.next(HashMap.java:828) at org.jboss.jsr299.tck.tests.context.GetFromContextualTest.testGetMayNotCreateNewInstanceUnlessCreationalContextGiven(GetFromContextualTest.java:42) 44 lines not shown ---------- org.jboss.jsr299.tck.tests.context.dependent.DependentContextTest:testContextIsActiveDuringBeanCreation Unable to resolve any Web Beans of class org.jboss.jsr299.tck.tests.context.dependent.SensitiveFox org.jboss.jsr299.tck.impl.OldSPIBridge.ensureUniqueBean(OldSPIBridge.java:56) at org.jboss.jsr299.tck.impl.OldSPIBridge.getInstanceByType(OldSPIBridge.java:41) at org.jboss.jsr299.tck.AbstractJSR299Test.getInstanceByType(AbstractJSR299Test.java:160) at org.jboss.jsr299.tck.tests.context.dependent.DependentContextTest.testContextIsActiveDuringBeanCreation(DependentContextTest.java:248) 44 lines not shown ---- org.jboss.jsr299.tck.tests.context.dependent.DependentContextTest:testContextIsActiveWhenInvokingProducerMethod Unable to resolve any Web Beans of class org.jboss.jsr299.tck.tests.context.dependent.Tarantula org.jboss.jsr299.tck.impl.OldSPIBridge.ensureUniqueBean(OldSPIBridge.java:56) at org.jboss.jsr299.tck.impl.OldSPIBridge.getInstanceByType(OldSPIBridge.java:41) at org.jboss.jsr299.tck.AbstractJSR299Test.getInstanceByType(AbstractJSR299Test.java:160) at org.jboss.jsr299.tck.tests.context.dependent.DependentContextTest.testContextIsActiveWhenInvokingProducerMethod(DependentContextTest.java:193) 43 lines not shown Lin On Thu, Sep 2, 2010 at 3:10 PM, Joseph Bergmark <[email protected]> wrote: > Just to double check I updated my sandbox and then ran "mvn clean install" > from the root, before running the TCK again. I'm still getting the same > results with 574 tests and 2 failures. > > It might be worth digging into the logs and trying to determine where things > are going wrong. The emailable-report.html > inside webbeans-tck/target/surefire-reports sometimes had some information > about the failure, and I believe it always has the failures first in the > section at the bottom. > > Sincerely, > > Joe > > On Thu, Sep 2, 2010 at 1:46 PM, Lin Sun <[email protected]> wrote: > >> Hi Joe >> >> Thanks for the pointer. I looked at your email closely and I think >> I've done all things you mentioned (sorry I forgot to mention them). >> >> The only extra thing I did was I had to add this - >> >> >> org.jboss.testharness.api.TestLauncher=org.jboss.testharness.impl.runner.servlet.ServletTestLauncher >> >> in the jboss-test-harness.properties file, otherwise, I'd get a build >> failure. >> >> There is a slight chance that things might have regressed in between >> the last time you ran it and the current trunk, but I could still have >> missed things obvious. >> >> Thanks >> >> Lin >> >> >> >> On Thu, Sep 2, 2010 at 11:40 AM, Joseph Bergmark <[email protected]> >> wrote: >> > 574 seems like the correct number for standalone, but your results do not >> > appear to match mine. I get back: >> > >> > Failed tests: >> > >> testBindingTypesAppliedToDisposalMethodParameters(org.jboss.jsr299.tck.tests.implementation.disposal.method.definition.DisposalMethodDefinitionTest) >> > >> testContextCreatesNewInstanceForInjection(org.jboss.jsr299.tck.tests.implementation.simple.lifecycle.SimpleBeanLifecycleTest) >> > >> > Tests run: 574, Failures: 2, Errors: 0, Skipped: 0 >> > >> > There are a couple steps I mentioned back in August that I needed to do, >> > that I still haven't updated the README with. I'll paste a link below to >> > that older dev mailing list e-mail. >> > >> http://mail-archives.apache.org/mod_mbox/openwebbeans-dev/201008.mbox/%[email protected]%3e >> > >> > Sincerely, >> > >> > Joe >> > >> > On Thu, Sep 2, 2010 at 11:05 AM, Lin Sun <[email protected]> wrote: >> > >> >> Hi! >> >> >> >> I am new to the list and I did some searches on the titled topic and >> >> was able to find the readme/TCK-RUNNING.txt. I was able to follow >> >> the instruction. >> >> >> >> I discovered that in order to run the tck standalone, I still need to >> >> setup tomcat.home and have the tomcat server running. Also, I have to >> >> start tomcat server with -ea to enable assertions as some tests seems >> >> to run as servlet and need the assertions to be enabled. >> >> >> >> My biggest prob right now is most of the tck in standalone failed for >> me. >> >> >> >> >> >> Tests run: 574, Failures: 524, Errors: 0, Skipped: 0 >> >> >> >> Does the total # of tests look right? The good thing is test did run >> >> instead of skipped but I am probably still missing something obvious >> >> here. I remember seeing a post that says that openwebbeans has >> >> passed all jsr299 tcks. >> >> >> >> Thanks. >> >> >> >> Lin >> >> >> > >> >
