|
From: Rob H. <ro...@ca...> - 2005-02-04 11:44:51
|
I tested this particular test on Windows XP and it runs in 2400 ms on my machine. Switching back to CGLIB 2.0.2 makes the test run in 2380 ms - so I guess there is no real difference. Does anyone have access to a Solaris workstation/server where they can execute this test manually? The interesting thing is that the test that is failing is inherited from CglibProxyTests and it seems to have passed on there assuming the tests are executed in order. Rob Darren Davison wrote: >1107477484 >FAILED > [junit] StopWatch '': running time (millis) = 32064 > [junit] [class org.springframework.aop.framework.OptimizedCglibProxyTeststestManyProxies: create 10000 proxies] took 32.064=100% > [junit] ------------- ---------------- --------------- > > [junit] Testcase: testDeclaredException took 0.126 sec > [junit] Testcase: testTargetCanGetInvocationEvenIfNoAdviceChain took 0 sec > [junit] Testcase: testExistingProxyChangesTarget took 0.006 sec > [junit] Testcase: testDynamicMethodPointcutThatAppliesStaticallyOnlyToSetters took 1.084 sec > [junit] Testcase: testStaticMethodPointcut took 0.845 sec > [junit] Testcase: testNullConfig took 0.001 sec > [junit] Testcase: testNoTarget took 0.001 sec > [junit] Testcase: testProtectedMethodInvocation took 0.311 sec > [junit] Testcase: testProxyCanBeClassNotInterface took 0.696 sec > [junit] Testcase: testCglibProxyingGivesMeaningfulExceptionIfAskedToProxyNonvisibleClass took 0.244 sec > [junit] Testcase: testMethodInvocationDuringConstructor took 0.307 sec > [junit] Testcase: testMultipleProxies took 1.364 sec > [junit] Testcase: testWithNoArgConstructor took 0.565 sec > [junit] Testcase: testUnadvisedProxyCreationWithCallDuringConstructor took 0.242 sec > [junit] Testcase: testExceptionHandling took 0.882 sec > [junit] Testcase: testNoInterceptorsAndNoTarget took 0.001 sec > [junit] Testcase: testValuesStick took 0.001 sec > [junit] Testcase: testManyProxies took 32.196 sec > [junit] FAILED > [junit] Proxy creation was too slow > [junit] junit.framework.AssertionFailedError: Proxy creation was too slow > [junit] at org.springframework.aop.framework.AbstractAopProxyTests.testManyProxies(AbstractAopProxyTests.java:148) > [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > > >This is an automated mail from one of the SF Compile Farm machines. >The machine name noted in the subject encountered a failure building >or running the Spring test suite. The last few lines of the output >were included for info. > >NB: No further mail will be sent from this machine until a >manual reset occurs on the cf-shell machine, although builds will >continue as scheduled. > >See http://springframework.sourceforge.net/test/ for further >information. > > >------------------------------------------------------- >This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting >Tool for open source databases. Create drag-&-drop reports. Save time >by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. >Download a FREE copy at http://www.intelliview.com/go/osdn_nl >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > |