Menu
▾
▴
springframework-developer — Spring Framework developers list
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
(55) |
Mar
(100) |
Apr
(203) |
May
(330) |
Jun
(190) |
Jul
(302) |
Aug
(323) |
Sep
(197) |
Oct
(245) |
Nov
(490) |
Dec
(330) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(194) |
Feb
(400) |
Mar
(416) |
Apr
(415) |
May
(359) |
Jun
(381) |
Jul
(491) |
Aug
(311) |
Sep
(291) |
Oct
(273) |
Nov
(355) |
Dec
(266) |
| 2005 |
Jan
(306) |
Feb
(303) |
Mar
(520) |
Apr
(346) |
May
(255) |
Jun
(221) |
Jul
(171) |
Aug
(247) |
Sep
(147) |
Oct
(125) |
Nov
(165) |
Dec
(65) |
| 2006 |
Jan
(90) |
Feb
(53) |
Mar
(121) |
Apr
(103) |
May
(113) |
Jun
(103) |
Jul
(104) |
Aug
(67) |
Sep
(78) |
Oct
(82) |
Nov
(78) |
Dec
(70) |
| 2007 |
Jan
(77) |
Feb
(76) |
Mar
(63) |
Apr
(30) |
May
(47) |
Jun
(41) |
Jul
(44) |
Aug
(44) |
Sep
(49) |
Oct
(33) |
Nov
(25) |
Dec
(21) |
| 2008 |
Jan
(45) |
Feb
(13) |
Mar
(15) |
Apr
(12) |
May
(9) |
Jun
(33) |
Jul
(30) |
Aug
(7) |
Sep
(20) |
Oct
(17) |
Nov
(20) |
Dec
(10) |
| 2009 |
Jan
(8) |
Feb
(5) |
Mar
(12) |
Apr
(17) |
May
(19) |
Jun
(97) |
Jul
(77) |
Aug
(33) |
Sep
(24) |
Oct
(41) |
Nov
(16) |
Dec
(32) |
| 2010 |
Jan
(24) |
Feb
(14) |
Mar
(50) |
Apr
(71) |
May
(70) |
Jun
(64) |
Jul
(45) |
Aug
(62) |
Sep
(32) |
Oct
(4) |
Nov
(12) |
Dec
(2) |
| 2011 |
Jan
(1) |
Feb
(3) |
Mar
(4) |
Apr
(3) |
May
(6) |
Jun
(1) |
Jul
(4) |
Aug
(3) |
Sep
(4) |
Oct
(6) |
Nov
(3) |
Dec
(3) |
| 2012 |
Jan
(4) |
Feb
(8) |
Mar
(6) |
Apr
(10) |
May
(2) |
Jun
(3) |
Jul
(11) |
Aug
(10) |
Sep
(4) |
Oct
|
Nov
(1) |
Dec
(1) |
| 2013 |
Jan
(4) |
Feb
(1) |
Mar
(9) |
Apr
(1) |
May
(8) |
Jun
(2) |
Jul
(5) |
Aug
(2) |
Sep
|
Oct
(3) |
Nov
(10) |
Dec
(8) |
| 2014 |
Jan
(3) |
Feb
(12) |
Mar
(9) |
Apr
(12) |
May
(2) |
Jun
|
Jul
(3) |
Aug
(1) |
Sep
(1) |
Oct
(4) |
Nov
|
Dec
(2) |
| 2015 |
Jan
(1) |
Feb
(3) |
Mar
(4) |
Apr
(9) |
May
(2) |
Jun
(2) |
Jul
|
Aug
(2) |
Sep
(7) |
Oct
(9) |
Nov
(7) |
Dec
(9) |
| 2016 |
Jan
(7) |
Feb
(5) |
Mar
(5) |
Apr
(5) |
May
(8) |
Jun
(4) |
Jul
(5) |
Aug
(4) |
Sep
(6) |
Oct
(7) |
Nov
(2) |
Dec
(3) |
| 2017 |
Jan
(7) |
Feb
(8) |
Mar
(7) |
Apr
(3) |
May
(4) |
Jun
(3) |
Jul
(5) |
Aug
(8) |
Sep
(4) |
Oct
(2) |
Nov
(3) |
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2019 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2021 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
(5) |
Sep
(2) |
Oct
|
Nov
|
Dec
(1) |
| 2026 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Andy D. <an...@ma...> - 2006-01-10 16:49:31
|
I've noticed that the dev list has died down considerably over the last few months (it contains mostly automated messages now). Has the mail list moved or a new one opened somewhere? Just making sure I didn't miss something... - Andy |
|
From: <al...@in...> - 2006-01-10 16:23:26
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20060110165432 |
|
From: <al...@in...> - 2006-01-10 15:29:40
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20060110161727 |
|
From: Alef A. <al...@in...> - 2006-01-10 15:19:56
|
I'm working on the builds at the moment (migrating the uploads to a different host) so there might be a couple of build failed reports in the next hour(s). regards, alef al...@in... wrote: > View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20060110153759 > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > -- Alef Arendsen Interface21 NL Spring Services from the Source http://www.interface21.com Spring Core Developer http://www.springframework.org Author, "Professional Java Development with the Spring Framework" (June 2005, with Rod Johnson, Juergen Hoeller, Colin Sampaleanu and Thomas Risberg) http://www.amazon.com/exec/obidos/ASIN/0764574833/ Interface21 NL B.V. Donker Curtiusstraat 7-400c 1051JL Amsterdam Phone: 020 486 20 36 Fax: 084 837 00 00 Mail: al...@in... Skype: aarendsen ************************************ DISCLAIMER ********************* This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. ********************************************************************* |
|
From: Alef A. <al...@in...> - 2006-01-10 15:19:23
|
Thanks Darren, it's something i'd like to take up in the coming weeks, so I'll certainly think about your offer! regards, alef da...@da... wrote: > On Tue, Jan 10, 2006 at 02:27:07AM +0100, Alef Arendsen wrote: > >> On the subject of automatic building, it seems the builds running at >> SF.net fail quite often (if not always). I haven't looked at all the >> error messages, but some come from binding errors, some I can't seem to >> find the error message for. Darren, are x86-linux and sparc-solaris the >> only platforms the builds are running on, or is it an issue related to >> those platforms only? >> > > they do fail a lot, but certainly not always. You can track their progress > at http://springframework.sourceforge.net/test/ and the page also shows > which platforms the builds are occurring on. Remember too, that the SF > machines are continuously building and running the test suite, so they show > up more intra-day errors that may not be caught by the nightly build. Often > when one or more fail during the day, it's confirmed with a similar failed > build messsage from your nightly build too - but I don't know if it's always > for the same reasons. > > The SF machines are overloaded and underspec'ed, which accounts for some of > the errors (esp. "Proxy creation too slow" and some of the ones with no > stack traces or error messages). I have offered, on behalf of UPCO, to host > a proper continuous build environment on dedicated hardware for Spring. The > intention was to use one Linux and one Windows machine to do a similar job > to the SF compile farm stuff I run, but based on Luntbuild instead. Had no > response on this.. probably slipped under the radar as I sent it to Rod and > Juergen early Dec. (preparing for TSE and JavaPolis). So, if it's > something you guys think the project would benefit from (I do!) the offer's > still open :) > > Cheers, > -- Alef Arendsen Interface21 NL Spring Services from the Source http://www.interface21.com Spring Core Developer http://www.springframework.org Author, "Professional Java Development with the Spring Framework" (June 2005, with Rod Johnson, Juergen Hoeller, Colin Sampaleanu and Thomas Risberg) http://www.amazon.com/exec/obidos/ASIN/0764574833/ Interface21 NL B.V. Donker Curtiusstraat 7-400c 1051JL Amsterdam Phone: 020 486 20 36 Fax: 084 837 00 00 Mail: al...@in... Skype: aarendsen ************************************ DISCLAIMER ********************* This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. ********************************************************************* |
|
From: <al...@in...> - 2006-01-10 14:51:02
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20060110153759 |
|
From: <da...@da...> - 2006-01-10 11:46:37
|
On Tue, Jan 10, 2006 at 02:27:07AM +0100, Alef Arendsen wrote: > On the subject of automatic building, it seems the builds running at=20 > SF.net fail quite often (if not always). I haven't looked at all the=20 > error messages, but some come from binding errors, some I can't seem to= =20 > find the error message for. Darren, are x86-linux and sparc-solaris the= =20 > only platforms the builds are running on, or is it an issue related to=20 > those platforms only? they do fail a lot, but certainly not always. You can track their progress at http://springframework.sourceforge.net/test/ and the page also shows which platforms the builds are occurring on. Remember too, that the SF machines are continuously building and running the test suite, so they show up more intra-day errors that may not be caught by the nightly build. Often when one or more fail during the day, it's confirmed with a similar failed build messsage from your nightly build too - but I don't know if it's always for the same reasons. The SF machines are overloaded and underspec'ed, which accounts for some of the errors (esp. "Proxy creation too slow" and some of the ones with no stack traces or error messages). I have offered, on behalf of UPCO, to host a proper continuous build environment on dedicated hardware for Spring. The intention was to use one Linux and one Windows machine to do a similar job to the SF compile farm stuff I run, but based on Luntbuild instead. Had no response on this.. probably slipped under the radar as I sent it to Rod and Juergen early Dec. (preparing for TSE and JavaPolis). So, if it's something you guys think the project would benefit from (I do!) the offer's still open :) Cheers, --=20 Darren Davison Public Key: 0xDD356B0D |
|
From: Alef A. <al...@in...> - 2006-01-10 01:28:08
|
Thanks for looking into this Thomas. It's been bothering me for some time, but due to holidays I couldn't get to it... On the subject of automatic building, it seems the builds running at SF.net fail quite often (if not always). I haven't looked at all the error messages, but some come from binding errors, some I can't seem to find the error message for. Darren, are x86-linux and sparc-solaris the only platforms the builds are running on, or is it an issue related to those platforms only? regards, Alef Thomas Risberg wrote: > I've seen quite a few of the following errors lately: > Unit Test Error Details: (1) > Test: testRegisterWithMBeanServer > Class: org.springframework.jmx.support.ConnectorServerFactoryBeanTests > Type: java.net.BindException > Message: Address already in use > java.net.BindException: Address already in use > at java.net.PlainSocketImpl.socketBind(Native Method) > at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359) > at java.net.ServerSocket.bind(ServerSocket.java:319) > at > com.sun.jmx.remote.socket.SocketConnectionServer.start(SocketConnectionServer.java:128) > at > com.sun.jmx.remote.generic.SynchroMessageConnectionServerImpl.start(SynchroMessageConnectionServerImpl.java:39) > at > javax.management.remote.generic.GenericConnectorServer.start(GenericConnectorServer.java:235) > at > org.springframework.jmx.support.ConnectorServerFactoryBean.afterPropertiesSet(ConnectorServerFactoryBean.java:167) > at > org.springframework.jmx.support.ConnectorServerFactoryBeanTests.testRegisterWithMBeanServer(ConnectorServerFactoryBeanTests.java:78) > > > > Since I could reproduce this on my Linux machine I played around with > some potential fixes. Looks like a timing issue so I added a brief > sleep at the beginning of the failing test methods. Seems to take > care of it but occasionally I see the following warnings: > > > tests: > [junit] Running > org.springframework.jmx.support.ConnectorServerFactoryBeanTests > [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.921 sec > [junit] Testsuite: > org.springframework.jmx.support.ConnectorServerFactoryBeanTests > [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.921 sec > [junit] ------------- Standard Error ----------------- > [junit] Jan 7, 2006 5:30:22 PM ClientCommunicatorAdmin restart > [junit] WARNING: Failed to restart: java.net.ConnectException: > Connection refused > [junit] Jan 7, 2006 5:30:22 PM ClientCommunicatorAdmin restart > [junit] WARNING: Failed to restart: java.net.ConnectException: > Connection refused > [junit] ------------- ---------------- --------------- > > [junit] Testcase: testStartupWithLocatedServer took 0.429 sec > [junit] Testcase: testStartupWithSuppliedServer took 0.029 sec > [junit] Testcase: testRegisterWithMBeanServer took 0.013 sec > [junit] Testcase: testNoRegisterWithMBeanServer took 0.002 sec > > Not sure if this indicates a problem or not - it does not show up all > the time. > > > I've committed my change, let's see how the automated tests respond. > > > Thomas > > > > > On Jan 7, 2006, at 5:38 AM, Darren Davison wrote: > >> 1136630281 >> FAILED >> >> [junit] Testcase: testNaming took 0,005 sec >> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,014 sec >> [junit] Testsuite: >> org.springframework.jmx.export.naming.PropertiesFileNamingStrategyTests >> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,014 sec >> >> [junit] Testcase: testNaming took 0,003 sec >> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,012 sec >> [junit] Testsuite: >> org.springframework.jmx.export.naming.PropertiesNamingStrategyTests >> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,012 sec >> >> [junit] Testcase: testNaming took 0 sec >> [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 0,059 sec >> [junit] Testsuite: >> org.springframework.jmx.support.ConnectorServerFactoryBeanTests >> [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 0,059 sec >> >> [junit] Testcase: testStartupWithLocatedServer took 0,031 sec >> [junit] Testcase: testStartupWithSuppliedServer took 0,01 sec >> [junit] Caused an ERROR >> [junit] Address already in use >> [junit] java.net.BindException: Address already in use >> [junit] at java.net.PlainSocketImpl.socketBind(Native Method) >> [junit] at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331) >> [junit] at java.net.ServerSocket.bind(ServerSocket.java:318) >> [junit] at >> com.sun.jmx.remote.socket.SocketConnectionServer.start(SocketConnectionServer.java:128) >> [junit] at >> com.sun.jmx.remote.generic.SynchroMessageConnectionServerImpl.start(SynchroMessageConnectionServerImpl.java:39) >> [junit] at >> javax.management.remote.generic.GenericConnectorServer.start(GenericConnectorServer.java:235) >> [junit] at >> org.springframework.jmx.support.ConnectorServerFactoryBean.afterPropertiesSet(ConnectorServerFactoryBean.java:167) >> [junit] at >> org.springframework.jmx.support.ConnectorServerFactoryBeanTests.testStartupWithSuppliedServer(ConnectorServerFactoryBeanTests.java:65) >> >> Last CVS updates prior to this build were: >> 1136628781 >> ? ? >> ? junit423465713.properties >> ? junittestcases2136842450.properties >> ? sandbox/src/org/springframework/core/closure/ElementGenerator.java >> ? >> sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java >> ? >> sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java >> ? sandbox/src/org/springframework/core/closure/support/IfBlock.java >> ? sandbox/src/org/springframework/jms/listener >> ? >> test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml >> C >> test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml >> >> 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 >> successful build occurs on the machine in question. >> >> See http://springframework.sourceforge.net/test/ for further >> information. >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. Do you grep through >> log files >> for problems? Stop! Download the new AJAX search engine that makes >> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click >> <http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click> >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> <mailto:Spr...@li...> >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> > -- Alef Arendsen Interface21 NL Spring Services from the Source http://www.interface21.com Spring Core Developer http://www.springframework.org Author, "Professional Java Development with the Spring Framework" (June 2005, with Rod Johnson, Juergen Hoeller, Colin Sampaleanu and Thomas Risberg) http://www.amazon.com/exec/obidos/ASIN/0764574833/ Interface21 NL B.V. Donker Curtiusstraat 7-400c 1051JL Amsterdam Phone: 020 486 20 36 Fax: 084 837 00 00 Mail: al...@in... Skype: aarendsen ************************************ DISCLAIMER ********************* This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. ********************************************************************* |
|
From: <al...@in...> - 2006-01-09 23:21:19
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20060110001709 |
|
From: Darren D. <da...@sh...> - 2006-01-09 05:53:29
|
1136785695
FAILED
[junit] Testcase: testAutowireWithDefault took 0.082 sec
[junit] Testcase: testAutowireByConstructor took 0.096 sec
[junit] Testcase: testAutowireByConstructorWithSimpleValues took 0.133 sec
[junit] Testcase: testConstructorArgResolution took 0.183 sec
[junit] Testcase: testConstructorArgWithSingleMatch took 0.263 sec
[junit] Testcase: testThrowsExceptionOnTooManyArguments took 0.123 sec
[junit] Testcase: testThrowsExceptionOnAmbiguousResolution took 0.106 sec
[junit] Testcase: testFactoryBeanDefinedAsPrototype took 0.071 sec
[junit] Testcase: testDependsOn took 0.309 sec
[junit] Testcase: testDependsOnInInnerBean took 0.145 sec
[junit] Testcase: testDependenciesThroughConstructorArguments took 0.058 sec
[junit] Testcase: testDependenciesThroughConstructorArgumentAutowiring took 0.228 sec
[junit] Testcase: testDependenciesThroughConstructorArgumentsInInnerBean took 0.084 sec
[junit] Testcase: testDependenciesThroughProperties took 0.069 sec
[junit] Testcase: testDependenciesThroughPropertiesWithInTheMiddle took 0.216 sec
[junit] Testcase: testDependenciesThroughPropertyAutowiringByName took 0.057 sec
[junit] Testcase: testDependenciesThroughPropertyAutowiringByType took 0.056 sec
[junit] Testcase: testDependenciesThroughPropertiesInInnerBean took 0.048 sec
[junit] Testcase: testClassNotFoundWithDefault took 0.047 sec
[junit] Testcase: testClassNotFoundWithNoBeanClassLoader took 0.046 sec
[junit] Testcase: testResourceAndInputStream took 0.365 sec
[junit] Testcase: testClassPathResourceWithImport took 0.304 sec
[junit] Testcase: testUrlResourceWithImport took 0.1 sec
[junit] Testcase: testFileSystemResourceWithImport took 0.094 sec
[junit] Testcase: testLookupOverrideMethodsWithSetterInjection took 2.006 sec
[junit] FAILED
[junit] null
[junit] junit.framework.AssertionFailedError
[junit] at org.springframework.beans.factory.xml.XmlBeanFactoryTests.testLookupOverrideMethodsWithSetterInjection(XmlBeanFactoryTests.java:908)
Last CVS updates prior to this build were:
1136783582
? ?
? junit423465713.properties
? junittestcases2136842450.properties
? sandbox/src/org/springframework/core/closure/ElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java
? sandbox/src/org/springframework/core/closure/support/IfBlock.java
? sandbox/src/org/springframework/jms/listener
? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
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
successful build occurs on the machine in question.
See http://springframework.sourceforge.net/test/ for further
information.
|
|
From: Darren D. <da...@sh...> - 2006-01-09 02:38:12
|
1136773981 FAILED Last CVS updates prior to this build were: 1136772781 ? ? ? junit423465713.properties ? junittestcases2136842450.properties ? sandbox/src/org/springframework/core/closure/ElementGenerator.java ? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java ? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java ? sandbox/src/org/springframework/core/closure/support/IfBlock.java ? sandbox/src/org/springframework/jms/listener ? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml 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 successful build occurs on the machine in question. See http://springframework.sourceforge.net/test/ for further information. |
|
From: Darren D. <da...@sh...> - 2006-01-08 19:52:48
|
1136749654
FAILED
[junit] Testcase: testAutowireWithDefault took 0.06 sec
[junit] Testcase: testAutowireByConstructor took 0.095 sec
[junit] Testcase: testAutowireByConstructorWithSimpleValues took 0.093 sec
[junit] Testcase: testConstructorArgResolution took 0.213 sec
[junit] Testcase: testConstructorArgWithSingleMatch took 0.207 sec
[junit] Testcase: testThrowsExceptionOnTooManyArguments took 0.074 sec
[junit] Testcase: testThrowsExceptionOnAmbiguousResolution took 0.071 sec
[junit] Testcase: testFactoryBeanDefinedAsPrototype took 0.058 sec
[junit] Testcase: testDependsOn took 0.396 sec
[junit] Testcase: testDependsOnInInnerBean took 0.196 sec
[junit] Testcase: testDependenciesThroughConstructorArguments took 0.056 sec
[junit] Testcase: testDependenciesThroughConstructorArgumentAutowiring took 0.062 sec
[junit] Testcase: testDependenciesThroughConstructorArgumentsInInnerBean took 0.051 sec
[junit] Testcase: testDependenciesThroughProperties took 0.202 sec
[junit] Testcase: testDependenciesThroughPropertiesWithInTheMiddle took 0.213 sec
[junit] Testcase: testDependenciesThroughPropertyAutowiringByName took 0.045 sec
[junit] Testcase: testDependenciesThroughPropertyAutowiringByType took 0.27 sec
[junit] Testcase: testDependenciesThroughPropertiesInInnerBean took 0.047 sec
[junit] Testcase: testClassNotFoundWithDefault took 0.058 sec
[junit] Testcase: testClassNotFoundWithNoBeanClassLoader took 0.051 sec
[junit] Testcase: testResourceAndInputStream took 0.461 sec
[junit] Testcase: testClassPathResourceWithImport took 0.09 sec
[junit] Testcase: testUrlResourceWithImport took 0.157 sec
[junit] Testcase: testFileSystemResourceWithImport took 0.095 sec
[junit] Testcase: testLookupOverrideMethodsWithSetterInjection took 2.151 sec
[junit] FAILED
[junit] null
[junit] junit.framework.AssertionFailedError
[junit] at org.springframework.beans.factory.xml.XmlBeanFactoryTests.testLookupOverrideMethodsWithSetterInjection(XmlBeanFactoryTests.java:908)
Last CVS updates prior to this build were:
1136747581
? ?
? junit423465713.properties
? junittestcases2136842450.properties
? sandbox/src/org/springframework/core/closure/ElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java
? sandbox/src/org/springframework/core/closure/support/IfBlock.java
? sandbox/src/org/springframework/jms/listener
? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
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
successful build occurs on the machine in question.
See http://springframework.sourceforge.net/test/ for further
information.
|
|
From: Darren D. <da...@sh...> - 2006-01-08 17:51:08
|
1136742356
FAILED
[junit] Testcase: testProxiedUserInterfacesWithNoInterface took 0.008 sec
[junit] Tests run: 17, Failures: 1, Errors: 0, Time elapsed: 42.364 sec
[junit] Testsuite: org.springframework.aop.framework.CglibProxyTests
[junit] Tests run: 17, Failures: 1, Errors: 0, Time elapsed: 42.364 sec
[junit] ------------- Standard Output ---------------
[junit] StopWatch '': running time (millis) = 33806; [class org.springframework.aop.framework.CglibProxyTests.testManyProxies: create 10000 proxies] took 33806 = 100%
[junit] ------------- ---------------- ---------------
[junit] Testcase: testNullConfig took 0.001 sec
[junit] Testcase: testNoTarget took 0.005 sec
[junit] Testcase: testProtectedMethodInvocation took 0.536 sec
[junit] Testcase: testProxyCanBeClassNotInterface took 1.139 sec
[junit] Testcase: testCglibProxyingGivesMeaningfulExceptionIfAskedToProxyNonvisibleClass took 0.028 sec
[junit] Testcase: testMethodInvocationDuringConstructor took 0.326 sec
[junit] Testcase: testUnadvisedProxyCreationWithCallDuringConstructor took 0.528 sec
[junit] Testcase: testMultipleProxies took 1.379 sec
[junit] Testcase: testWithNoArgConstructor took 0.345 sec
[junit] Testcase: testProxyAProxy took 0.961 sec
[junit] Testcase: testExceptionHandling took 0.409 sec
[junit] Testcase: testWithDependencyChecking took 1.287 sec
[junit] Testcase: testAddAdviceAtRuntime took 0.723 sec
[junit] Testcase: testProxyClassWithFinalMethods took 0.534 sec
[junit] Testcase: testNoInterceptorsAndNoTarget took 0.001 sec
[junit] Testcase: testValuesStick took 0.045 sec
[junit] Testcase: testManyProxies took 33.829 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:153)
Last CVS updates prior to this build were:
1136740381
? ?
? junit423465713.properties
? junittestcases2136842450.properties
? sandbox/src/org/springframework/core/closure/ElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java
? sandbox/src/org/springframework/core/closure/support/IfBlock.java
? sandbox/src/org/springframework/jms/listener
? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
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
successful build occurs on the machine in question.
See http://springframework.sourceforge.net/test/ for further
information.
|
|
From: <al...@in...> - 2006-01-07 23:35:54
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20060108001618Lbuild.392 |
|
From: Thomas R. <tho...@tr...> - 2006-01-07 22:38:20
|
I've seen quite a few of the following errors lately:
Unit Test Error Details: (1)
Test: testRegisterWithMBeanServer
Class: org.springframework.jmx.support.ConnectorServerFactoryBeanTests
Type: java.net.BindException
Message: Address already in use
java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
at java.net.ServerSocket.bind(ServerSocket.java:319)
at com.sun.jmx.remote.socket.SocketConnectionServer.start
(SocketConnectionServer.java:128)
at
com.sun.jmx.remote.generic.SynchroMessageConnectionServerImpl.start
(SynchroMessageConnectionServerImpl.java:39)
at javax.management.remote.generic.GenericConnectorServer.start
(GenericConnectorServer.java:235)
at
org.springframework.jmx.support.ConnectorServerFactoryBean.afterProperti
esSet(ConnectorServerFactoryBean.java:167)
at
org.springframework.jmx.support.ConnectorServerFactoryBeanTests.testRegi
sterWithMBeanServer(ConnectorServerFactoryBeanTests.java:78)
Since I could reproduce this on my Linux machine I played around with
some potential fixes. Looks like a timing issue so I added a brief
sleep at the beginning of the failing test methods. Seems to take
care of it but occasionally I see the following warnings:
tests:
[junit] Running
org.springframework.jmx.support.ConnectorServerFactoryBeanTests
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed:
0.921 sec
[junit] Testsuite:
org.springframework.jmx.support.ConnectorServerFactoryBeanTests
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed:
0.921 sec
[junit] ------------- Standard Error -----------------
[junit] Jan 7, 2006 5:30:22 PM ClientCommunicatorAdmin restart
[junit] WARNING: Failed to restart: java.net.ConnectException:
Connection refused
[junit] Jan 7, 2006 5:30:22 PM ClientCommunicatorAdmin restart
[junit] WARNING: Failed to restart: java.net.ConnectException:
Connection refused
[junit] ------------- ---------------- ---------------
[junit] Testcase: testStartupWithLocatedServer took 0.429 sec
[junit] Testcase: testStartupWithSuppliedServer took 0.029 sec
[junit] Testcase: testRegisterWithMBeanServer took 0.013 sec
[junit] Testcase: testNoRegisterWithMBeanServer took 0.002 sec
Not sure if this indicates a problem or not - it does not show up all
the time.
I've committed my change, let's see how the automated tests respond.
Thomas
On Jan 7, 2006, at 5:38 AM, Darren Davison wrote:
> 1136630281
> FAILED
>
> [junit] Testcase: testNaming took 0,005 sec
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed:
> 0,014 sec
> [junit] Testsuite:
> org.springframework.jmx.export.naming.PropertiesFileNamingStrategyTest
> s
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed:
> 0,014 sec
>
> [junit] Testcase: testNaming took 0,003 sec
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed:
> 0,012 sec
> [junit] Testsuite:
> org.springframework.jmx.export.naming.PropertiesNamingStrategyTests
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed:
> 0,012 sec
>
> [junit] Testcase: testNaming took 0 sec
> [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed:
> 0,059 sec
> [junit] Testsuite:
> org.springframework.jmx.support.ConnectorServerFactoryBeanTests
> [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed:
> 0,059 sec
>
> [junit] Testcase: testStartupWithLocatedServer took 0,031 sec
> [junit] Testcase: testStartupWithSuppliedServer took 0,01 sec
> [junit] Caused an ERROR
> [junit] Address already in use
> [junit] java.net.BindException: Address already in use
> [junit] at java.net.PlainSocketImpl.socketBind(Native Method)
> [junit] at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:
> 331)
> [junit] at java.net.ServerSocket.bind(ServerSocket.java:318)
> [junit] at
> com.sun.jmx.remote.socket.SocketConnectionServer.start
> (SocketConnectionServer.java:128)
> [junit] at
> com.sun.jmx.remote.generic.SynchroMessageConnectionServerImpl.start
> (SynchroMessageConnectionServerImpl.java:39)
> [junit] at
> javax.management.remote.generic.GenericConnectorServer.start
> (GenericConnectorServer.java:235)
> [junit] at
> org.springframework.jmx.support.ConnectorServerFactoryBean.afterProper
> tiesSet(ConnectorServerFactoryBean.java:167)
> [junit] at
> org.springframework.jmx.support.ConnectorServerFactoryBeanTests.testSt
> artupWithSuppliedServer(ConnectorServerFactoryBeanTests.java:65)
>
> Last CVS updates prior to this build were:
> 1136628781
> ? ?
> ? junit423465713.properties
> ? junittestcases2136842450.properties
> ? sandbox/src/org/springframework/core/closure/ElementGenerator.java
> ? sandbox/src/org/springframework/core/closure/support/
> AbstractElementGenerator.java
> ? sandbox/src/org/springframework/core/closure/support/
> AbstractElementGeneratorWorkflow.java
> ? sandbox/src/org/springframework/core/closure/support/IfBlock.java
> ? sandbox/src/org/springframework/jms/listener
> ? test/org/springframework/beans/factory/xml/dependencies-prop-
> inTheMiddle.xml
> C test/org/springframework/beans/factory/xml/dependencies-prop-
> inTheMiddle.xml
>
> 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
> successful build occurs on the machine in question.
>
> See http://springframework.sourceforge.net/test/ for further
> information.
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through
> log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD
> SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
|
|
From: jeano <jjv...@je...> - 2006-01-07 19:00:11
|
For the last 6 months, I have been teaching myself Spring. I have a variety of web projects that all benefit from a framework like this.=20 I'm impressed with everything, save one piece - the IoC/dependency-injection component. During my day job, I use the Nucleus component of the ATG Dynamo framework regularly. It's the best thing since sliced bread. My first exposure to web apps was with the ATG framework ,4 years ago. Most of the ATG framework is dated and is vastly improved upon with various Open Source tools. However the Nucleus component is still impressive. It makes configuring large-scale applications a cinch. Honestly, I don't know how Spring users can live without it. For those of you who still need more background, I thought this thread was interesting. http://forum.springframework.org/showthread.php?t=3D16610 My question is this: Are there any plans to incorporate a Nucleus like component into Spring? If so, has development started on such a component? If not, I may start to do the development on my own and try to sell benefits to those in charge. I just don't want to reinvent the wheel. Thanks. -jean |
|
From: Darren D. <da...@sh...> - 2006-01-07 10:43:02
|
1136630281
FAILED
[junit] Testcase: testNaming took 0,005 sec
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,014 sec
[junit] Testsuite: org.springframework.jmx.export.naming.PropertiesFileNamingStrategyTests
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,014 sec
[junit] Testcase: testNaming took 0,003 sec
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,012 sec
[junit] Testsuite: org.springframework.jmx.export.naming.PropertiesNamingStrategyTests
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,012 sec
[junit] Testcase: testNaming took 0 sec
[junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 0,059 sec
[junit] Testsuite: org.springframework.jmx.support.ConnectorServerFactoryBeanTests
[junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 0,059 sec
[junit] Testcase: testStartupWithLocatedServer took 0,031 sec
[junit] Testcase: testStartupWithSuppliedServer took 0,01 sec
[junit] Caused an ERROR
[junit] Address already in use
[junit] java.net.BindException: Address already in use
[junit] at java.net.PlainSocketImpl.socketBind(Native Method)
[junit] at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
[junit] at java.net.ServerSocket.bind(ServerSocket.java:318)
[junit] at com.sun.jmx.remote.socket.SocketConnectionServer.start(SocketConnectionServer.java:128)
[junit] at com.sun.jmx.remote.generic.SynchroMessageConnectionServerImpl.start(SynchroMessageConnectionServerImpl.java:39)
[junit] at javax.management.remote.generic.GenericConnectorServer.start(GenericConnectorServer.java:235)
[junit] at org.springframework.jmx.support.ConnectorServerFactoryBean.afterPropertiesSet(ConnectorServerFactoryBean.java:167)
[junit] at org.springframework.jmx.support.ConnectorServerFactoryBeanTests.testStartupWithSuppliedServer(ConnectorServerFactoryBeanTests.java:65)
Last CVS updates prior to this build were:
1136628781
? ?
? junit423465713.properties
? junittestcases2136842450.properties
? sandbox/src/org/springframework/core/closure/ElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java
? sandbox/src/org/springframework/core/closure/support/IfBlock.java
? sandbox/src/org/springframework/jms/listener
? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
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
successful build occurs on the machine in question.
See http://springframework.sourceforge.net/test/ for further
information.
|
|
From: Darren D. <da...@sh...> - 2006-01-07 09:47:54
|
1136626971
FAILED
[junit] Testcase: testProxiedUserInterfacesWithNoInterface took 0.009 sec
[junit] Tests run: 17, Failures: 1, Errors: 0, Time elapsed: 34.372 sec
[junit] Testsuite: org.springframework.aop.framework.CglibProxyTests
[junit] Tests run: 17, Failures: 1, Errors: 0, Time elapsed: 34.372 sec
[junit] ------------- Standard Output ---------------
[junit] StopWatch '': running time (millis) = 26958; [class org.springframework.aop.framework.CglibProxyTests.testManyProxies: create 10000 proxies] took 26958 = 100%
[junit] ------------- ---------------- ---------------
[junit] Testcase: testNullConfig took 0.001 sec
[junit] Testcase: testNoTarget took 0.15 sec
[junit] Testcase: testProtectedMethodInvocation took 0.356 sec
[junit] Testcase: testProxyCanBeClassNotInterface took 0.809 sec
[junit] Testcase: testCglibProxyingGivesMeaningfulExceptionIfAskedToProxyNonvisibleClass took 0.027 sec
[junit] Testcase: testMethodInvocationDuringConstructor took 0.464 sec
[junit] Testcase: testUnadvisedProxyCreationWithCallDuringConstructor took 0.437 sec
[junit] Testcase: testMultipleProxies took 0.789 sec
[junit] Testcase: testWithNoArgConstructor took 0.272 sec
[junit] Testcase: testProxyAProxy took 1.451 sec
[junit] Testcase: testExceptionHandling took 0.27 sec
[junit] Testcase: testWithDependencyChecking took 1.253 sec
[junit] Testcase: testAddAdviceAtRuntime took 0.538 sec
[junit] Testcase: testProxyClassWithFinalMethods took 0.51 sec
[junit] Testcase: testNoInterceptorsAndNoTarget took 0 sec
[junit] Testcase: testValuesStick took 0.009 sec
[junit] Testcase: testManyProxies took 26.992 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:153)
Last CVS updates prior to this build were:
1136625181
? ?
? junit423465713.properties
? junittestcases2136842450.properties
? sandbox/src/org/springframework/core/closure/ElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java
? sandbox/src/org/springframework/core/closure/support/IfBlock.java
? sandbox/src/org/springframework/jms/listener
? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
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
successful build occurs on the machine in question.
See http://springframework.sourceforge.net/test/ for further
information.
|
|
From: <al...@in...> - 2006-01-06 23:21:15
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20060107001615 |
|
From: Darren D. <da...@sh...> - 2006-01-06 18:38:00
|
1136572382 FAILED Last CVS updates prior to this build were: 1136571182 ? ? ? junit423465713.properties ? junittestcases2136842450.properties ? sandbox/src/org/springframework/core/closure/ElementGenerator.java ? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java ? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java ? sandbox/src/org/springframework/core/closure/support/IfBlock.java ? sandbox/src/org/springframework/jms/listener ? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml U build.xml P changelog.txt P readme.txt P lib/readme.txt U lib/jpa/persistence.jar P sandbox/src/org/springframework/util/ConventionUtils.java U src/org/springframework/beans/Mergable.java P src/org/springframework/beans/MutablePropertyValues.java P src/org/springframework/beans/factory/support/ManagedList.java P src/org/springframework/beans/factory/support/ManagedMap.java P src/org/springframework/beans/factory/support/ManagedProperties.java P src/org/springframework/beans/factory/support/ManagedSet.java P src/org/springframework/beans/factory/xml/DefaultXmlBeanDefinitionParser.java P src/org/springframework/orm/jdo/DefaultJdoDialect.java P src/org/springframework/web/servlet/DispatcherServlet.java P src/org/springframework/web/servlet/DispatcherServlet.properties P src/org/springframework/web/servlet/ModelAndView.java U src/org/springframework/web/servlet/RequestToViewNameTranslator.java U src/org/springframework/web/servlet/view/DefaultRequestToViewNameTranslator.java C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml P test/org/springframework/web/servlet/ComplexWebApplicationContext.java P test/org/springframework/web/servlet/DispatcherServletTests.java U tiger/src/org/springframework/orm/jpa/DefaultJpaDialect.java U tiger/src/org/springframework/orm/jpa/EntityManagerFactoryUtils.java U tiger/src/org/springframework/orm/jpa/EntityManagerHolder.java U tiger/src/org/springframework/orm/jpa/JpaAccessor.java U tiger/src/org/springframework/orm/jpa/JpaCallback.java U tiger/src/org/springframework/orm/jpa/JpaDialect.java U tiger/src/org/springframework/orm/jpa/JpaInterceptor.java U tiger/src/org/springframework/orm/jpa/JpaOperations.java U tiger/src/org/springframework/orm/jpa/JpaSystemException.java U tiger/src/org/springframework/orm/jpa/JpaTemplate.java U tiger/src/org/springframework/orm/jpa/JpaTransactionManager.java U tiger/src/org/springframework/orm/jpa/LocalEntityManagerFactoryBean.java U tiger/src/org/springframework/orm/jpa/package.html U tiger/src/org/springframework/orm/jpa/support/JpaDaoSupport.java U tiger/src/org/springframework/orm/jpa/support/OpenEntityManagerInViewFilter.java U tiger/src/org/springframework/orm/jpa/support/OpenEntityManagerInViewInterceptor.java U tiger/src/org/springframework/orm/jpa/support/PortletOpenEntityManagerInViewInterceptor.java U tiger/src/org/springframework/orm/jpa/support/SharedEntityManagerAdapter.java U tiger/src/org/springframework/orm/jpa/support/package.html 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 successful build occurs on the machine in question. See http://springframework.sourceforge.net/test/ for further information. |
|
From: Darren D. <da...@sh...> - 2006-01-06 02:42:51
|
1136515068
FAILED
[junit] Testcase: testNaming took 0,006 sec
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,014 sec
[junit] Testsuite: org.springframework.jmx.export.naming.PropertiesFileNamingStrategyTests
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,014 sec
[junit] Testcase: testNaming took 0,004 sec
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,017 sec
[junit] Testsuite: org.springframework.jmx.export.naming.PropertiesNamingStrategyTests
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,017 sec
[junit] Testcase: testNaming took 0 sec
[junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 0,117 sec
[junit] Testsuite: org.springframework.jmx.support.ConnectorServerFactoryBeanTests
[junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 0,117 sec
[junit] Testcase: testStartupWithLocatedServer took 0,056 sec
[junit] Testcase: testStartupWithSuppliedServer took 0,029 sec
[junit] Testcase: testRegisterWithMBeanServer took 0,013 sec
[junit] Caused an ERROR
[junit] Address already in use
[junit] java.net.BindException: Address already in use
[junit] at java.net.PlainSocketImpl.socketBind(Native Method)
[junit] at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
[junit] at java.net.ServerSocket.bind(ServerSocket.java:318)
[junit] at com.sun.jmx.remote.socket.SocketConnectionServer.start(SocketConnectionServer.java:128)
[junit] at com.sun.jmx.remote.generic.SynchroMessageConnectionServerImpl.start(SynchroMessageConnectionServerImpl.java:39)
[junit] at javax.management.remote.generic.GenericConnectorServer.start(GenericConnectorServer.java:235)
[junit] at org.springframework.jmx.support.ConnectorServerFactoryBean.afterPropertiesSet(ConnectorServerFactoryBean.java:167)
[junit] at org.springframework.jmx.support.ConnectorServerFactoryBeanTests.testRegisterWithMBeanServer(ConnectorServerFactoryBeanTests.java:78)
Last CVS updates prior to this build were:
1136513581
? ?
? junit423465713.properties
? junittestcases2136842450.properties
? sandbox/src/org/springframework/core/closure/ElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java
? sandbox/src/org/springframework/core/closure/support/IfBlock.java
? sandbox/src/org/springframework/jms/listener
? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
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
successful build occurs on the machine in question.
See http://springframework.sourceforge.net/test/ for further
information.
|
|
From: <al...@in...> - 2006-01-05 23:34:11
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20060106001627Lbuild.391 |
|
From: Eugene K. <eu...@md...> - 2006-01-05 20:23:09
|
Hi, By the way, speaking of XML... I wonder if anyone had a chance to look at http://opensource2.atlassian.com/projects/spring/browse/SPR-1333 I am not sure how new xml parser for Spring 2.0 had been implemented but it probably would benefit from using suggested approach. regards, Eugene Colin Sampaleanu wrote: > As per > http://opensource2.atlassian.com/projects/spring/browse/SPR-1568 > I've put up: > http://www.springframework.org/schema/aop/spring-aop.xsd > http://www.springframework.org/schema/beans/spring-beans.xsd > http://www.springframework.org/schema/jndi/spring-jndi.xsd > http://www.springframework.org/schema/tx/spring-tx.xsd > http://www.springframework.org/schema/util/spring-util.xsd > > Anybody updating the source schema files should make sure these files > are updated on www.springframework.org as well. Right now I believe > Thomas, Alef, Keith and I have access to the static web site and can > do updates. > > Colin > |
|
From: Colin S. <col...@ex...> - 2006-01-05 18:27:51
|
As per http://opensource2.atlassian.com/projects/spring/browse/SPR-1568 I've put up: http://www.springframework.org/schema/aop/spring-aop.xsd http://www.springframework.org/schema/beans/spring-beans.xsd http://www.springframework.org/schema/jndi/spring-jndi.xsd http://www.springframework.org/schema/tx/spring-tx.xsd http://www.springframework.org/schema/util/spring-util.xsd Anybody updating the source schema files should make sure these files are updated on www.springframework.org as well. Right now I believe Thomas, Alef, Keith and I have access to the static web site and can do updates. Colin -- Colin Sampaleanu Interface21 Principal Consultant Spring Training, Consulting and Support - "From the Source" http://www.springframework.com |
|
From: Darren D. <da...@sh...> - 2006-01-05 17:48:57
|
1136483037
FAILED
[junit] Testcase: testProxiedUserInterfacesWithNoInterface took 0.009 sec
[junit] Tests run: 17, Failures: 1, Errors: 0, Time elapsed: 36.936 sec
[junit] Testsuite: org.springframework.aop.framework.CglibProxyTests
[junit] Tests run: 17, Failures: 1, Errors: 0, Time elapsed: 36.936 sec
[junit] ------------- Standard Output ---------------
[junit] StopWatch '': running time (millis) = 28945; [class org.springframework.aop.framework.CglibProxyTests.testManyProxies: create 10000 proxies] took 28945 = 100%
[junit] ------------- ---------------- ---------------
[junit] Testcase: testNullConfig took 0.001 sec
[junit] Testcase: testNoTarget took 0.005 sec
[junit] Testcase: testProtectedMethodInvocation took 0.441 sec
[junit] Testcase: testProxyCanBeClassNotInterface took 1.451 sec
[junit] Testcase: testCglibProxyingGivesMeaningfulExceptionIfAskedToProxyNonvisibleClass took 0.032 sec
[junit] Testcase: testMethodInvocationDuringConstructor took 0.485 sec
[junit] Testcase: testUnadvisedProxyCreationWithCallDuringConstructor took 0.285 sec
[junit] Testcase: testMultipleProxies took 0.971 sec
[junit] Testcase: testWithNoArgConstructor took 0.291 sec
[junit] Testcase: testProxyAProxy took 0.987 sec
[junit] Testcase: testExceptionHandling took 0.49 sec
[junit] Testcase: testWithDependencyChecking took 1.204 sec
[junit] Testcase: testAddAdviceAtRuntime took 0.776 sec
[junit] Testcase: testProxyClassWithFinalMethods took 0.273 sec
[junit] Testcase: testNoInterceptorsAndNoTarget took 0 sec
[junit] Testcase: testValuesStick took 0.008 sec
[junit] Testcase: testManyProxies took 28.967 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:153)
Last CVS updates prior to this build were:
1136481181
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
successful build occurs on the machine in question.
See http://springframework.sourceforge.net/test/ for further
information.
|
1239 messages has been excluded from this view by a project administrator.
