Menu
▾
▴
springframework-developer
|
From: Darren D. <da...@sh...> - 2005-05-17 21:37:05
|
1116365809 FAILED 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. |
|
From: Darren D. <da...@sh...> - 2005-05-22 05:05:41
|
1116738336
FAILED
[junit] Testcase: testCannotCommitTransaction took 0,002 sec
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,043 sec
[junit] Testsuite: org.springframework.transaction.support.JtaTransactionManagerSerializationTests
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,043 sec
[junit] Testcase: testSerializable took 0,008 sec
[junit] 2005-05-22 05:54:25.455 java[29022] Warning: Font LucidaSans-TypewriterBold claims fixed-pitch with 0 max advance!
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 8,104 sec
[junit] Testsuite: org.springframework.ui.jasperreports.JasperReportsUtilsTests
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 8,104 sec
[junit] Testcase: testRenderAsCsvWithDataSource took 8,042 sec
[junit] Caused an ERROR
[junit] Unsupported major.minor version 49.0
[junit] java.lang.UnsupportedClassVersionError: Unsupported major.minor version 49.0
[junit] at java.lang.ClassLoader.defineClass0(Native Method)
[junit] at java.lang.ClassLoader.defineClass(ClassLoader.java:502)
[junit] at java.lang.ClassLoader.defineClass(ClassLoader.java:431)
[junit] at net.sf.jasperreports.engine.util.JRClassLoader.loadClass(JRClassLoader.java:208)
[junit] at net.sf.jasperreports.engine.util.JRClassLoader.loadClassFromBytes(JRClassLoader.java:123)
[junit] at net.sf.jasperreports.engine.design.JRAbstractJavaCompiler.loadCalculator(JRAbstractJavaCompiler.java:63)
[junit] at net.sf.jasperreports.engine.design.JRDefaultCompiler.loadCalculator(JRDefaultCompiler.java:156)
[junit] at net.sf.jasperreports.engine.fill.JRBaseFiller.<init>(JRBaseFiller.java:327)
[junit] at net.sf.jasperreports.engine.fill.JRVerticalFiller.<init>(JRVerticalFiller.java:83)
[junit] at net.sf.jasperreports.engine.fill.JRVerticalFiller.<init>(JRVerticalFiller.java:75)
[junit] at net.sf.jasperreports.engine.fill.JRFiller.fillReport(JRFiller.java:108)
[junit] at net.sf.jasperreports.engine.JasperFillManager.fillReport(JasperFillManager.java:429)
[junit] at org.springframework.ui.jasperreports.JasperReportsUtils.renderAsCsv(JasperReportsUtils.java:127)
[junit] at org.springframework.ui.jasperreports.JasperReportsUtilsTests.testRenderAsCsvWithDataSource(JasperReportsUtilsTests.java:55)
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.
|
|
From: Darren D. <da...@sh...> - 2005-05-24 04:34:26
|
1116909262
FAILED
[junit] ------------- Standard Output ---------------
[junit] StopWatch '': running time (millis) = 24381
[junit] [class org.springframework.aop.framework.OptimizedCglibProxyTests.testManyProxies: create 10000 proxies] took 24381=100%
[junit] ------------- ---------------- ---------------
[junit] Testcase: testDeclaredException took 0.24 sec
[junit] Testcase: testTargetCanGetInvocationEvenIfNoAdviceChain took 0 sec
[junit] Testcase: testExistingProxyChangesTarget took 0.005 sec
[junit] Testcase: testDynamicMethodPointcutThatAppliesStaticallyOnlyToSetters took 0.422 sec
[junit] Testcase: testStaticMethodPointcut took 0.397 sec
[junit] Testcase: testNullConfig took 0.011 sec
[junit] Testcase: testNoTarget took 0.001 sec
[junit] Testcase: testProtectedMethodInvocation took 0.012 sec
[junit] Testcase: testProxyCanBeClassNotInterface took 0.001 sec
[junit] Testcase: testCglibProxyingGivesMeaningfulExceptionIfAskedToProxyNonvisibleClass took 0.063 sec
[junit] Testcase: testMethodInvocationDuringConstructor took 0.36 sec
[junit] Testcase: testUnadvisedProxyCreationWithCallDuringConstructor took 0.002 sec
[junit] Testcase: testMultipleProxies took 0.561 sec
[junit] Testcase: testWithNoArgConstructor took 0.003 sec
[junit] Testcase: testProxyAProxy took 0.003 sec
[junit] Testcase: testExceptionHandling took 0.112 sec
[junit] Testcase: testWithDependencyChecking took 0.389 sec
[junit] Testcase: testNoInterceptorsAndNoTarget took 0.001 sec
[junit] Testcase: testValuesStick took 0.001 sec
[junit] Testcase: testManyProxies took 24.433 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:147)
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.
|
|
From: Darren D. <da...@sh...> - 2005-06-04 12:33:36
|
1117888381 FAILED 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. |
|
From: Darren D. <da...@sh...> - 2005-06-15 12:22:46
|
1118838157
FAILED
[junit] Testcase: testTwoProperties took 0.001 sec
[junit] Testcase: testHandlesEqualsInValue took 0 sec
[junit] Testcase: testHandlesEmptyProperty took 0.001 sec
[junit] Testcase: testHandlesEmptyPropertyWithoutEquals took 0 sec
[junit] Testcase: testIgnoresCommentLinesAndEmptyLines took 0.019 sec
[junit] Testcase: testIgnoresLeadingSpacesAndTabs took 0.001 sec
[junit] Testcase: testNull took 0 sec
[junit] Testcase: testEmptyString took 0 sec
[junit] Exception in thread "main" java.io.FileNotFoundException: /home/users/d/da/davison/checkouts/spring/target/ppc-osx2/test-reports/TEST-org.springframework.beans.support.PagedListHolderTests.xml (Operation not permitted)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.FormatterElement.createFormatter(FormatterElement.java:236)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.FormatterElement.createFormatter(FormatterElement.java:192)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.transferFormatters(JUnitTestRunner.java:586)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:670)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:546)
[junit] Caused by: java.io.FileNotFoundException: /home/users/d/da/davison/checkouts/spring/target/ppc-osx2/test-reports/TEST-org.springframework.beans.support.PagedListHolderTests.xml (Operation not permitted)
[junit] at java.io.FileOutputStream.open(Native Method)
[junit] at java.io.FileOutputStream.<init>(FileOutputStream.java:176)
[junit] at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.FormatterElement.createFormatter(FormatterElement.java:234)
[junit] ... 4 more
[junit] --- Nested Exception ---
[junit] java.io.FileNotFoundException: /home/users/d/da/davison/checkouts/spring/target/ppc-osx2/test-reports/TEST-org.springframework.beans.support.PagedListHolderTests.xml (Operation not permitted)
[junit] at java.io.FileOutputStream.open(Native Method)
[junit] at java.io.FileOutputStream.<init>(FileOutputStream.java:176)
[junit] at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.FormatterElement.createFormatter(FormatterElement.java:234)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.FormatterElement.createFormatter(FormatterElement.java:192)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.transferFormatters(JUnitTestRunner.java:586)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:670)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:546)
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.
|
|
From: Darren D. <da...@sh...> - 2005-06-24 04:55:44
|
1119588937
FAILED
[junit] ------------- Standard Output ---------------
[junit] StopWatch '': running time (millis) = 43229
[junit] [class org.springframework.aop.framework.OptimizedCglibProxyTests.testManyProxies: create 10000 proxies] took 43229=100%
[junit] ------------- ---------------- ---------------
[junit] Testcase: testDeclaredException took 0.681 sec
[junit] Testcase: testTargetCanGetInvocationEvenIfNoAdviceChain took 0 sec
[junit] Testcase: testExistingProxyChangesTarget took 0.004 sec
[junit] Testcase: testDynamicMethodPointcutThatAppliesStaticallyOnlyToSetters took 0.531 sec
[junit] Testcase: testStaticMethodPointcut took 0.611 sec
[junit] Testcase: testNullConfig took 0.001 sec
[junit] Testcase: testNoTarget took 0 sec
[junit] Testcase: testProtectedMethodInvocation took 0.001 sec
[junit] Testcase: testProxyCanBeClassNotInterface took 0.001 sec
[junit] Testcase: testCglibProxyingGivesMeaningfulExceptionIfAskedToProxyNonvisibleClass took 0.011 sec
[junit] Testcase: testMethodInvocationDuringConstructor took 0.104 sec
[junit] Testcase: testUnadvisedProxyCreationWithCallDuringConstructor took 0.002 sec
[junit] Testcase: testMultipleProxies took 0.216 sec
[junit] Testcase: testWithNoArgConstructor took 0.055 sec
[junit] Testcase: testProxyAProxy took 0.002 sec
[junit] Testcase: testExceptionHandling took 0.061 sec
[junit] Testcase: testWithDependencyChecking took 0.292 sec
[junit] Testcase: testNoInterceptorsAndNoTarget took 0.001 sec
[junit] Testcase: testValuesStick took 0 sec
[junit] Testcase: testManyProxies took 44.793 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:147)
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.
|
|
From: Darren D. <da...@sh...> - 2005-07-02 05:18:48
|
1120281521
FAILED
[junit] Testcase: testIsCompatibleWithThrowsClause took 0,001 sec
[junit] Testcase: testToObjectArray took 0,085 sec
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,072 sec
[junit] Testsuite: org.springframework.util.PathMatcherTests
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,072 sec
[junit] Testcase: testAntPathMatcher took 0,048 sec
[junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 1,28 sec
[junit] Testsuite: org.springframework.util.PropertiesPersisterTests
[junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 1,28 sec
[junit] Testcase: testPropertiesPersister took 0,595 sec
[junit] Testcase: testPropertiesPersisterWithWhitespace took 0,001 sec
[junit] Testcase: testPropertiesPersisterWithHeader took 0,002 sec
[junit] Testcase: testPropertiesPersisterWithEmptyValue took 0,002 sec
[junit] Testcase: testPropertiesPersisterWithReader took 0,006 sec
[junit] Testcase: testPropertiesPersisterWithReaderAndWhitespace took 0,001 sec
[junit] Testcase: testPropertiesPersisterWithReaderAndHeader took 0,64 sec
[junit] Testcase: testPropertiesPersisterWithReaderAndEmptyValue took 0 sec
[junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 3,039 sec
[junit] Testsuite: org.springframework.util.ResponseTimeMonitorTests
[junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 3,039 sec
[junit] Testcase: testGetAccessCount took 0,508 sec
[junit] Testcase: testGetUptime took 1,784 sec
[junit] FAILED
[junit] expected:<0.0> but was:<460.0>
[junit] junit.framework.AssertionFailedError: expected:<0.0> but was:<460.0>
[junit] at org.springframework.util.ResponseTimeMonitorTests.testGetUptime(ResponseTimeMonitorTests.java:48)
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.
|
|
From: Darren D. <da...@sh...> - 2005-07-18 22:28:22
|
1121725700 FAILED 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. |
|
From: Darren D. <da...@sh...> - 2005-07-24 04:33:08
|
1122179582 FAILED 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. |
|
From: Darren D. <da...@sh...> - 2005-08-04 04:58:49
|
1123131522
FAILED
[junit] Testcase: testTransactionRollbackWithAutoCommitFalse took 0,001 sec
[junit] Testcase: testTransactionRollbackWithAutoCommitTrueAndLazyConnection took 0,006 sec
[junit] Testcase: testTransactionRollbackWithAutoCommitFalseAndLazyConnection took 0,003 sec
[junit] Testcase: testTransactionRollbackWithAutoCommitTrueAndLazyConnectionAndCreateStatement took 0,001 sec
[junit] Testcase: testTransactionRollbackWithAutoCommitFalseAndLazyConnectionAndCreateStatement took 0,007 sec
[junit] Testcase: testTransactionRollbackOnly took 0,008 sec
[junit] Testcase: testParticipatingTransactionWithRollbackOnly took 0,016 sec
[junit] Testcase: testPropagationRequiresNewWithExistingTransaction took 0,065 sec
[junit] Testcase: testPropagationNotSupportedWithExistingTransaction took 0,228 sec
[junit] Testcase: testPropagationNeverWithExistingTransaction took 0,137 sec
[junit] Testcase: testTransactionWithIsolationAndReadOnly took 0,009 sec
[junit] Testcase: testTransactionWithLongTimeout took 7,444 sec
[junit] FAILED
[junit] Unexpected method call rollback():
[junit] rollback(): expected: 0, actual: 1
[junit] junit.framework.AssertionFailedError:
[junit] Unexpected method call rollback():
[junit] rollback(): expected: 0, actual: 1
[junit] at org.easymock.MockControl$4.invoke(MockControl.java:148)
[junit] at org.easymock.internal.ObjectMethodsFilter.invoke(ObjectMethodsFilter.java:44)
[junit] at $Proxy82.rollback(Unknown Source)
[junit] at org.springframework.jdbc.datasource.DataSourceTransactionManager.doRollback(DataSourceTransactionManager.java:238)
[junit] at org.springframework.transaction.support.AbstractPlatformTransactionManager.processRollback(AbstractPlatformTransactionManager.java:578)
[junit] at org.springframework.transaction.support.AbstractPlatformTransactionManager.rollback(AbstractPlatformTransactionManager.java:555)
[junit] at org.springframework.transaction.support.TransactionTemplate.rollbackOnException(TransactionTemplate.java:141)
[junit] at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:123)
[junit] at org.springframework.jdbc.datasource.DataSourceTransactionManagerTests.doTestTransactionWithTimeout(DataSourceTransactionManagerTests.java:620)
[junit] at org.springframework.jdbc.datasource.DataSourceTransactionManagerTests.testTransactionWithLongTimeout(DataSourceTransactionManagerTests.java:571)
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.
|
|
From: Darren D. <da...@sh...> - 2005-08-05 20:15:04
|
1123272900
FAILED
Buildfile: build.xml
clean:
compileattr:
[attribute-compiler] Generated attribute information for 1 classes. Ignored 0 classes.
buildmain:
[mkdir] Created dir: /home/users/d/da/davison/checkouts/spring/target/ppc-osx2/classes
[mkdir] Created dir: /home/users/d/da/davison/checkouts/spring/target/ppc-osx2/classes/META-INF
[javac] Compiling 1105 source files to /home/users/d/da/davison/checkouts/spring/target/ppc-osx2/classes
[javac] /home/users/d/da/davison/checkouts/spring/src/org/springframework/jmx/access/MBeanProxyFactoryBean.java:70: unreported exception java.io.IOException; must be caught or declared to be thrown
[javac] super.afterPropertiesSet();
[javac] ^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -deprecation for details.
[javac] 1 error
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.
|
|
From: Darren D. <da...@sh...> - 2005-08-10 20:14:31
|
1123704858 FAILED Buildfile: build.xml clean: [delete] Deleting directory /home/users/d/da/davison/checkouts/spring/target/ppc-osx2/classes [delete] Deleting directory /home/users/d/da/davison/checkouts/spring/target/ppc-osx2/test-classes [delete] Deleting directory /home/users/d/da/davison/checkouts/spring/target/ppc-osx2/mock-classes [delete] Deleting directory /home/users/d/da/davison/checkouts/spring/target/ppc-osx2/test-reports 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. |
|
From: Darren D. <da...@sh...> - 2005-08-19 13:31:20
|
1124458278
FAILED
[junit] at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213)
[junit] at java.io.BufferedWriter.flush(BufferedWriter.java:230)
[junit] at org.apache.tools.ant.util.DOMElementWriter.closeElement(DOMElementWriter.java:198)
[junit] at org.apache.tools.ant.util.DOMElementWriter.write(DOMElementWriter.java:132)
[junit] at org.apache.tools.ant.util.DOMElementWriter.write(DOMElementWriter.java:94)
[junit] at org.apache.tools.ant.util.DOMElementWriter.write(DOMElementWriter.java:94)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter.endTestSuite(XMLJUnitResultFormatter.java:137)
[junit] ... 4 more
[junit] --- Nested Exception ---
[junit] java.io.IOException: No such file or directory
[junit] at java.io.FileOutputStream.writeBytes(Native Method)
[junit] at java.io.FileOutputStream.write(FileOutputStream.java:257)
[junit] at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:334)
[junit] at sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder.java:402)
[junit] Testcase: testRenderAsXlsWithCollection took 8,001 sec
[junit] at sun.nio.cs.StreamEncoder$CharsetSE.implFlush(StreamEncoder.java:406)
[junit] Testcase: testRenderWithWriter took 5,182 sec
[junit] at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:150)
[junit] Testcase: testRenderWithOutputStream took 2,74 sec
[junit] at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213)
[junit] at java.io.BufferedWriter.flush(BufferedWriter.java:230)
[junit] at org.apache.tools.ant.util.DOMElementWriter.closeElement(DOMElementWriter.java:198)
[junit] at org.apache.tools.ant.util.DOMElementWriter.write(DOMElementWriter.java:132)
[junit] at org.apache.tools.ant.util.DOMElementWriter.write(DOMElementWriter.java:94)
[junit] at org.apache.tools.ant.util.DOMElementWriter.write(DOMElementWriter.java:94)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter.endTestSuite(XMLJUnitResultFormatter.java:137)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.fireEndTestSuite(JUnitTestRunner.java:449)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:322)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:672)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:546)
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.
|
|
From: Darren D. <da...@sh...> - 2005-08-20 04:19:11
|
1124511547 FAILED 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. |
|
From: Darren D. <da...@sh...> - 2005-08-23 20:43:30
|
1124829803 FAILED 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. |
|
From: Darren D. <da...@sh...> - 2005-08-31 14:20:28
|
1125498018
FAILED
[junit] Testcase: testRmiProxyFactoryBeanWithBusinessInterfaceAndConnectExceptionAndRefresh took 0,263 sec
[junit] Testcase: testRmiProxyFactoryBeanWithBusinessInterfaceAndConnectIOExceptionAndRefresh took 0,348 sec
[junit] Testcase: testRmiProxyFactoryBeanWithBusinessInterfaceAndUnknownHostExceptionAndRefresh took 0,154 sec
[junit] Testcase: testRmiProxyFactoryBeanWithBusinessInterfaceAndNoSuchObjectExceptionAndRefresh took 0,076 sec
[junit] Testcase: testRmiProxyFactoryBeanWithBusinessInterfaceAndStubNotFoundExceptionAndRefresh took 0,499 sec
[junit] Testcase: testRmiProxyFactoryBeanWithBusinessInterfaceAndMarshalExceptionAndRefresh took 0,171 sec
[junit] Testcase: testRmiProxyFactoryBeanWithBusinessInterfaceAndUnmarshalExceptionAndRefresh took 0,256 sec
[junit] Testcase: testRmiClientInterceptorRequiresUrl took 0,65 sec
[junit] Testcase: testRemoteInvocation took 0,254 sec
[junit] Testcase: testRmiInvokerWithSpecialLocalMethods took 2,023 sec
[junit] Tests run: 11, Failures: 1, Errors: 0, Time elapsed: 333,047 sec
[junit] Testsuite: org.springframework.scheduling.quartz.QuartzSupportTests
[junit] Tests run: 11, Failures: 1, Errors: 0, Time elapsed: 333,047 sec
[junit] Testcase: testSchedulerFactoryBean took 192,403 sec
[junit] Testcase: testSchedulerFactoryBeanWithExplicitJobDetail took 0,651 sec
[junit] Testcase: testSchedulerFactoryBeanWithListeners took 2,788 sec
[junit] Testcase: testSchedulerFactoryBeanWithPlainQuartzObjects took 0,275 sec
[junit] Testcase: testSchedulerFactoryBeanWithApplicationContext took 0,959 sec
[junit] Testcase: testJobDetailBeanWithApplicationContext took 0,002 sec
[junit] Testcase: testJobDetailBeanWithListenerNames took 0,003 sec
[junit] Testcase: testCronTriggerBeanWithListenerNames took 0,002 sec
[junit] Testcase: testSimpleTriggerBeanWithListenerNames took 0,001 sec
[junit] Testcase: testMultipleSchedulers took 90,257 sec
[junit] Testcase: testWithTwoAnonymousMethodInvokingJobDetailFactoryBeans took 35,429 sec
[junit] FAILED
[junit] doExport not called on exportService expected:<2> but was:<0>
[junit] junit.framework.AssertionFailedError: doExport not called on exportService expected:<2> but was:<0>
[junit] at org.springframework.scheduling.quartz.QuartzSupportTests.testWithTwoAnonymousMethodInvokingJobDetailFactoryBeans(QuartzSupportTests.java:456)
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.
|
|
From: Darren D. <da...@sh...> - 2005-09-02 04:33:16
|
1125635587 FAILED 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. |
|
From: Darren D. <da...@sh...> - 2005-09-27 12:18:01
|
1127823479
FAILED
[junit] Testsuite: org.springframework.core.enums.LabeledEnumTests
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0,071 sec
[junit] Testcase: testEquals took 0,026 sec
[junit] Testcase: testForCodeFound took 0,025 sec
[junit] Testcase: testDoesNotMatchWrongClass took 0,001 sec
[junit] Tests run: 15, Failures: 1, Errors: 0, Time elapsed: 0,424 sec
[junit] Testsuite: org.springframework.core.io.ResourceTests
[junit] Tests run: 15, Failures: 1, Errors: 0, Time elapsed: 0,424 sec
[junit] Testcase: testByteArrayResource took 0,006 sec
[junit] Testcase: testByteArrayResourceWithDescription took 0 sec
[junit] Testcase: testInputStreamResource took 0,006 sec
[junit] Testcase: testInputStreamResourceWithDescription took 0 sec
[junit] Testcase: testClassPathResource took 0,014 sec
[junit] Testcase: testClassPathResourceWithClassLoader took 0,01 sec
[junit] Testcase: testClassPathResourceWithClass took 0,01 sec
[junit] Testcase: testFileSystemResource took 0,002 sec
[junit] Testcase: testUrlResource took 0,002 sec
[junit] Testcase: testServletContextResource took 0,051 sec
[junit] Testcase: testClassPathResourceWithRelativePath took 0 sec
[junit] Testcase: testFileSystemResourceWithRelativePath took 0 sec
[junit] Testcase: testUrlResourceWithRelativePath took 0,001 sec
[junit] Testcase: testServletContextResourceWithRelativePath took 0 sec
[junit] Testcase: testNonFileResourceExists took 0,291 sec
[junit] FAILED
[junit] null
[junit] junit.framework.AssertionFailedError
[junit] at org.springframework.core.io.ResourceTests.testNonFileResourceExists(ResourceTests.java:151)
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.
|
|
From: Darren D. <da...@sh...> - 2005-10-10 04:34:23
|
1128918866 FAILED 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. |
|
From: Darren D. <da...@sh...> - 2005-10-21 20:38:28
|
1129927091
FAILED
[junit] ------------- ---------------- ---------------
[junit] Testcase: testDeclaredException took 0.722 sec
[junit] Testcase: testTargetCanGetInvocationEvenIfNoAdviceChain took 0 sec
[junit] Testcase: testExistingProxyChangesTarget took 0.048 sec
[junit] Testcase: testDynamicMethodPointcutThatAppliesStaticallyOnlyToSetters took 0.34 sec
[junit] Testcase: testStaticMethodPointcut took 0.684 sec
[junit] Testcase: testProxyIsBoundBeforeTargetSourceInvoked took 0.424 sec
[junit] Testcase: testNullConfig took 0 sec
[junit] Testcase: testNoTarget took 0.001 sec
[junit] Testcase: testProtectedMethodInvocation took 0.001 sec
[junit] Testcase: testProxyCanBeClassNotInterface took 0.013 sec
[junit] Testcase: testCglibProxyingGivesMeaningfulExceptionIfAskedToProxyNonvisibleClass took 0.013 sec
[junit] Testcase: testMethodInvocationDuringConstructor took 0.103 sec
[junit] Testcase: testUnadvisedProxyCreationWithCallDuringConstructor took 0.013 sec
[junit] Testcase: testMultipleProxies took 0.521 sec
[junit] Testcase: testWithNoArgConstructor took 0.014 sec
[junit] Testcase: testProxyAProxy took 0.019 sec
[junit] Testcase: testExceptionHandling took 0.269 sec
[junit] Testcase: testWithDependencyChecking took 0.356 sec
[junit] Testcase: testAddAdviceAtRuntime took 0.122 sec
[junit] Testcase: testProxyClassWithFinalMethods took 0.002 sec
[junit] Testcase: testNoInterceptorsAndNoTarget took 0 sec
[junit] Testcase: testValuesStick took 0 sec
[junit] Testcase: testManyProxies took 40.154 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:151)
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.
|
|
From: Darren D. <da...@sh...> - 2005-10-25 04:13:11
|
1130213587 FAILED 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. |
|
From: Darren D. <da...@sh...> - 2005-10-26 04:33:07
|
1130301180 FAILED 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. |
|
From: Will B. <wil...@ra...> - 2005-10-26 15:45:06
|
Is it possible to refresh the Spring MVC Dispatcher servlet's application context? How do you get access to it? Thanks, Will |
|
From: Dmitriy K. <dko...@ru...> - 2005-10-26 16:03:05
|
You could implement "ApplicationContextAware" container callback which will inject the instance of the current ApplicationContext that the bean is defined in. Then you could cast it to "ConfigurableApplicationContext" and call its "refresh" method. Regards, Dmitriy. Will Butler wrote: >Is it possible to refresh the Spring MVC Dispatcher servlet's application >context? How do you get access to it? > >Thanks, > >Will > > > >------------------------------------------------------- >This SF.Net email is sponsored by the JBoss Inc. >Get Certified Today * Register for a JBoss Training Course >Free Certification Exam for All Training Attendees Through End of 2005 >Visit http://www.jboss.com/services/certification for more information >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > > |
|
From: Will B. <wil...@ra...> - 2005-10-26 18:57:01
|
I would actually like to get access to the application context from outside of spring. For example, I would like to call a static method on some class to reset the servlet application context. - Will On 10/26/05 10:02 AM, "Dmitriy Kopylenko" <dko...@ru...> wrote: > You could implement "ApplicationContextAware" container callback which > will inject the instance of the current ApplicationContext that the bean > is defined in. Then you could cast it to > "ConfigurableApplicationContext" and call its "refresh" method. > > Regards, > Dmitriy. > > Will Butler wrote: > >> Is it possible to refresh the Spring MVC Dispatcher servlet's application >> context? How do you get access to it? >> >> Thanks, >> >> Will >> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by the JBoss Inc. >> Get Certified Today * Register for a JBoss Training Course >> Free Certification Exam for All Training Attendees Through End of 2005 >> Visit http://www.jboss.com/services/certification for more information >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the JBoss Inc. > Get Certified Today * Register for a JBoss Training Course > Free Certification Exam for All Training Attendees Through End of 2005 > Visit http://www.jboss.com/services/certification for more information > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer |
