Re: [JBoss-dev] Automated JBoss Testsuite Results: 18-May-2002
Hi, Should be possible - I will look into it. Chris - Original Message - From: Jason Dillon [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Friday, May 17, 2002 7:50 PM Subject: Re: [JBoss-dev] Automated JBoss Testsuite Results: 18-May-2002 Can we get direct links to the servers build and run logs in this mail too? --jason On Saturday 18 May 2002 01:37 am, [EMAIL PROTECTED] wrote: Number of tests run: 607 Successful tests: 530 Errors:73 Failures: 4 [time of test: 18 May 2002 2:35 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1_02a-FCS] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-31] See http://lubega.com/testarchive/blackdown_jdk131_02_native for details of this test. See http://lubega.com for general test information. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! Oh dear - still got some errors! Thanks for all your effort - we really do love you! ___ Hundreds of nodes, one monster rendering program. Now that's a super model! Visit http://clustering.foundries.sf.net/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Hundreds of nodes, one monster rendering program. Now that's a super model! Visit http://clustering.foundries.sf.net/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results: 18-May-2002
Can we get direct links to the servers build and run logs in this mail too? --jason On Saturday 18 May 2002 01:37 am, [EMAIL PROTECTED] wrote: Number of tests run: 607 Successful tests: 530 Errors:73 Failures: 4 [time of test: 18 May 2002 2:35 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1_02a-FCS] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-31] See http://lubega.com/testarchive/blackdown_jdk131_02_native for details of this test. See http://lubega.com for general test information. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! Oh dear - still got some errors! Thanks for all your effort - we really do love you! ___ Hundreds of nodes, one monster rendering program. Now that's a super model! Visit http://clustering.foundries.sf.net/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Hundreds of nodes, one monster rendering program. Now that's a super model! Visit http://clustering.foundries.sf.net/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results: 10-May-2002
Hi, --- danch [EMAIL PROTECTED] wrote: This report says 142 errors, but the HTML report it links to says 11. What gives? The dates don't match, but is that because this email is GMT and the HTML is server time? Nope - the test was sending the email before setting up the directory with the html - it was spending time ensuring the server stopped in between... at least 5mins plus... The links should be good now - as that time has passed... I've moved the setup of the html link stuff earlier - so it should be ready before the email is sent from now on. If the dates differ, then you are looking at different results - as the date from the same base XML results file for both reports (email and HTML). Chris = -- http://www.soccer2002.org.uk - The Game is On! __ Do You Yahoo!? Yahoo! Shopping - Mother's Day is May 12th! http://shopping.yahoo.com ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results: 10-May-2002
These summary statistics do not match those seen if you follow the report link. Why is that? The report lists the following: Number of tests run: 757 Successful tests: 740 Errors:3 Failures: 14 Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, May 09, 2002 4:47 PM Subject: [JBoss-dev] Automated JBoss Testsuite Results: 10-May-2002 Number of tests run: 757 Successful tests: 593 Errors:136 Failures: 28 [time of test: 10 May 2002 0:45 GMT] [java.version: 1.3.0] [java.vendor: IBM Corporation] [java.vm.version: 1.3.0] [java.vm.name: Classic VM] [java.vm.info: J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)] [os.name: Linux] [os.arch: x86] [os.version: 2.4.9-31] See http://lubega.com/testarchive/ibm_jdk13_20010626 for details of this test. See http://lubega.com for general test information. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results: 10-May-2002
This report says 142 errors, but the HTML report it links to says 11. What gives? The dates don't match, but is that because this email is GMT and the HTML is server time? -danch [EMAIL PROTECTED] wrote: Number of tests run: 757 Successful tests: 604 Errors:142 Failures: 11 [time of test: 10 May 2002 2:43 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1_02a-FCS] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-31] See http://lubega.com/testarchive/blackdown_jdk131_02_native for details of this test. See http://lubega.com for general test information. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! Oh dear - still got some errors! Thanks for all your effort - we really do love you! ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results: 28-April-2002
Quoting David Jencks [EMAIL PROTECTED]: It's a milestone, but ... 1. There are more bugs 2. this is only one jvm. 3. I think the testsuite should run twice with no errors (see bug 549775) We should make sure that the state of the container is the same before and after a test runs... I think we have tests conflicting with each other. This was the case a while back before we started undeploying test components and draining JMS destinations. It would be nice if there was a pre and post test that could do a quick scrape of the server state... perhaps list JMX components and JNDI mappings and then diff the two and fail of they are different. --jason - This mail sent through IMP: http://horde.org/imp/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Automated JBoss Testsuite Results: 28-April-2002
Holly molly |Number of tests run: 585 | | | |Successful tests: 582 |Errors:1 |Failures: 2 | | we are almost there, kudos to Mr Stark for this push. marcf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Automated JBoss Testsuite Results: 28-April-2002
The clustering test has 1 failure that I haven't been able to figure out. I guess I will have to comment it out.(the erroneous test) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of marc fleury Sent: Sunday, April 28, 2002 1:54 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Automated JBoss Testsuite Results: 28-April-2002 Holly molly |Number of tests run: 585 | | | |Successful tests: 582 |Errors:1 |Failures: 2 | | we are almost there, kudos to Mr Stark for this push. marcf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results: 28-April-2002
I'm pleased to say that after my latest fixes to the jca stuff i get, for Branch_3_0: Tests Failures Errors Success rate Time 582 00 100.00% 1348.885 on my linux jdk 1.4 setup. david jencks On 2002.04.28 13:54:00 -0400 marc fleury wrote: Holly molly |Number of tests run: 585 | | | |Successful tests: 582 |Errors:1 |Failures: 2 | | we are almost there, kudos to Mr Stark for this push. marcf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Automated JBoss Testsuite Results: 28-April-2002
Hooray! Then 3.0RC1 has graduated. Time to FINAL. ( I believe Scott wants to do a RC2 for at least a week). Time to congratulate each other. This is history in the making and I am glad to be here with you guys. PLeC (Excellent) marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of David |Jencks |Sent: Sunday, April 28, 2002 1:20 PM |To: marc fleury |Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] |Subject: Re: [JBoss-dev] Automated JBoss Testsuite Results: |28-April-2002 | | |I'm pleased to say that after my latest fixes to the jca stuff i get, for |Branch_3_0: | |Tests Failures Errors Success rate Time |582 00 100.00% 1348.885 | |on my linux jdk 1.4 setup. | |david jencks | |On 2002.04.28 13:54:00 -0400 marc fleury wrote: | Holly molly | | |Number of tests run: 585 | | | | | | | |Successful tests: 582 | |Errors:1 | |Failures: 2 | | | | | | we are almost there, kudos to Mr Stark for this push. | | | marcf | | ___ | Jboss-development mailing list | [EMAIL PROTECTED] | https://lists.sourceforge.net/lists/listinfo/jboss-development | | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results: 28-April-2002
It's a milestone, but ... 1. There are more bugs 2. this is only one jvm. 3. I think the testsuite should run twice with no errors (see bug 549775) 2.a Well, 1.9 jvms. Running on osx, everything passes except the cluster tests, which presumably fail because I removed cluster-service.xml. For some reason cluster-service.xml started hanging on my powerbook after the last time I booted. Is there some way to get it to throw an exception instead of hanging? 3.a I'm working on a fix to one of the big problems seen in the trace in that bug, datasources currently can't be stopped and restarted. In general do we want to claim that, on a running server, any mbean can be stopped and restarted and the server will still run? thanks david jencks On 2002.04.28 16:32:26 -0400 marc fleury wrote: Hooray! Then 3.0RC1 has graduated. Time to FINAL. ( I believe Scott wants to do a RC2 for at least a week). Time to congratulate each other. This is history in the making and I am glad to be here with you guys. PLeC (Excellent) marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of David |Jencks |Sent: Sunday, April 28, 2002 1:20 PM |To: marc fleury |Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] |Subject: Re: [JBoss-dev] Automated JBoss Testsuite Results: |28-April-2002 | | |I'm pleased to say that after my latest fixes to the jca stuff i get, for |Branch_3_0: | |Tests Failures Errors Success rate Time |582 00 100.00% 1348.885 | |on my linux jdk 1.4 setup. | |david jencks | |On 2002.04.28 13:54:00 -0400 marc fleury wrote: | Holly molly | | |Number of tests run: 585 | | | | | | | |Successful tests: 582 | |Errors:1 | |Failures: 2 | | | | | | we are almost there, kudos to Mr Stark for this push. | | | marcf | | ___ | Jboss-development mailing list | [EMAIL PROTECTED] | https://lists.sourceforge.net/lists/listinfo/jboss-development | | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results: 28-April-2002
Except that if you run the test twice in a row the error count does not stay at 0. Still more work to do. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: marc fleury [EMAIL PROTECTED] To: David Jencks [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Sunday, April 28, 2002 1:32 PM Subject: RE: [JBoss-dev] Automated JBoss Testsuite Results: 28-April-2002 Hooray! Then 3.0RC1 has graduated. Time to FINAL. ( I believe Scott wants to do a RC2 for at least a week). Time to congratulate each other. This is history in the making and I am glad to be here with you guys. PLeC (Excellent) marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of David |Jencks |Sent: Sunday, April 28, 2002 1:20 PM |To: marc fleury |Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] |Subject: Re: [JBoss-dev] Automated JBoss Testsuite Results: |28-April-2002 | | |I'm pleased to say that after my latest fixes to the jca stuff i get, for |Branch_3_0: | |Tests Failures Errors Success rate Time |582 00 100.00% 1348.885 | |on my linux jdk 1.4 setup. | |david jencks | |On 2002.04.28 13:54:00 -0400 marc fleury wrote: | Holly molly | | |Number of tests run: 585 | | | | | | | |Successful tests: 582 | |Errors:1 | |Failures: 2 | | | | | | we are almost there, kudos to Mr Stark for this push. | | | marcf | | ___ | Jboss-development mailing list | [EMAIL PROTECTED] | https://lists.sourceforge.net/lists/listinfo/jboss-development | | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Automated JBoss Testsuite Results: 28-April-2002
oh well, now the trick is to put the champagne bottle cork BACK in the bottle :) he he marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Scott |M Stark |Sent: Sunday, April 28, 2002 2:46 PM |To: [EMAIL PROTECTED] |Subject: Re: [JBoss-dev] Automated JBoss Testsuite Results: |28-April-2002 | | |Except that if you run the test twice in a row the error count does |not stay at 0. Still more work to do. | | |Scott Stark |Chief Technology Officer |JBoss Group, LLC | |- Original Message - |From: marc fleury [EMAIL PROTECTED] |To: David Jencks [EMAIL PROTECTED] |Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] |Sent: Sunday, April 28, 2002 1:32 PM |Subject: RE: [JBoss-dev] Automated JBoss Testsuite Results: 28-April-2002 | | | Hooray! | | Then 3.0RC1 has graduated. Time to FINAL. ( I believe Scott |wants to do a | RC2 for at least a week). | | Time to congratulate each other. | | This is history in the making and I am glad to be here with you guys. | | PLeC (Excellent) | | marcf | | | |-Original Message- | |From: [EMAIL PROTECTED] | |[mailto:[EMAIL PROTECTED]]On Behalf Of David | |Jencks | |Sent: Sunday, April 28, 2002 1:20 PM | |To: marc fleury | |Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] | |Subject: Re: [JBoss-dev] Automated JBoss Testsuite Results: | |28-April-2002 | | | | | |I'm pleased to say that after my latest fixes to the jca stuff |i get, for | |Branch_3_0: | | | |Tests Failures Errors Success rate Time | |582 00 100.00% 1348.885 | | | |on my linux jdk 1.4 setup. | | | |david jencks | | | |On 2002.04.28 13:54:00 -0400 marc fleury wrote: | | Holly molly | | | | |Number of tests run: 585 | | | | | | | | | | | |Successful tests: 582 | | |Errors:1 | | |Failures: 2 | | | | | | | | | | we are almost there, kudos to Mr Stark for this push. | | | | | | marcf | | | | ___ | | Jboss-development mailing list | | [EMAIL PROTECTED] | | https://lists.sourceforge.net/lists/listinfo/jboss-development | | | | | | | |___ | |Jboss-development mailing list | |[EMAIL PROTECTED] | |https://lists.sourceforge.net/lists/listinfo/jboss-development | | | ___ | Jboss-development mailing list | [EMAIL PROTECTED] | https://lists.sourceforge.net/lists/listinfo/jboss-development | | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results: 13-April-2002
Thanks Chris! --jason [EMAIL PROTECTED] wrote: Number of tests run: 556 Successful tests: 498 Errors:53 Failures: 5 [time of test: 13 April 2002 1:15 GMT] [java.version: 1.3.0] [java.vendor: IBM Corporation] [java.vm.version: 1.3.0] [java.vm.name: Classic VM] [java.vm.info: J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)] [os.name: Linux] [os.arch: x86] [os.version: 2.4.9-31] See http://lubega.com/testarchive/ibm_jdk13_20010626 for details of this test. See http://lubega.com for general test information. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! Oh dear - still got some errors! Thanks for all your effort - we really do love you! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results: 12-April-2002
How about returning a link to the junit results page for the run? --jason [EMAIL PROTECTED] wrote: JBoss daily test results SUMMARY Number of tests run: 567 Successful tests: 505 Errors:56 Failures: 6 [time of test: 12 April 2002 0:57 GMT] [java.version: 1.3.0] [java.vendor: IBM Corporation] [java.vm.version: 1.3.0] [java.vm.name: Classic VM] [java.vm.info: J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)] [os.name: Linux] [os.arch: x86] [os.version: 2.4.9-31] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! DETAILS OF ERRORS [details not shown -as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite! Its really is easy, just use the ant target 'run-basic-testsuite' from the build directory. To just run the unit tests (they are quite quick): In the testsuite directory, ./build.sh tests-unit You can run a single test case using: ./build.sh -Dtest=[XXXTestCase] one-test The XXXTestCase is the classname of the junit class to run. So, to run the EJBSpecUnitTestCase use: ./build.sh -Dtest=EJBSpecUnitTestCase one-test To run all tests within a package, use ./build.sh -Dtest=[package] test The package is name of the directory under the org/jboss/test directory that contains the tests to run. So, to run the unit tests in the org.jboss.test.security package use: ./build.sh -Dtest=security test Thanks for all your effort - we really do love you! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results: 25-March-2002
This was caused by both versions of defaultds configuration (hsqldb-default-service.xml and newhsqldb-default-service.xml) being copied to deploy. I've fixed it in cvs... we'll see how the next run goes. david jencks On 2002.03.24 19:39:39 -0500 [EMAIL PROTECTED] wrote: JBoss daily test results SUMMARY Number of tests run: 556 Successful tests: 379 Errors:149 Failures: 28 [time of test: 25 March 2002 0:37 GMT] [java.version: 1.3.0] [java.vendor: IBM Corporation] [java.vm.version: 1.3.0] [java.vm.name: Classic VM] [java.vm.info: J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)] [os.name: Linux] [os.arch: x86] [os.version: 2.4.9-31] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! DETAILS OF ERRORS [details not shown -as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite! Its really is easy, just use the ant target 'run-basic-testsuite' from the build directory. To just run the unit tests (they are quite quick): In the testsuite directory, ./build.sh tests-unit You can run a single test case using: ./build.sh -Dtest=[XXXTestCase] one-test The XXXTestCase is the classname of the junit class to run. So, to run the EJBSpecUnitTestCase use: ./build.sh -Dtest=EJBSpecUnitTestCase one-test To run all tests within a package, use ./build.sh -Dtest=[package] test The package is name of the directory under the org/jboss/test directory that contains the tests to run. So, to run the unit tests in the org.jboss.test.security package use: ./build.sh -Dtest=security test Thanks for all your effort - we really do love you! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Automated JBoss Testsuite Results: 9-March-2002
huh? since i didn't do any testing before i left i didn't expect this to report so many succesful tests are we sure that this suite is working properly? marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of |[EMAIL PROTECTED] |Sent: Friday, March 08, 2002 9:26 PM |To: [EMAIL PROTECTED] |Subject: [JBoss-dev] Automated JBoss Testsuite Results: 9-March-2002 | | | | |JBoss daily test results | |SUMMARY | |Number of tests run: 535 | | | |Successful tests: 509 | |Errors:21 | |Failures: 5 | | | | | |[time of test: 9 March 2002 5:25 GMT] |[java.version: 1.3.1_02] |[java.vendor: Sun Microsystems Inc.] |[java.vm.version: 1.3.1_02-b02] |[java.vm.name: Java HotSpot(TM) Server VM] |[java.vm.info: mixed mode] |[os.name: Linux] |[os.arch: i386] |[os.version: 2.4.9-31] | |See http://lubega.com for full details | |NOTE: If there are any errors shown above - this mail is only highlighting |them - it is NOT indicating that they are being looked at by anyone. |Remember - if a test becomes broken after your changes - fix it or |fix the test! | | | | | |DETAILS OF ERRORS | |[details not shown -as this makes the mail too big to reach the sf |mailing list] | | | | |PS BEFORE you commit, run the test suite! | |Its really is easy, just use the ant target 'run-basic-testsuite' from the |build directory. | | |To just run the unit tests (they are quite quick): | |In the testsuite directory, |./build.sh tests-unit | | |You can run a single test case using: |./build.sh -Dtest=[XXXTestCase] one-test | |The XXXTestCase is the classname of the junit class to run. So, to run the |EJBSpecUnitTestCase use: |./build.sh -Dtest=EJBSpecUnitTestCase one-test | | |To run all tests within a package, use |./build.sh -Dtest=[package] test | |The package is name of the directory under the org/jboss/test |directory that |contains the tests to run. So, to run the unit tests in the |org.jboss.test.security package use: |./build.sh -Dtest=security test | | | |Thanks for all your effort - we really do love you! | | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development | ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Automated JBoss Testsuite Results: 9-March-2002
Hi, --- marc fleury [EMAIL PROTECTED] wrote: are we sure that this suite is working properly? Looks good to me - the cvs update bit patched some files - so the latest code should be there. Everything looks fairly ok... Chris = Need somewhere to Live in London? - Then go to http://freeflats.com __ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.com/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
RedHat 7.2 with Sun JDK 1.3.1_02 is what is working for me: [starksm@banshee testsuite]$ uname -a Linux banshee.starkinternational.com 2.4.9-13 #1 Tue Oct 30 20:11:04 EST 2001 i686 unknown [starksm@banshee testsuite]$ java -version java version 1.3.1_02 Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_02-b02) Java HotSpot(TM) Client VM (build 1.3.1_02-b02, mixed mode) ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Hi, --- Scott M Stark [EMAIL PROTECTED] wrote: RedHat 7.2 with Sun JDK 1.3.1_02 is what is working for me: Thanks for that - I've just installed that on the server too - so we will get 5 messages per day. I think the problem is solved - the latest jboss re-org had moved the location of the log directory and I was trying to pipe the console into an invalid directory - which seems to cause the server some problems - although I can't really believe this is the main cause. I also increased the time I allow for the server to warm up - it was 2mins - but my test runs show it taking 1min 40secs or so - which is getting close - so it now allows 5 mins for the server to warm up. Making this change alone was not enough to fix the problem - but the console logging seems to have helped - I am still running the tests. There are currently some connectivity issues with the test servers hosting company - but not enough to stop me working on it - so I don't think that should cause any problems either. Chris = Need somewhere to Live in London? - Then go to http://freeflats.com __ Do You Yahoo!? Yahoo! Greetings - Send FREE e-cards for every occasion! http://greetings.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results: 2-March-2002
Wow... a unique subject line... nice. Forums will like this too... --jason [EMAIL PROTECTED] wrote: JBoss daily test results SUMMARY Number of tests run: 503 Successful tests: 494 Errors:4 Failures: 5 [time of test: 2 March 2002 2:57 GMT] [java.version: 1.3.0] [java.vendor: IBM Corporation] [java.vm.version: 1.3.0] [java.vm.name: Classic VM] [java.vm.info: J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)] [os.name: Linux] [os.arch: x86] [os.version: 2.4.9-21] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! DETAILS OF ERRORS [details not shown -as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite! Its really is easy, just use the ant target 'run-basic-testsuite' from the build directory. To just run the unit tests (they are quite quick): In the testsuite directory, ./build.sh tests-unit You can run a single test case using: ./build.sh -Dtest=[XXXTestCase] one-test The XXXTestCase is the classname of the junit class to run. So, to run the EJBSpecUnitTestCase use: ./build.sh -Dtest=EJBSpecUnitTestCase one-test To run all tests within a package, use ./build.sh -Dtest=[package] test The package is name of the directory under the org/jboss/test directory that contains the tests to run. So, to run the unit tests in the org.jboss.test.security package use: ./build.sh -Dtest=security test Thanks for all your effort - we really do love you! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Hi, The test host looks hosed as there are numerous JNDI lookup failures of the JNDI service. javax.naming.CommunicationException: Receive timed out. Root exception is java.io.InterruptedIOException: Receive timed out at java.net.PlainDatagramSocketImpl.receive(Native Method) at java.net.DatagramSocket.receive(DatagramSocket.java:392) I think it is just a problem with the current build of JBoss ;-) There does not seem to be any jboss processes running now - which is usually the cause of these kind of clashes. I presume if CVS had changed drastically then the problem would have been more fundamental - ie not compiling - unless the code has become really well decoupled in the last day or so... I am going to put the date into the subject of these messages too - it will make it easier to follow discussions about problems on the forums... Regards, Chris _ Chat with friends online, try MSN Messenger: http://messenger.msn.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
I just pulled down a clean co and built it on my linux box and the tests are running fine: [junit] Running org.jboss.test.util.test.SchedulerUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 1.878 sec [junit] Running org.jboss.test.bmp.test.BmpUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 8.359 sec [junit] Running org.jboss.test.cmp2.ejbselect.EJBSelectUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 5.139 sec [junit] Running org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 3.975 sec [junit] Running org.jboss.test.cmp2.relationship.RelationshipUnitTestCase [junit] Tests run: 21, Failures: 0, Errors: 0, Time elapsed: 20.51 sec [junit] Running org.jboss.test.cts.test.BmpUnitTestCase [junit] GETTING THE HOME [junit] Tests run: 11, Failures: 0, Errors: 0, Time elapsed: 22.198 sec [junit] Running org.jboss.test.cts.test.StatefulSessionUnitTestCase so either you grabbed an inconsistent snaptshot or something else is up as the current build looks fine. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Chris Kimpton [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, February 28, 2002 12:27 AM Subject: Re: [JBoss-dev] Automated JBoss Testsuite Results Hi, The test host looks hosed as there are numerous JNDI lookup failures of the JNDI service. javax.naming.CommunicationException: Receive timed out. Root exception is java.io.InterruptedIOException: Receive timed out at java.net.PlainDatagramSocketImpl.receive(Native Method) at java.net.DatagramSocket.receive(DatagramSocket.java:392) I think it is just a problem with the current build of JBoss ;-) There does not seem to be any jboss processes running now - which is usual ly the cause of these kind of clashes. I presume if CVS had changed drastically then the problem would have been more fundamental - ie not compiling - unless the code has become really well decoupled in the last day or so... I am going to put the date into the subject of these messages too - it will make it easier to follow discussions about problems on the forums... Regards, Chris ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Hi, Thanks - just ran the job again with updated CVS and it still failed. I can't see any obvious problems in the server log - HA JNDI seems to start up ok. I don't suppose there are alternate configs now and the default one is not the one to be used for testing - perhaps? I am now doing a clean checkout will see if that works better. Chris --- Scott M Stark [EMAIL PROTECTED] wrote: I just pulled down a clean co and built it on my linux box and the tests are running fine: [junit] Running org.jboss.test.util.test.SchedulerUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 1.878 sec [junit] Running org.jboss.test.bmp.test.BmpUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 8.359 sec = Need somewhere to Live in London? - Then go to http://freeflats.com __ Do You Yahoo!? Yahoo! Greetings - Send FREE e-cards for every occasion! http://greetings.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Hi, I still get problems, even with a clean checkout - but if I run it manually - it works - AAARGH! I am going to have to spend some more time on this... Chris = Need somewhere to Live in London? - Then go to http://freeflats.com __ Do You Yahoo!? Yahoo! Greetings - Send FREE e-cards for every occasion! http://greetings.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Automated JBoss Testsuite Results: 1-March-2002
YO we got a problem marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of |[EMAIL PROTECTED] |Sent: Thursday, February 28, 2002 7:41 PM |To: [EMAIL PROTECTED] |Subject: [JBoss-dev] Automated JBoss Testsuite Results: 1-March-2002 | | | | |JBoss daily test results | |SUMMARY | |Number of tests run: 471 | | | |Successful tests: 200 | |Errors:263 | |Failures: 8 | | | | | |[time of test: 1 March 2002 3:40 GMT] |[java.version: 1.3.1] |[java.vendor: Blackdown Java-Linux Team] |[java.vm.version: Blackdown-1.3.1-FCS] |[java.vm.name: Java HotSpot(TM) Client VM] |[java.vm.info: mixed mode] |[os.name: Linux] |[os.arch: i386] |[os.version: 2.4.9-21] | |See http://lubega.com for full details | |NOTE: If there are any errors shown above - this mail is only highlighting |them - it is NOT indicating that they are being looked at by anyone. |Remember - if a test becomes broken after your changes - fix it or |fix the test! | | | | | |DETAILS OF ERRORS | |[details not shown -as this makes the mail too big to reach the sf |mailing list] | | | | |PS BEFORE you commit, run the test suite! | |Its really is easy, just use the ant target 'run-basic-testsuite' from the |build directory. | | |To just run the unit tests (they are quite quick): | |In the testsuite directory, |./build.sh tests-unit | | |You can run a single test case using: |./build.sh -Dtest=[XXXTestCase] one-test | |The XXXTestCase is the classname of the junit class to run. So, to run the |EJBSpecUnitTestCase use: |./build.sh -Dtest=EJBSpecUnitTestCase one-test | | |To run all tests within a package, use |./build.sh -Dtest=[package] test | |The package is name of the directory under the org/jboss/test |directory that |contains the tests to run. So, to run the unit tests in the |org.jboss.test.security package use: |./build.sh -Dtest=security test | | | |Thanks for all your effort - we really do love you! | | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
PLEASE READ!!!!!!!!!RE: [JBoss-dev] Automated JBoss Testsuite Results: 1-March-2002
ONE OF THE PATCHES OF TODAY, just broke half the tests... ! please revert your patches so we find the culprit. I did it myself, so really it's ok but we need to solve this marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of |[EMAIL PROTECTED] |Sent: Thursday, February 28, 2002 8:57 PM |To: [EMAIL PROTECTED] |Subject: [JBoss-dev] Automated JBoss Testsuite Results: 1-March-2002 | | | | |JBoss daily test results | |SUMMARY | |Number of tests run: 471 | | | |Successful tests: 200 | |Errors:263 | |Failures: 8 | | | | | |[time of test: 1 March 2002 4:51 GMT] |[java.version: 1.3.1] |[java.vendor: Blackdown Java-Linux Team] |[java.vm.version: Blackdown-1.3.1-FCS] |[java.vm.name: Classic VM] |[java.vm.info: green threads, nojit] |[os.name: Linux] |[os.arch: i386] |[os.version: 2.4.9-21] | |See http://lubega.com for full details | |NOTE: If there are any errors shown above - this mail is only highlighting |them - it is NOT indicating that they are being looked at by anyone. |Remember - if a test becomes broken after your changes - fix it or |fix the test! | | | | | |DETAILS OF ERRORS | |[details not shown -as this makes the mail too big to reach the sf |mailing list] | | | | |PS BEFORE you commit, run the test suite! | |Its really is easy, just use the ant target 'run-basic-testsuite' from the |build directory. | | |To just run the unit tests (they are quite quick): | |In the testsuite directory, |./build.sh tests-unit | | |You can run a single test case using: |./build.sh -Dtest=[XXXTestCase] one-test | |The XXXTestCase is the classname of the junit class to run. So, to run the |EJBSpecUnitTestCase use: |./build.sh -Dtest=EJBSpecUnitTestCase one-test | | |To run all tests within a package, use |./build.sh -Dtest=[package] test | |The package is name of the directory under the org/jboss/test |directory that |contains the tests to run. So, to run the unit tests in the |org.jboss.test.security package use: |./build.sh -Dtest=security test | | | |Thanks for all your effort - we really do love you! | | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: PLEASE READ!!!!!!!!!RE: [JBoss-dev] Automated JBoss Testsuite Results: 1-March-2002
Look before you leap, marc. I just ran the testsuite and there are 7 errors, just like yesterday. I think maybe chris's setup doesnt cope well with build failures. david jencks On 2002.03.01 03:11:21 -0500 marc fleury wrote: ONE OF THE PATCHES OF TODAY, just broke half the tests... ! bull please revert your patches so we find the culprit. I did it myself, so really it's ok but we need to solve this marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of |[EMAIL PROTECTED] |Sent: Thursday, February 28, 2002 8:57 PM |To: [EMAIL PROTECTED] |Subject: [JBoss-dev] Automated JBoss Testsuite Results: 1-March-2002 | | | | |JBoss daily test results | |SUMMARY | |Number of tests run: 471 | | | |Successful tests: 200 | |Errors:263 | |Failures: 8 | | | | | |[time of test: 1 March 2002 4:51 GMT] |[java.version: 1.3.1] |[java.vendor: Blackdown Java-Linux Team] |[java.vm.version: Blackdown-1.3.1-FCS] |[java.vm.name: Classic VM] |[java.vm.info: green threads, nojit] |[os.name: Linux] |[os.arch: i386] |[os.version: 2.4.9-21] | |See http://lubega.com for full details | |NOTE: If there are any errors shown above - this mail is only highlighting |them - it is NOT indicating that they are being looked at by anyone. |Remember - if a test becomes broken after your changes - fix it or |fix the test! | | | | | |DETAILS OF ERRORS | |[details not shown -as this makes the mail too big to reach the sf |mailing list] | | | | |PS BEFORE you commit, run the test suite! | |Its really is easy, just use the ant target 'run-basic-testsuite' from the |build directory. | | |To just run the unit tests (they are quite quick): | |In the testsuite directory, |./build.sh tests-unit | | |You can run a single test case using: |./build.sh -Dtest=[XXXTestCase] one-test | |The XXXTestCase is the classname of the junit class to run. So, to run the |EJBSpecUnitTestCase use: |./build.sh -Dtest=EJBSpecUnitTestCase one-test | | |To run all tests within a package, use |./build.sh -Dtest=[package] test | |The package is name of the directory under the org/jboss/test |directory that |contains the tests to run. So, to run the unit tests in the |org.jboss.test.security package use: |./build.sh -Dtest=security test | | | |Thanks for all your effort - we really do love you! | | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: PLEASE READ!!!!!!!!!RE: [JBoss-dev] Automated JBoss Testsuite Results: 1-March-2002
Its the same problem as yesterday and the issue is with the test machine not the build as the test run fine for me. Chris said he was looking into the problem. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: marc fleury [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Friday, March 01, 2002 12:11 AM Subject: PLEASE READ!RE: [JBoss-dev] Automated JBoss Testsuite Results: 1-March-2002 ONE OF THE PATCHES OF TODAY, just broke half the tests... ! please revert your patches so we find the culprit. I did it myself, so really it's ok but we need to solve this marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of |[EMAIL PROTECTED] |Sent: Thursday, February 28, 2002 8:57 PM |To: [EMAIL PROTECTED] |Subject: [JBoss-dev] Automated JBoss Testsuite Results: 1-March-2002 | | | | |JBoss daily test results | |SUMMARY | |Number of tests run: 471 | | | |Successful tests: 200 | |Errors:263 | |Failures: 8 | | | | | |[time of test: 1 March 2002 4:51 GMT] |[java.version: 1.3.1] |[java.vendor: Blackdown Java-Linux Team] |[java.vm.version: Blackdown-1.3.1-FCS] |[java.vm.name: Classic VM] |[java.vm.info: green threads, nojit] |[os.name: Linux] |[os.arch: i386] |[os.version: 2.4.9-21] | |See http://lubega.com for full details | |NOTE: If there are any errors shown above - this mail is only highlighting |them - it is NOT indicating that they are being looked at by anyone. |Remember - if a test becomes broken after your changes - fix it or |fix the test! | | | | | |DETAILS OF ERRORS | |[details not shown -as this makes the mail too big to reach the sf |mailing list] | | | | |PS BEFORE you commit, run the test suite! | |Its really is easy, just use the ant target 'run-basic-testsuite' from the |build directory. | | |To just run the unit tests (they are quite quick): | |In the testsuite directory, |./build.sh tests-unit | | |You can run a single test case using: |./build.sh -Dtest=[XXXTestCase] one-test | |The XXXTestCase is the classname of the junit class to run. So, to run the |EJBSpecUnitTestCase use: |./build.sh -Dtest=EJBSpecUnitTestCase one-test | | |To run all tests within a package, use |./build.sh -Dtest=[package] test | |The package is name of the directory under the org/jboss/test |directory that |contains the tests to run. So, to run the unit tests in the |org.jboss.test.security package use: |./build.sh -Dtest=security test | | | |Thanks for all your effort - we really do love you! | | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: PLEASE READ!!!!!!!!!RE: [JBoss-dev] Automated JBoss Testsuite Results: 1-March-2002
ok I get it, marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Scott |M Stark |Sent: Thursday, February 28, 2002 11:18 PM |To: [EMAIL PROTECTED] |Subject: Re: PLEASE READ!RE: [JBoss-dev] Automated JBoss |Testsuite Results: 1-March-2002 | | |Its the same problem as yesterday and the issue is with the |test machine not the build as the test run fine for me. Chris |said he was looking into the problem. | | |Scott Stark |Chief Technology Officer |JBoss Group, LLC | |- Original Message - |From: marc fleury [EMAIL PROTECTED] |To: [EMAIL PROTECTED]; [EMAIL PROTECTED] |Sent: Friday, March 01, 2002 12:11 AM |Subject: PLEASE READ!RE: [JBoss-dev] Automated JBoss Testsuite |Results: 1-March-2002 | | | ONE OF THE PATCHES OF TODAY, | | just broke half the tests... ! | | please revert your patches so we find the culprit. | | I did it myself, so really it's ok but we need to solve this | | | marcf | | |-Original Message- | |From: [EMAIL PROTECTED] | |[mailto:[EMAIL PROTECTED]]On Behalf Of | |[EMAIL PROTECTED] | |Sent: Thursday, February 28, 2002 8:57 PM | |To: [EMAIL PROTECTED] | |Subject: [JBoss-dev] Automated JBoss Testsuite Results: 1-March-2002 | | | | | | | | | |JBoss daily test results | | | |SUMMARY | | | |Number of tests run: 471 | | | | | | | |Successful tests: 200 | | | |Errors:263 | | | |Failures: 8 | | | | | | | | | | | |[time of test: 1 March 2002 4:51 GMT] | |[java.version: 1.3.1] | |[java.vendor: Blackdown Java-Linux Team] | |[java.vm.version: Blackdown-1.3.1-FCS] | |[java.vm.name: Classic VM] | |[java.vm.info: green threads, nojit] | |[os.name: Linux] | |[os.arch: i386] | |[os.version: 2.4.9-21] | | | |See http://lubega.com for full details | | | |NOTE: If there are any errors shown above - this mail is only |highlighting | |them - it is NOT indicating that they are being looked at by anyone. | |Remember - if a test becomes broken after your changes - fix it or | |fix the test! | | | | | | | | | | | |DETAILS OF ERRORS | | | |[details not shown -as this makes the mail too big to reach the sf | |mailing list] | | | | | | | | | |PS BEFORE you commit, run the test suite! | | | |Its really is easy, just use the ant target 'run-basic-testsuite' from |the | |build directory. | | | | | |To just run the unit tests (they are quite quick): | | | |In the testsuite directory, | |./build.sh tests-unit | | | | | |You can run a single test case using: | |./build.sh -Dtest=[XXXTestCase] one-test | | | |The XXXTestCase is the classname of the junit class to run. So, to run |the | |EJBSpecUnitTestCase use: | |./build.sh -Dtest=EJBSpecUnitTestCase one-test | | | | | |To run all tests within a package, use | |./build.sh -Dtest=[package] test | | | |The package is name of the directory under the org/jboss/test | |directory that | |contains the tests to run. So, to run the unit tests in the | |org.jboss.test.security package use: | |./build.sh -Dtest=security test | | | | | | | |Thanks for all your effort - we really do love you! | | | | | | | |___ | |Jboss-development mailing list | |[EMAIL PROTECTED] | |https://lists.sourceforge.net/lists/listinfo/jboss-development | | | ___ | Jboss-development mailing list | [EMAIL PROTECTED] | https://lists.sourceforge.net/lists/listinfo/jboss-development | | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
The test host looks hosed as there are numerous JNDI lookup failures of the JNDI service. javax.naming.CommunicationException: Receive timed out. Root exception is java.io.InterruptedIOException: Receive timed out at java.net.PlainDatagramSocketImpl.receive(Native Method) at java.net.DatagramSocket.receive(DatagramSocket.java:392) at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:820) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:890) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:356) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:349) at javax.naming.InitialContext.lookup(InitialContext.java:350) at org.jboss.test.bank.test.BankStressTestCase.setUp(BankStressTestCase.java:44 4) Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, February 27, 2002 9:14 PM Subject: [JBoss-dev] Automated JBoss Testsuite Results JBoss daily test results SUMMARY Number of tests run: 471 Successful tests: 200 Errors:263 Failures: 8 [time of test: 28 February 2002 5:5 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1-FCS] [java.vm.name: Classic VM] [java.vm.info: green threads, nojit] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-21] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Hi, --- Jason Dillon [EMAIL PROTECTED] wrote: I am gonna need you to perform a full checkout from cvs again. Its in progress... Chris = Need somewhere to Live in London? - Then go to http://freeflats.com __ Do You Yahoo!? Yahoo! Sports - Coverage of the 2002 Olympic Games http://sports.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
I am gonna need you to perform a full checkout from cvs again. --jason On Sat, 2002-02-16 at 20:28, [EMAIL PROTECTED] wrote: JBoss daily test results SUMMARY Number of tests run: 493 Successful tests: 485 Errors:4 Failures: 4 [time of test: 17 February 2002 4:19 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1-FCS] [java.vm.name: Classic VM] [java.vm.info: green threads, nojit] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-12] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! DETAILS OF ERRORS [details not shown -as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite! Its really is easy, just use the ant target 'run-basic-testsuite' from the build directory. To just run the unit tests (they are quite quick): In the testsuite directory, ./build.sh tests-unit You can run a single test case using: ./build.sh -Dtest=[XXXTestCase] one-test The XXXTestCase is the classname of the junit class to run. So, to run the EJBSpecUnitTestCase use: ./build.sh -Dtest=EJBSpecUnitTestCase one-test To run all tests within a package, use ./build.sh -Dtest=[package] test The package is name of the directory under the org/jboss/test directory that contains the tests to run. So, to run the unit tests in the org.jboss.test.security package use: ./build.sh -Dtest=security test Thanks for all your effort - we really do love you! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Why doesn't this show 201 tests? --jason On Thu, 13 Dec 2001 [EMAIL PROTECTED] wrote: JBoss daily test results SUMMARY Number of tests run: 127 Successful tests: 127 Errors:0 Failures: 0 [time of test: 13 December 2001 10:17 GMT] [java.version: 1.3.1] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.3.1-b24] [java.vm.name: Java HotSpot(TM) Server VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-12] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! PS BEFORE you commit, run the test suite. Its easy, just run the target 'run-basic-testsuite' from the main build.xml. PPS Come on people - there were a few days back in July 2001 when we had ZERO tests failing! Oh, and thanks - remember we love you too! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
On 2001.12.13 15:31:27 -0500 Jason Dillon wrote: Why doesn't this show 201 tests? --jason I think something got stuck, lots of tests failed completely (no xml output at all, so they aren't in this summary), and finally shutdown didn't work, generating the other message you love so much. ;-) (I will stop when all the tests run every time, I think) david jencks On Thu, 13 Dec 2001 [EMAIL PROTECTED] wrote: JBoss daily test results SUMMARY Number of tests run: 127 Successful tests: 127 Errors:0 Failures: 0 [time of test: 13 December 2001 10:17 GMT] [java.version: 1.3.1] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.3.1-b24] [java.vm.name: Java HotSpot(TM) Server VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-12] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! PS BEFORE you commit, run the test suite. Its easy, just run the target 'run-basic-testsuite' from the main build.xml. PPS Come on people - there were a few days back in July 2001 when we had ZERO tests failing! Oh, and thanks - remember we love you too! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Why doesn't this show 201 tests? I think something got stuck, lots of tests failed completely (no xml output at all, so they aren't in this summary), and finally shutdown didn't work, generating the other message you love so much. ;-) (I will stop when all the tests run every time, I think) Can we get it fixed so that it will show us that these tests failed? --jason ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
On 2001.12.13 16:49:49 -0500 David Jencks wrote: On 2001.12.13 15:31:27 -0500 Jason Dillon wrote: Why doesn't this show 201 tests? --jason I think something got stuck, lots of tests failed completely (no xml output at all, so they aren't in this summary), and finally shutdown didn't work, generating the other message you love so much. ;-) (I will stop when all the tests run every time, I think) Ummm that would be It will stop... ;-) I plan to keep going. david david jencks On Thu, 13 Dec 2001 [EMAIL PROTECTED] wrote: JBoss daily test results SUMMARY Number of tests run: 127 Successful tests: 127 Errors:0 Failures: 0 [time of test: 13 December 2001 10:17 GMT] [java.version: 1.3.1] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.3.1-b24] [java.vm.name: Java HotSpot(TM) Server VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-12] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! PS BEFORE you commit, run the test suite. Its easy, just run the target 'run-basic-testsuite' from the main build.xml. PPS Come on people - there were a few days back in July 2001 when we had ZERO tests failing! Oh, and thanks - remember we love you too! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Hi, Why doesn't this show 201 tests? Don't you just love Java's portability... ;-) Chris ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
On 2001.12.13 17:10:34 -0500 Jason Dillon wrote: Why doesn't this show 201 tests? I think something got stuck, lots of tests failed completely (no xml output at all, so they aren't in this summary), and finally shutdown didn't work, generating the other message you love so much. ;-) (I will stop when all the tests run every time, I think) Can we get it fixed so that it will show us that these tests failed? That would be nice, I don't have time right now. I think the problem is with tests that timeout, they generate no xml report. I expect this will take some digging around in the junit task and possibly junit. Maybe a bug report at ant would help. david --jason ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
I created a bug report on this on 2001-07-07 20:51 http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2499 Can we get it fixed so that it will show us that these tests failed? That would be nice, I don't have time right now. I think the problem is with tests that timeout, they generate no xml report. I expect this will take some digging around in the junit task and possibly junit. Maybe a bug report at ant would help. david ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Automated JBoss Testsuite Results
Tag that build! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Thursday, December 13, 2001 1:13 AM To: [EMAIL PROTECTED] Subject: [JBoss-dev] Automated JBoss Testsuite Results JBoss daily test results SUMMARY Number of tests run: 201 Successful tests: 201 Errors:0 Failures: 0 [time of test: 13 December 2001 6:12 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1-FCS] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-12] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! PS BEFORE you commit, run the test suite. Its easy, just run the target 'run-basic-testsuite' from the main build.xml. PPS Come on people - there were a few days back in July 2001 when we had ZERO tests failing! Oh, and thanks - remember we love you too! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
I am impressed by the fact that green threeds now runs all tests and the others run 36 lesser tests - it used to be the other way around not to long ago ? ... /peter_f ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Hi, Errors:1 Failures: 2 Yes - out of 162 We have a 100% success rate - the above test stat is missing that XA is not a valid test *now* (Error) therefore it should be removed - and if javac is in the classpath the other 2 is cleared as well ... javac is in the classpath - is there something I can change in my config to correct this? I believe I have an empty CLASSPATH when starting the jboss tests - so it should just be what jboss/ant adds... Chris = Need somewhere to Live in London? - Then go to http://freeflats.com __ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Hi, PPS Come on people - there were a few days back in July 2001 when we had ZERO tests failing! dude tell your script to stop biotching X-( I will take a plane to the UK just to kick his binary ass ...the template for this email is in CVS - so feel free to change it yourself... power to the people... Chris = Need somewhere to Live in London? - Then go to http://freeflats.com __ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
...the template for this email is in CVS - so feel free to change it yourself... power to the people... A taste of my own medicine? You are making progress. What we really need to remove is the XA test that throws Error as a standard result ?:| and __ View: http://jboss.org/forums/thread.jsp?forum=66thread=4926 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
on 1-12-08 11.29, Chris Kimpton at [EMAIL PROTECTED] wrote: javac is in the classpath - is there something I can change in my config to correct this? I believe I have an empty CLASSPATH when starting the jboss tests - so it should just be what jboss/ant adds... I think Julian is looking at adding the javac to the classpath programatically instead of forcing all of us to copy tools.jar to /lib/ext/ or maybe we could ask buildmagic to do it for us ? ... /peter_f ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
[EMAIL PROTECTED] wrote:
Hi,
Errors:1
Failures: 2
missing that XA is not a valid test *now* (Error) therefore it
should be
removed - and if javac is in the classpath the other 2 is cleared
as well
javac is in the classpath - is there something I can change in my
config to correct this? I believe I have an empty CLASSPATH when
starting the jboss tests - so it should just be what jboss/ant
adds...
actually javac (tools.jar) has to be in the jboss-service.xml file AND
in the lib/ext dir. Just being in the classpath didn't work for me. we
could change the build script slightly to work.
in my build script i changed
/jboss-all/server/src/etc/conf/default/jboss-service.xml by adding
tools.jar to the classpath element. then in my build script in the
_module-j2ee-most I added the following:
!-- copy the tools.jar to lib/ext --
copy file=${java.home}/../lib/tools.jar
tofile=${install.lib.ext}/tools.jar /
and now it just copies my tools.jar for me.
I can check this in , its so simple I don't know why it hasn't been done
before :)
Now the xatest, not sure there is an easy way around this other than not
running that test... Its not really an invalid test though. There just
is not an xa capabale datasource anymore (instantDB no longer being free)
Al
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
why not just do it in build.xml? [EMAIL PROTECTED] wrote: on 1-12-08 11.29, Chris Kimpton at [EMAIL PROTECTED] wrote: I think Julian is looking at adding the javac to the classpath programatically instead of forcing all of us to copy tools.jar to /lib/ext/ or maybe we could ask buildmagic to do it for us ? ... /peter_f ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
- Original Message -
From: Allen Fogleson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Saturday, December 08, 2001 9:04 AM
Subject: Re: [JBoss-dev] Automated JBoss Testsuite Results
javac is in the classpath - is there something I can change in my
config to correct this? I believe I have an empty CLASSPATH when
starting the jboss tests - so it should just be what jboss/ant
adds...
actually javac (tools.jar) has to be in the jboss-service.xml file AND
in the lib/ext dir. Just being in the classpath didn't work for me. we
could change the build script slightly to work.
in my build script i changed
/jboss-all/server/src/etc/conf/default/jboss-service.xml by adding
tools.jar to the classpath element. then in my build script in the
_module-j2ee-most I added the following:
!-- copy the tools.jar to lib/ext --
copy file=${java.home}/../lib/tools.jar
tofile=${install.lib.ext}/tools.jar /
and now it just copies my tools.jar for me.
I can check this in , its so simple I don't know why it hasn't been done
before :)
Because this depends on which JVM your are using and the setting your
proposing does not work in general. On OS X the javac compiler is in the
/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Classes/clas
ses.jar
The javac compiler can to be added to the system classpath of the server by
the
start script and does not need to be copied into the JBoss distribution.
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Ohh yeah stupid me... I forgot about OS X. The one OS I cant test it on :) Ahh well I said it was so simple there had to be a reason it wasnt done before. Because this depends on which JVM your are using and the setting your proposing does not work in general. On OS X the javac compiler is in the /System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Classes/clas ses.jar ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
on 1-12-08 18.04, Allen Fogleson at [EMAIL PROTECTED] wrote:
in my build script i changed
/jboss-all/server/src/etc/conf/default/jboss-service.xml by adding
tools.jar to the classpath element. then in my build script in the
_module-j2ee-most I added the following:
!-- copy the tools.jar to lib/ext --
copy file=${java.home}/../lib/tools.jar
tofile=${install.lib.ext}/tools.jar /
and now it just copies my tools.jar for me.
I can check this in , its so simple I don't know why it hasn't been done
before :)
please do as an interim solution ...
Now the xatest, not sure there is an easy way around this other than not
running that test... Its not really an invalid test though. There just
is not an xa capabale datasource anymore (instantDB no longer being free)
Yes - valid but not now - could You while the patient is open locate the
code that runs it and disable it for now ? ...
as for tools.jar could We use kaffe.org GLP licenced javac ?
/peter_f
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
[EMAIL PROTECTED] wrote: on 1-12-08 18.04, Allen Fogleson at [EMAIL PROTECTED] wrote: please do as an interim solution ... actually scott pointed out that it wont work for OS X For some reason tools.jar wasnt in my classpath when I tested before. it does work if it is... so I think Chris could change his script pretty easily for the WebIntegration tests to pass. Yes - valid but not now - could You while the patient is open locate the code that runs it and disable it for now ? ... Im actually doing that now. as for tools.jar could We use kaffe.org GLP licenced javac ? I havent tried kaffe. It would be an alternative I imagine. :) Al ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Point JAVA_HOME to a JDK distribution that is compatible with the Sun layout(has javac in lib/tools.jar) and this is included in the system classpath by the run.bat and run.sh start scripts. If no such VM is available, explicitly set JAVAC_JAR to the compiler jar. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Allen Fogleson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Saturday, December 08, 2001 10:08 AM Subject: Re: [JBoss-dev] Automated JBoss Testsuite Results [EMAIL PROTECTED] wrote: on 1-12-08 18.04, Allen Fogleson at [EMAIL PROTECTED] wrote: please do as an interim solution ... actually scott pointed out that it wont work for OS X For some reason tools.jar wasnt in my classpath when I tested before. it does work if it is... so I think Chris could change his script pretty easily for the WebIntegration tests to pass. Yes - valid but not now - could You while the patient is open locate the code that runs it and disable it for now ? ... Im actually doing that now. as for tools.jar could We use kaffe.org GLP licenced javac ? I havent tried kaffe. It would be an alternative I imagine. :) Al ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Hi, --- Scott M Stark [EMAIL PROTECTED] wrote: Point JAVA_HOME to a JDK distribution that is compatible with the Sun layout(has javac in lib/tools.jar) and this is included in the system classpath by the run.bat and run.sh start scripts. ...but I am using the sun, ibm and blackdown jdks - which confirm to the above. I also run with run.sh (via jboss_init_redhat.sh). Chris = Need somewhere to Live in London? - Then go to http://freeflats.com __ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
JBoss daily test results SUMMARY Number of tests run: 162 Successful tests: 159 Errors:1 Failures: 2 we are almost there it seems PPS Come on people - there were a few days back in July 2001 when we had ZERO tests failing! dude tell your script to stop biotching X-( I will take a plane to the UK just to kick his binary ass __ View: http://jboss.org/forums/thread.jsp?forum=66thread=4926 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
JBoss daily test results SUMMARY Number of tests run: 162 Successful tests: 159 Errors:1 Failures: 2 we are almost there it seems Yes - out of 162 We have a 100% success rate - the above test stat is missing that XA is not a valid test *now* (Error) therefore it should be removed - and if javac is in the classpath the other 2 is cleared as well ... ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Hi, right now sars and service.xml files need to be explicitly undeployed and redeployed. This will be fixed when the undeploy responsibility goes to AutoDeployer where it belongs. Does this mean that the tests will fail until then - or is there another problem on my Testsuite run? I am re-running them at the moment to see if they work any better now... Chris = Need somewhere to Live in London? - Then go to http://freeflats.com __ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
David, I did a small hack to DeployerMBeanSupport that calls undeploy instead of sending the message. My motivation was laziness when redeploying modified SARs. This seems to work fine in my tests, including suspending dependent services, except... The classloader in the SarDeployerInfo is not being garbage collected. I haven't tracked down the problem yet. NOTE: This problem occurs using your method without my hack. Regards, Adrian View: http://jboss.org/forums/thread.jsp?forum=66thread=4926 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
On 2001.12.06 07:12:48 -0500 Chris Kimpton wrote: Hi, right now sars and service.xml files need to be explicitly undeployed and redeployed. This will be fixed when the undeploy responsibility goes to AutoDeployer where it belongs. Does this mean that the tests will fail until then - or is there another problem on my Testsuite run? I think there must be another problem. This hasn't changed for a couple of months. Also, tests need to make sure to undeploy anything they deploy, either using setup/teardown or a finally block in the test code. Each test run involves recompiling and rerunning the server on the specified jvm, right? david I am re-running them at the moment to see if they work any better now... Chris = Need somewhere to Live in London? - Then go to http://freeflats.com __ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
on 1-12-06 13.12, Chris Kimpton at [EMAIL PROTECTED] wrote: Does this mean that the tests will fail until then - or is there another problem on my Testsuite run? No i do not think so ... that behaivior has been there some time ... but the new log4j.RollingFileAppender might need a bigger number in its properties ? ... or u could copy in all server.log(s) to the site ... /peter_f ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
The problems are caused by the build scripts. jboss-xa.rar and jboss-jdbc.rar are missing from deploy/lib. View: http://jboss.org/forums/thread.jsp?forum=66thread=4926 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
chris, I am looking at the results right now, I got a bit rusty on the latest build.xml test so I am swimming upstream, it seems on cursory look that NOTHING is deployed at all, I mean the log is full of not found not found something is very wrong in the setup. I assume you do a straight clean co with rebuild? could you remove everyone and really start from what is in CVS so I can work on the errors? - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - View Thread: http://jboss.org/forums/thread.jsp?forum=66thread=4926 Reply to Message: http://jboss.org/forums/post.jsp?forum=66thread=4926message=355485reply=true ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
SUMMARY Number of tests run: 186 Successful tests: 73 Errors:105 Failures: 8 pfff, I am done compiling the server, of course nothing runs but if the stuff that is supposed to run throws 105 errors I am really up shit creek without a paddle X-( ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Hrm... I did not actually test the testsuite with new build system... could be my fault... --jason On Wed, 5 Dec 2001, marc fleury wrote: SUMMARY Number of tests run: 186 Successful tests: 73 Errors:105 Failures: 8 pfff, I am done compiling the server, of course nothing runs but if the stuff that is supposed to run throws 105 errors I am really up shit creek without a paddle X-( ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
I just tried the testsuite (ala ./build/build.sh run-basic-testsuite with a ./build/build.sh run-jboss instance) and I am seeing errors about DefaultDS not bound. I just checked JNDIView and I don't see it anywhere. I tried touching hsqldb-default-service.xml, and got a very unhelpful log message: 21:40:35,854 INFO [AutoDeployer] Auto deploy of file:/nfs/home/jason/ws/jboss/jboss-all/build/output/jboss-3.0.0alpha/deploy/hsqldb-default-service.xml 21:40:35,855 INFO [ServiceDeployer] not deploying package because it is already deployed: file:/nfs/home/jason/ws/jboss/jboss-all/build/output/jboss-3.0.0alpha/deploy/hsqldb-default-service.xml I guess I would have expected it to undeploy and redeploy when touched. Just tried moving this file to hsqldb.xml, which looks like it shutit down, but I don't see it starting back up. Also, looks like the removing class bits should be logged at DEBUG or TRACE, right now they come off as INFO (probably a System.out too). What is up with DefaultDS? It could still be a problem which I enduced, but I am too unfamilar with this 3.0 bliss to make any sence of it. --jason JBoss Forums: JBoss Development: [JBoss-dev] Automated JBoss Testsuite Results View: http://jboss.org/forums/thread.jsp?forum=66thread=4926 Reply: http://jboss.org/forums/post.jsp?forum=66thread=4926message=355662reply=true ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Ok time to clean, the core build doesn't work when I run due to the service.xml pointing to a thousand things in classpath,but tonight I am going to bed and I will work on this tomorrow, JBoss Forums: JBoss Development View: http://jboss.org/forums/thread.jsp?forum=66thread=4926 Reply: http://jboss.org/forums/post.jsp?forum=66thread=4926message=355667reply=true ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
on 1-12-06 06.29, Jason Dillon at [EMAIL PROTECTED] wrote: What is up with DefaultDS? lubega.com is not writing out its server log in full -for the last test's -so i do not know ... hth /peter_f ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
I tried touching hsqldb-default-service.xml, and got a very unhelpful log message: 21:40:35,854 INFO [AutoDeployer] Auto deploy of file:/nfs/home/jason/ws/jboss/jboss-all/build/output/j oss-3.0.0alpha/deploy/hsqldb-default-service.xml 21:40:35,855 INFO [ServiceDeployer] not deploying package because it is already deployed: file:/nfs/home/jason/ws/jboss/jboss-all/build/output/j oss-3.0.0alpha/deploy/hsqldb-default-service.xml I guess I would have expected it to undeploy and redeploy when touched. ahhh ... that is a feature of the deployer ... You need to drag it out of the deploy folder - and back in (after a while) - i use the conf folder as a temp place ... View: http://jboss.org/forums/thread.jsp?forum=66thread=4926 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
On 2001.12.06 00:29:28 -0500 Jason Dillon wrote: I just tried the testsuite (ala ./build/build.sh run-basic-testsuite with a ./build/build.sh run-jboss instance) and I am seeing errors about DefaultDS not bound. I just checked JNDIView and I don't see it anywhere. I tried touching hsqldb-default-service.xml, and got a very unhelpful log message: 21:40:35,854 INFO [AutoDeployer] Auto deploy of file:/nfs/home/jason/ws/jboss/jboss-all/build/output/jboss-3.0.0alpha/deploy/hsqldb-default-service.xml 21:40:35,855 INFO [ServiceDeployer] not deploying package because it is already deployed: file:/nfs/home/jason/ws/jboss/jboss-all/build/output/jboss-3.0.0alpha/deploy/hsqldb-default-service.xml I guess I would have expected it to undeploy and redeploy when touched. right now sars and service.xml files need to be explicitly undeployed and redeployed. This will be fixed when the undeploy responsibility goes to AutoDeployer where it belongs. david jencks Just tried moving this file to hsqldb.xml, which looks like it shutit down, but I don't see it starting back up. Also, looks like the removing class bits should be logged at DEBUG or TRACE, right now they come off as INFO (probably a System.out too). What is up with DefaultDS? It could still be a problem which I enduced, but I am too unfamilar with this 3.0 bliss to make any sence of it. --jason JBoss Forums: JBoss Development: [JBoss-dev] Automated JBoss Testsuite Results View: http://jboss.org/forums/thread.jsp?forum=66thread=4926 Reply: http://jboss.org/forums/post.jsp?forum=66thread=4926message=355662reply=true ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Automated JBoss Testsuite Results
OK let's make this work bit by bit |Number of tests run: 130 | | | |Successful tests: 121 | |Errors:4 | |Failures: 5 | | |DETAILS OF ERRORS | |[details not shown - as this makes the mail too big to reach the |sf mailing list] | | | |PS BEFORE you commit, run the test suite. Its easy, just run the |target 'run-basic-testsuite' from the main build.xml. yeah IS THERE A WAY TO RUN THIS WITHOUT THE BUILD (man...) I *just* want to run the freaking testbean stuff just to make sure the JMX detaching doesn't break the functionality and right now I am getting an headache just looking at the build xml files from Jason :( |PPS Come on people - there were a few days back in July 2001 when |we had ZERO tests failing! Yeah we will get back there eventually, will take some effort. marcf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
In the testsuite directory, ./build.sh tests-unit The build scripts aren't quite as complicated as they look at first ;-) david jencks On 2001.10.30 20:48:49 -0500 marc fleury wrote: OK let's make this work bit by bit |Number of tests run: 130 | | | |Successful tests: 121 | |Errors:4 | |Failures: 5 | | |DETAILS OF ERRORS | |[details not shown - as this makes the mail too big to reach the |sf mailing list] | | | |PS BEFORE you commit, run the test suite. Its easy, just run the |target 'run-basic-testsuite' from the main build.xml. yeah IS THERE A WAY TO RUN THIS WITHOUT THE BUILD (man...) I *just* want to run the freaking testbean stuff just to make sure the JMX detaching doesn't break the functionality and right now I am getting an headache just looking at the build xml files from Jason :( |PPS Come on people - there were a few days back in July 2001 when |we had ZERO tests failing! Yeah we will get back there eventually, will take some effort. marcf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
on 1-10-26 06.30, [EMAIL PROTECTED] at [EMAIL PROTECTED] wrote: JBoss daily test results SUMMARY Number of tests run: 130 Successful tests: 121 Errors:4 Failures: 5 [time of test: 26 October 2001 5:27 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1-FCS] [java.vm.name: Classic VM] [java.vm.info: green threads, nojit] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-6] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS [details not shown - as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite. Its easy, just run the target 'run-basic-testsuite' from the main build.xml. PPS Come on people - there were a few days back in July 2001 when we had ZERO tests failing! Oh, and thanks - remember we love you too! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development How come We run 130 with green ??? ... /peter_f ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Hi, How come We run 130 with green ??? ... A bit of a non-answer ... I don't know - presumably something to do with some tests failing to start properly with the green thread model... but it should be the same ;-) Chris = Need somewhere to Live in London? - Then go to http://freeflats.com __ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Hi, --- Hiram Chirino [EMAIL PROTECTED] wrote: So should I change my default?? I need to good port numbers for JBossMQ?? Scott, Any ideas?? I've changed my test webserver to use port 8030 - so feel free to leave it at 8090/8091 as far as I am concerned. Chris On Mon, Oct 22, 2001 at 08:20:55AM -0400, Hiram Chirino wrote: I just looked up why JBossMQ is failing for the lubega system. Since I just added the feature that lets an app connect to MQ without needing JNDI, I had to pin down the port that the OIL and UIL listen to. I picked ports 8090 and 8091. Seems like something allready has 8090 bound on the lubega machine. Are those bad choices for port numbers?? Regards, Hiram = Need somewhere to Live in London - http://freeflats.com __ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
I just looked up why JBossMQ is failing for the lubega system. Since I just added the feature that lets an app connect to MQ without needing JNDI, I had to pin down the port that the OIL and UIL listen to. I picked ports 8090 and 8091. Seems like something allready has 8090 bound on the lubega machine. Are those bad choices for port numbers?? Regards, Hiram From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [JBoss-dev] Automated JBoss Testsuite Results Date: Sun, 21 Oct 2001 03:17:18 +0100 JBoss daily test results SUMMARY Number of tests run: 140 Successful tests: 129 Errors:5 Failures: 6 [time of test: 21 October 2001 3:16 GMT] [java.version: 1.3.0] [java.vendor: IBM Corporation] [java.vm.version: 1.3.0] [java.vm.name: Classic VM] [java.vm.info: J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)] [os.name: Linux] [os.arch: x86] [os.version: 2.4.9-6] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS [details not shown - as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite. PPS Come on people - there were a few days back in July 2001 when we had ZERO tests failing! Oh, and thanks - remember we love you too! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
So should I change my default?? I need to good port numbers for JBossMQ?? Scott, Any ideas?? Regards, Hiram From: Neale Swinnerton [EMAIL PROTECTED] To: Hiram Chirino [EMAIL PROTECTED] Subject: Re: [JBoss-dev] Automated JBoss Testsuite Results Date: Mon, 22 Oct 2001 13:57:31 +0100 If I recall correctly Chris was asking about changing the default Jetty port to 8090 'cos he already had something running on 8080. I guess you both decided that 8090 was a good alternative :-) -- regards Neale Swinnerton On Mon, Oct 22, 2001 at 08:20:55AM -0400, Hiram Chirino wrote: I just looked up why JBossMQ is failing for the lubega system. Since I just added the feature that lets an app connect to MQ without needing JNDI, I had to pin down the port that the OIL and UIL listen to. I picked ports 8090 and 8091. Seems like something allready has 8090 bound on the lubega machine. Are those bad choices for port numbers?? Regards, Hiram _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Tests that timeout generate no testcase xml results and are (I think) not counted. This happens on my local machine, I don't know if it is causing these count differences. david jencks On 2001.09.30 00:06:15 -0400 Jason Dillon wrote: Why does the number of tests run vary from vm to vm? --jason On Sun, 30 Sep 2001 [EMAIL PROTECTED] wrote: JBoss daily test results SUMMARY Number of tests run: 113 Successful tests: 92 Errors:19 Failures: 2 [time of test: 30 September 2001 3:16 GMT] [java.version: 1.3.0] [java.vendor: IBM Corporation] [java.vm.version: 1.3.0] [java.vm.name: Classic VM] [java.vm.info: J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)] [os.name: Linux] [os.arch: x86] [os.version: 2.4.3-12] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS [details not shown - as this makes the mail too big to reach the sf mailing list] ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Is there any easy way to track how mant tests there are outside of this? I don't really know how many tests there are. It would be good to know what coverage we arte getting and what we are missing due to tool errors or timeouts. --jason On Sun, 30 Sep 2001, David Jencks wrote: Tests that timeout generate no testcase xml results and are (I think) not counted. This happens on my local machine, I don't know if it is causing these count differences. david jencks On 2001.09.30 00:06:15 -0400 Jason Dillon wrote: Why does the number of tests run vary from vm to vm? --jason On Sun, 30 Sep 2001 [EMAIL PROTECTED] wrote: JBoss daily test results SUMMARY Number of tests run: 113 Successful tests: 92 Errors:19 Failures: 2 [time of test: 30 September 2001 3:16 GMT] [java.version: 1.3.0] [java.vendor: IBM Corporation] [java.vm.version: 1.3.0] [java.vm.name: Classic VM] [java.vm.info: J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)] [os.name: Linux] [os.arch: x86] [os.version: 2.4.3-12] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS [details not shown - as this makes the mail too big to reach the sf mailing list] ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Why does the number of tests run vary from vm to vm? --jason On Sun, 30 Sep 2001 [EMAIL PROTECTED] wrote: JBoss daily test results SUMMARY Number of tests run: 113 Successful tests: 92 Errors:19 Failures: 2 [time of test: 30 September 2001 3:16 GMT] [java.version: 1.3.0] [java.vendor: IBM Corporation] [java.vm.version: 1.3.0] [java.vm.name: Classic VM] [java.vm.info: J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)] [os.name: Linux] [os.arch: x86] [os.version: 2.4.3-12] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS [details not shown - as this makes the mail too big to reach the sf mailing list] ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Automated JBoss Testsuite Results
Hi, From: Sacha Labourey [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Automated JBoss Testsuite Results Date: Mon, 24 Sep 2001 10:24:43 +0200 Hello Chris, Are you sure the system is correctly running? I am sure it is not running correctly ;-) It seems I need to be more aggressive at ensuring the previous jboss run finished ok - this seems to be the main problem at the moment - the previous run has hung - so when the next one starts, the server fails to start up properly - and we get the reduced test results... When I go on lubega.com web page, many links are not reachable = I cannot see what are the problems with the current build. The archives are the main place to find the old results - because of the above problems the job is still running - 8hours and still going - so the current reports are being built still... Thank you. Cheers, Sacha -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de [EMAIL PROTECTED] Envoyé : lundi, 24 septembre 2001 10:20 À : [EMAIL PROTECTED] Objet : [JBoss-dev] Automated JBoss Testsuite Results JBoss daily test results SUMMARY Number of tests run: 21 Successful tests: 16 Errors:5 Failures: 0 [time of test: 24 September 2001 9:18 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1-FCS] [java.vm.name: Classic VM] [java.vm.info: green threads, nojit] [os.name: Linux] [os.arch: i386] [os.version: 2.4.3-12] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS [details not shown - as this makes the mail too big to reach the sf mailing list] ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Automated JBoss Testsuite Results
|When I go on lubega.com web page, many links are not reachable = I |cannot see what are the problems with the current build. | |The archives are the main place to find the old results - because of |the above problems the job is still running - 8hours and still going |- so the current reports are being built still... My goal this week is to rework the current website with the updated navigation and information but I would want to spend some time on the dev as well. My first goal has to do with the test... we need to get the test count up to max if we want to move forward with new features. marcf | |Thank you. Cheers, | | | | Sacha | | | | -Message d'origine- | De : [EMAIL PROTECTED] | [mailto:[EMAIL PROTECTED]]De la part |de [EMAIL PROTECTED] | Envoyé : lundi, 24 septembre 2001 10:20 | À : [EMAIL PROTECTED] | Objet : [JBoss-dev] Automated JBoss Testsuite Results | | | | | JBoss daily test results | | SUMMARY | | Number of tests run: 21 | | | | Successful tests: 16 | | Errors:5 | | Failures: 0 | | | | | | [time of test: 24 September 2001 9:18 GMT] | [java.version: 1.3.1] | [java.vendor: Blackdown Java-Linux Team] | [java.vm.version: Blackdown-1.3.1-FCS] | [java.vm.name: Classic VM] | [java.vm.info: green threads, nojit] | [os.name: Linux] | [os.arch: i386] | [os.version: 2.4.3-12] | | See http://lubega.com for full details | | NOTE: If there are any errors shown above - this mail is only | highlighting | them - it is NOT indicating that they are being looked at by |anyone. | It is assumed that whoever makes change(s) to jboss that | break the test will be fixing the test or jboss, as appropriate! | | | | | | DETAILS OF ERRORS | | [details not shown - as this makes the mail too big to reach the | sf mailing list] | | | | ___ | Jboss-development mailing list | [EMAIL PROTECTED] | https://lists.sourceforge.net/lists/listinfo/jboss-development | | | |_ |Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Well I'm glad at least some of them are coming through matching more or less what I get here... I imagine you already know this, I have found that if jboss hangs on shutdown sending it SIGABRT kills it without leaving all the ports it is using permanently disabled. Do you happen to know it there is some way to release ports held by a crashed and killed program? Until I found the SIGABRT I had to reboot several times. Thanks david jencks On 2001.09.24 05:23:57 -0400 Chris Kimpton wrote: Hi, From: Sacha Labourey [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Automated JBoss Testsuite Results Date: Mon, 24 Sep 2001 10:24:43 +0200 Hello Chris, Are you sure the system is correctly running? I am sure it is not running correctly ;-) It seems I need to be more aggressive at ensuring the previous jboss run finished ok - this seems to be the main problem at the moment - the previous run has hung - so when the next one starts, the server fails to start up properly - and we get the reduced test results... When I go on lubega.com web page, many links are not reachable = I cannot see what are the problems with the current build. The archives are the main place to find the old results - because of the above problems the job is still running - 8hours and still going - so the current reports are being built still... Thank you. Cheers, Sacha -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de [EMAIL PROTECTED] Envoyé : lundi, 24 septembre 2001 10:20 À : [EMAIL PROTECTED] Objet : [JBoss-dev] Automated JBoss Testsuite Results JBoss daily test results SUMMARY Number of tests run: 21 Successful tests: 16 Errors:5 Failures: 0 [time of test: 24 September 2001 9:18 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1-FCS] [java.vm.name: Classic VM] [java.vm.info: green threads, nojit] [os.name: Linux] [os.arch: i386] [os.version: 2.4.3-12] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS [details not shown - as this makes the mail too big to reach the sf mailing list] ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Hi, --- David Jencks [EMAIL PROTECTED] wrote: I imagine you already know this, I have found that if jboss hangs on shutdown sending it SIGABRT kills it without leaving all the ports it is using permanently disabled. What I am doing in the tests is to try shutting it down with org.jboss.Shutdown. If that fails (which it always does at the moment), I then do a kill -9 (SIGKILL) - but even this seems to sometimes fail - or my algorithm in unix script for determining the root java process maybe failing ;-) Do you happen to know it there is some way to release ports held by a crashed and killed program? Until I found the SIGABRT I had to reboot several times. I don't really see this affect - I can either see the process is still there - and then I can kill -9 it - or its not there, in which case, I can start a new jboss, no worries. I've not rebooted the box for 37 days. Chris = Need somewhere to Live in London - http://freeflats.com __ Do You Yahoo!? Get email alerts NEW webcam video instant messaging with Yahoo! Messenger. http://im.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Automated JBoss Testsuite Results
what is great about it is that if we wait a bit it gets better :) the more days go by the more tests we run... I really try to get them to 111 soon marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of |[EMAIL PROTECTED] |Sent: Monday, September 24, 2001 10:28 PM |To: [EMAIL PROTECTED] |Subject: [JBoss-dev] Automated JBoss Testsuite Results | | | | |JBoss daily test results | |SUMMARY | |Number of tests run: 111 | | | |Successful tests: 89 | |Errors:19 | |Failures: 3 | | | | | |[time of test: 25 September 2001 3:27 GMT] |[java.version: 1.3.0] |[java.vendor: IBM Corporation] |[java.vm.version: 1.3.0] |[java.vm.name: Classic VM] |[java.vm.info: J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)] |[os.name: Linux] |[os.arch: x86] |[os.version: 2.4.3-12] | |See http://lubega.com for full details | |NOTE: If there are any errors shown above - this mail is only highlighting |them - it is NOT indicating that they are being looked at by anyone. | |It is assumed that whoever makes change(s) to jboss that |break the test will be fixing the test or jboss, as appropriate! | | | | | |DETAILS OF ERRORS | |[details not shown - as this makes the mail too big to reach the |sf mailing list] | | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Hi, From: David Jencks [EMAIL PROTECTED] Having these tests back is wonderful but... WHATS GOING ON? the test script appears to be assuming every class whose name begins with Test is a test-- does this mean I have to rewrite my tests to rename the ejbs and mbeans that I happened to name e.g. TestSomethingMBean? Couldn't we only assume classes are tests if they are in a .../test/xxx/test/ directory? Also, there is some kind of security exception from rmi making even less information come back from the server than previously. Anyone know what this is about? (cf eg jmx/test/TestConnectionFactoryLoader) I think the testsuite/test run ant scripts need some work to include/exclude the right stuff - and/or to follow some naming convention - I think Jason mentioned this a few weeks back... Chris _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Tests often include utility classes in the same directory so just assuming everything is a test case is not valid. The unit test class naming conventions allow for: Test*.class *Test.class Main.class AllJUnitTests.class - Original Message - From: Chris Kimpton [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, September 05, 2001 7:08 AM Subject: Re: [JBoss-dev] Automated JBoss Testsuite Results Hi, From: David Jencks [EMAIL PROTECTED] Having these tests back is wonderful but... WHATS GOING ON? the test script appears to be assuming every class whose name begins with Test is a test-- does this mean I have to rewrite my tests to rename the ejbs and mbeans that I happened to name e.g. TestSomethingMBean? Couldn't we only assume classes are tests if they are in a .../test/xxx/test/ directory? Also, there is some kind of security exception from rmi making even less information come back from the server than previously. Anyone know what this is about? (cf eg jmx/test/TestConnectionFactoryLoader) I think the testsuite/test run ant scripts need some work to include/exclude the right stuff - and/or to follow some naming convention - I think Jason mentioned this a few weeks back... Chris ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
Can we rename, so that all test end with *Test.class, or *TestCase.class? I was looking into some of the errors yesterday, but did not really have any energy to do anything about it. I saw a few interfaces were thought to be tests and some odd naming problems. I also didn't see all of the tests on the output page again. --jason On Wed, 5 Sep 2001, Scott M Stark wrote: Tests often include utility classes in the same directory so just assuming everything is a test case is not valid. The unit test class naming conventions allow for: Test*.class *Test.class Main.class AllJUnitTests.class - Original Message - From: Chris Kimpton [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, September 05, 2001 7:08 AM Subject: Re: [JBoss-dev] Automated JBoss Testsuite Results Hi, From: David Jencks [EMAIL PROTECTED] Having these tests back is wonderful but... WHATS GOING ON? the test script appears to be assuming every class whose name begins with Test is a test-- does this mean I have to rewrite my tests to rename the ejbs and mbeans that I happened to name e.g. TestSomethingMBean? Couldn't we only assume classes are tests if they are in a .../test/xxx/test/ directory? Also, there is some kind of security exception from rmi making even less information come back from the server than previously. Anyone know what this is about? (cf eg jmx/test/TestConnectionFactoryLoader) I think the testsuite/test run ant scripts need some work to include/exclude the right stuff - and/or to follow some naming convention - I think Jason mentioned this a few weeks back... Chris ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
*TestCase is fine with me. - Original Message - From: Jason Dillon [EMAIL PROTECTED] To: Scott M Stark [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, September 05, 2001 12:55 PM Subject: Re: [JBoss-dev] Automated JBoss Testsuite Results Can we rename, so that all test end with *Test.class, or *TestCase.class? I was looking into some of the errors yesterday, but did not really have any energy to do anything about it. I saw a few interfaces were thought to be tests and some odd naming problems. I also didn't see all of the tests on the output page again. --jason ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss Testsuite Results
I plan on getting to this shortly. I want to create a JBossTestSuite and force all tests to extend from it at the same time. --jason On Wed, 5 Sep 2001, Scott M Stark wrote: *TestCase is fine with me. - Original Message - From: Jason Dillon [EMAIL PROTECTED] To: Scott M Stark [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, September 05, 2001 12:55 PM Subject: Re: [JBoss-dev] Automated JBoss Testsuite Results Can we rename, so that all test end with *Test.class, or *TestCase.class? I was looking into some of the errors yesterday, but did not really have any energy to do anything about it. I saw a few interfaces were thought to be tests and some odd naming problems. I also didn't see all of the tests on the output page again. --jason ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
