[JBoss-dev] RE: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors
Rajesh, can we put jboss-head at the end? If there is only one failure on jboss-head, perhaps we could raise the issue for the portal team to fix. Having Portal 2.4 compatible with Jboss 5.0 would be a nice thing to have if it's easy. If it's a big deal to fix, we should remove jboss-head from the matrix so we can have a clean build. -Original Message- From: Julien Viet Sent: Wednesday, February 22, 2006 3:38 PM To: Rajesh Rajasekaran Cc: QA; Anil Saldhana; [EMAIL PROTECTED]; Chris Laprun; jboss-development@lists.sourceforge.net; QA; Julien Viet; [EMAIL PROTECTED]; Thomas Heute Subject: Re: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors jboss-head (JBoss 5) is not today a target for us but we can test it of course. Here is the list that I would like to see : - Branch_4_0 - 4.0.4RC1 (later 4.0.4) - 4.0.3SP1 (already done) --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] RE: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors
I will put jboss-head to the end and rearrange the list as Julien had requested. The portlet tests against jboss-head had failed and the report XML's were not well-formed, hence the failures not reported by CC. I have opened a task for this. Here s the link. http://jira.jboss.com/jira/browse/JBPORTAL-679 Thanks Rajesh -Original Message- From: Ryan Campbell Sent: Wednesday, February 22, 2006 3:54 PM To: Julien Viet; Rajesh Rajasekaran Cc: QA; jboss-development@lists.sourceforge.net Subject: RE: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors Rajesh, can we put jboss-head at the end? If there is only one failure on jboss-head, perhaps we could raise the issue for the portal team to fix. Having Portal 2.4 compatible with Jboss 5.0 would be a nice thing to have if it's easy. If it's a big deal to fix, we should remove jboss-head from the matrix so we can have a clean build. -Original Message- From: Julien Viet Sent: Wednesday, February 22, 2006 3:38 PM To: Rajesh Rajasekaran Cc: QA; Anil Saldhana; [EMAIL PROTECTED]; Chris Laprun; jboss-development@lists.sourceforge.net; QA; Julien Viet; [EMAIL PROTECTED]; Thomas Heute Subject: Re: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors jboss-head (JBoss 5) is not today a target for us but we can test it of course. Here is the list that I would like to see : - Branch_4_0 - 4.0.4RC1 (later 4.0.4) - 4.0.3SP1 (already done) --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors
We target JBoss Portal 3.0.x to work on JBoss 5. However as you say it would be a good thing, still I don't know when JBoss 5 will be released (alpha was scheduled for 1 month ago). Ryan Campbell wrote: Rajesh, can we put jboss-head at the end? If there is only one failure on jboss-head, perhaps we could raise the issue for the portal team to fix. Having Portal 2.4 compatible with Jboss 5.0 would be a nice thing to have if it's easy. If it's a big deal to fix, we should remove jboss-head from the matrix so we can have a clean build. -Original Message- From: Julien Viet Sent: Wednesday, February 22, 2006 3:38 PM To: Rajesh Rajasekaran Cc: QA; Anil Saldhana; [EMAIL PROTECTED]; Chris Laprun; jboss-development@lists.sourceforge.net; QA; Julien Viet; [EMAIL PROTECTED]; Thomas Heute Subject: Re: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors jboss-head (JBoss 5) is not today a target for us but we can test it of course. Here is the list that I would like to see : - Branch_4_0 - 4.0.4RC1 (later 4.0.4) - 4.0.3SP1 (already done) -- Julien Viet JBoss Portal Project Lead --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors
it looks that the file is truncated, what is the reason of that ? Rajesh Rajasekaran wrote: I will put jboss-head to the end and rearrange the list as Julien had requested. The portlet tests against jboss-head had failed and the report XML's were not well-formed, hence the failures not reported by CC. I have opened a task for this. Here s the link. http://jira.jboss.com/jira/browse/JBPORTAL-679 Thanks Rajesh -Original Message- From: Ryan Campbell Sent: Wednesday, February 22, 2006 3:54 PM To: Julien Viet; Rajesh Rajasekaran Cc: QA; jboss-development@lists.sourceforge.net Subject: RE: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors Rajesh, can we put jboss-head at the end? If there is only one failure on jboss-head, perhaps we could raise the issue for the portal team to fix. Having Portal 2.4 compatible with Jboss 5.0 would be a nice thing to have if it's easy. If it's a big deal to fix, we should remove jboss-head from the matrix so we can have a clean build. -Original Message- From: Julien Viet Sent: Wednesday, February 22, 2006 3:38 PM To: Rajesh Rajasekaran Cc: QA; Anil Saldhana; [EMAIL PROTECTED]; Chris Laprun; jboss-development@lists.sourceforge.net; QA; Julien Viet; [EMAIL PROTECTED]; Thomas Heute Subject: Re: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors jboss-head (JBoss 5) is not today a target for us but we can test it of course. Here is the list that I would like to see : - Branch_4_0 - 4.0.4RC1 (later 4.0.4) - 4.0.3SP1 (already done) -- Julien Viet JBoss Portal Project Lead --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors
how can we do to improve that (i.e fix the wellformedness) ? Rajesh Rajasekaran wrote: The junit reports (xml) for the portlet tests are not well formed. Hence the portlet test results are not accounted in the HTML reports shown. The common and format tests pass 100%. Please refer the link below for the portlet test reports. http://cruisecontrol.jboss.com/cc/artifacts/jboss-portal-2.4-testsuite/20060220170427/jboss-4.0.3SP1-logs/results/testfailures Please let me know if you have the same problem. Thanks Rajesh *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *Sent:* Monday, February 20, 2006 4:07 PM *To:* [EMAIL PROTECTED]; jboss-development@lists.sourceforge.net; QA; Julien Viet; QA *Subject:* jboss-portal-2.4-testsuite Build Completed With Testsuite Errors *Importance:* High View results here - http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.4-testsuite?log=log20060220170427 *TESTS FAILED* *Ant Error Message: */services/cruisecontrol/work/scripts/build-jboss-portal.xml:67: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:93: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:199: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures. *Date of build: *02/20/2006 17:04:27 *Time to build: *1 minute 58 seconds *Last changed: *02/20/2006 09:17:02 *Last log entry: *JBPORTAL-608 : Timed content is not serializable and raise issues in http session replication Unit Tests: (84) Total Errors and Failures: (0) All Tests Passed Modifications since last build: (first 50 of 26) 1.4 modified julien server/src/main/org/jboss/portal/server/output/cache/SoftTimedContent.java JBPORTAL-608 : Timed content is not serializable and raise issues in http session replication 1.3 modified julien server/src/main/org/jboss/portal/server/output/cache/StrongTimedContent.java JBPORTAL-608 : Timed content is not serializable and raise issues in http session replication 1.3 modified julien server/src/main/org/jboss/portal/server/output/cache/TimedContent.java JBPORTAL-608 : Timed content is not serializable and raise issues in http session replication 1.2 modified bdaw portlet/src/resources/test/test-portletinterface-war/WEB-INF/portlet.xml - JBPORTAL-672 PLT.5.2.4.4 Exceptions During Request Handling test cases 1.9 modified bdaw portlet/src/main/org/jboss/portal/test/portlet/junit/PortletTestCase.java - JBPORTAL-672 PLT.5.2.4.4 Exceptions During Request Handling test cases 1.2 modified bdaw portlet/src/main/org/jboss/portal/test/portlet/portletinterface/PortletInterfaceTestCase.java - JBPORTAL-672 PLT.5.2.4.4 Exceptions During Request Handling test cases 1.1 added bdaw portlet/src/main/org/jboss/portal/test/portlet/portletinterface/spec/ExceptionsDuringRequestHandlingControllerPortlet.java - JBPORTAL-672 PLT.5.2.4.4 Exceptions During Request Handling test cases 1.1 added bdaw portlet/src/main/org/jboss/portal/test/portlet/portletinterface/spec/PortletExceptionDuringRequestHandlingPortlet.java - JBPORTAL-672 PLT.5.2.4.4 Exceptions During Request Handling test cases 1.1 added bdaw portlet/src/main/org/jboss/portal/test/portlet/portletinterface/spec/RuntimeExceptionDuringRequestHandlingPortlet.java - JBPORTAL-672 PLT.5.2.4.4 Exceptions During Request Handling test cases 1.1 added bdaw portlet/src/main/org/jboss/portal/test/portlet/portletinterface/spec/UnavailableExceptionDuringProcessActionPortlet.java - JBPORTAL-672 PLT.5.2.4.4 Exceptions During Request Handling test cases 1.1 added bdaw portlet/src/main/org/jboss/portal/test/portlet/portletinterface/spec/UnavailableExceptionDuringRenderPortlet.java - JBPORTAL-672 PLT.5.2.4.4 Exceptions During Request Handling test cases 1.4 modified julien common/src/main/org/jboss/portal/common/net/file/FileURLNavigationProvider.java sort files when we list a sub dir to have the behavior independant of the platform 1.1 added bdaw
[JBoss-dev] RE: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors
I guess portal uses an old version of junit(from 2001). The newer version might solve the problem. Anyways these are the errors I get. [junitreport] [Fatal Error] :-1:-1: Premature end of file. [junitreport] The file /home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port al.test.portlet.dispatcher.spec.DispatcherTestCase.xml is not a valid XML document. It is possibly corrupted. [junitreport] [Fatal Error] :-1:-1: Premature end of file. [junitreport] The file /home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port al.test.portlet.portletconfig.PortletConfigTestCase.xml is not a valid XML document. It is possibly corrupted. [junitreport] [Fatal Error] :-1:-1: Premature end of file. [junitreport] The file /home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port al.test.portlet.portletinterface.PortletInterfaceTestCase.xml is not a valid XML document. It is possibly corrupted. [junitreport] [Fatal Error] :-1:-1: Premature end of file. [junitreport] The file /home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port al.test.portlet.portletmode.PortletModeTestCase.xml is not a valid XML document. It is possibly corrupted. [junitreport] [Fatal Error] :-1:-1: Premature end of file. [junitreport] The file /home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port al.test.portlet.portletrequest.PortletRequestTestCase.xml is not a valid XML document. It is possibly corrupted. [junitreport] [Fatal Error] :-1:-1: Premature end of file. [junitreport] The file /home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port al.test.portlet.portletsession.PortletSessionTestCase.xml is not a valid XML document. It is possibly corrupted. [junitreport] [Fatal Error] :-1:-1: Premature end of file. [junitreport] The file /home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port al.test.portlet.preferences.PreferencesTestCase.xml is not a valid XML document. It is possibly corrupted. [junitreport] [Fatal Error] :-1:-1: Premature end of file. [junitreport] The file /home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port al.test.portlet.renderresponse.RenderResponseTestCase.xml is not a valid XML document. It is possibly corrupted. -Original Message- From: Julien Viet Sent: Monday, February 20, 2006 4:41 PM To: Rajesh Rajasekaran Cc: QA; [EMAIL PROTECTED]; jboss-development@lists.sourceforge.net; QA; Julien Viet Subject: Re: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors how can we do to improve that (i.e fix the wellformedness) ? Rajesh Rajasekaran wrote: The junit reports (xml) for the portlet tests are not well formed. Hence the portlet test results are not accounted in the HTML reports shown. The common and format tests pass 100%. Please refer the link below for the portlet test reports. http://cruisecontrol.jboss.com/cc/artifacts/jboss-portal-2.4-testsuite/2 0060220170427/jboss-4.0.3SP1-logs/results/testfailures Please let me know if you have the same problem. Thanks Rajesh *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *Sent:* Monday, February 20, 2006 4:07 PM *To:* [EMAIL PROTECTED]; jboss-development@lists.sourceforge.net; QA; Julien Viet; QA *Subject:* jboss-portal-2.4-testsuite Build Completed With Testsuite Errors *Importance:* High View results here - http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.4-testsuit e?log=log20060220170427 *TESTS FAILED* *Ant Error Message: */services/cruisecontrol/work/scripts/build-jboss-portal.xml:67: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:93: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:199: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures. *Date of build: *02/20/2006 17:04:27 *Time to build: *1 minute 58 seconds *Last changed: *02/20/2006 09:17:02 *Last log entry: *JBPORTAL-608 : Timed content is not serializable and raise issues in http session replication Unit Tests: (84) Total Errors and Failures: (0) All Tests Passed Modifications since last build: (first 50 of 26) 1.4 modified julien server/src/main/org/jboss/portal/server/output/cache/SoftTimedContent.ja va JBPORTAL-608 : Timed content is not serializable and raise issues in http session replication 1.3 modified julien
[JBoss-dev] RE: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors
I see two things here: 1. The xml reports are empty, causing the XML validation errors. I guess no one has even looked at these yet?! 2. The Portlet test cases don't extend org.junit.TestCase, they extend java.lang.Object. That might work in your IDE, but I doubt we should expect AntRunner to put it up with it. -Original Message- From: Rajesh Rajasekaran Sent: Monday, February 20, 2006 5:22 PM To: Julien Viet Cc: QA; [EMAIL PROTECTED]; jboss-development@lists.sourceforge.net; QA Subject: RE: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors I guess portal uses an old version of junit(from 2001). The newer version might solve the problem. Anyways these are the errors I get. [junitreport] [Fatal Error] :-1:-1: Premature end of file. [junitreport] The file /home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port al.test.portlet.dispatcher.spec.DispatcherTestCase.xml is not a valid XML document. It is possibly corrupted. [junitreport] [Fatal Error] :-1:-1: Premature end of file. [junitreport] The file /home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port al.test.portlet.portletconfig.PortletConfigTestCase.xml is not a valid XML document. It is possibly corrupted. [junitreport] [Fatal Error] :-1:-1: Premature end of file. [junitreport] The file /home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port al.test.portlet.portletinterface.PortletInterfaceTestCase.xml is not a valid XML document. It is possibly corrupted. [junitreport] [Fatal Error] :-1:-1: Premature end of file. [junitreport] The file /home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port al.test.portlet.portletmode.PortletModeTestCase.xml is not a valid XML document. It is possibly corrupted. [junitreport] [Fatal Error] :-1:-1: Premature end of file. [junitreport] The file /home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port al.test.portlet.portletrequest.PortletRequestTestCase.xml is not a valid XML document. It is possibly corrupted. [junitreport] [Fatal Error] :-1:-1: Premature end of file. [junitreport] The file /home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port al.test.portlet.portletsession.PortletSessionTestCase.xml is not a valid XML document. It is possibly corrupted. [junitreport] [Fatal Error] :-1:-1: Premature end of file. [junitreport] The file /home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port al.test.portlet.preferences.PreferencesTestCase.xml is not a valid XML document. It is possibly corrupted. [junitreport] [Fatal Error] :-1:-1: Premature end of file. [junitreport] The file /home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port al.test.portlet.renderresponse.RenderResponseTestCase.xml is not a valid XML document. It is possibly corrupted. -Original Message- From: Julien Viet Sent: Monday, February 20, 2006 4:41 PM To: Rajesh Rajasekaran Cc: QA; [EMAIL PROTECTED]; jboss-development@lists.sourceforge.net; QA; Julien Viet Subject: Re: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors how can we do to improve that (i.e fix the wellformedness) ? Rajesh Rajasekaran wrote: The junit reports (xml) for the portlet tests are not well formed. Hence the portlet test results are not accounted in the HTML reports shown. The common and format tests pass 100%. Please refer the link below for the portlet test reports. http://cruisecontrol.jboss.com/cc/artifacts/jboss-portal-2.4-testsuite/2 0060220170427/jboss-4.0.3SP1-logs/results/testfailures Please let me know if you have the same problem. Thanks Rajesh *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *Sent:* Monday, February 20, 2006 4:07 PM *To:* [EMAIL PROTECTED]; jboss-development@lists.sourceforge.net; QA; Julien Viet; QA *Subject:* jboss-portal-2.4-testsuite Build Completed With Testsuite Errors *Importance:* High View results here - http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.4-testsuit e?log=log20060220170427 *TESTS FAILED* *Ant Error Message: */services/cruisecontrol/work/scripts/build-jboss-portal.xml:67: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:93: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:199: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures. *Date of build: *02/20/2006 17:04:27 *Time to build: *1 minute 58 seconds *Last changed: *02/20/2006 09:17:02 *Last log entry: *JBPORTAL-608 : Timed content is not serializable and raise issues in http session replication Unit Tests: (84) Total Errors and
[JBoss-dev] RE: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors
The xml reports are generated. The error from the junitreport task deletes the contents of the malformed xml's. -Original Message- From: Ryan Campbell Sent: Monday, February 20, 2006 5:37 PM To: Rajesh Rajasekaran; Julien Viet Cc: QA; '[EMAIL PROTECTED]'; 'jboss-development@lists.sourceforge.net' Subject: RE: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors I see two things here: 1. The xml reports are empty, causing the XML validation errors. I guess no one has even looked at these yet?! 2. The Portlet test cases don't extend org.junit.TestCase, they extend java.lang.Object. That might work in your IDE, but I doubt we should expect AntRunner to put it up with it. -Original Message- From: Rajesh Rajasekaran Sent: Monday, February 20, 2006 5:22 PM To: Julien Viet Cc: QA; [EMAIL PROTECTED]; jboss-development@lists.sourceforge.net; QA Subject: RE: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors I guess portal uses an old version of junit(from 2001). The newer version might solve the problem. Anyways these are the errors I get. [junitreport] [Fatal Error] :-1:-1: Premature end of file. [junitreport] The file /home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port al.test.portlet.dispatcher.spec.DispatcherTestCase.xml is not a valid XML document. It is possibly corrupted. [junitreport] [Fatal Error] :-1:-1: Premature end of file. [junitreport] The file /home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port al.test.portlet.portletconfig.PortletConfigTestCase.xml is not a valid XML document. It is possibly corrupted. [junitreport] [Fatal Error] :-1:-1: Premature end of file. [junitreport] The file /home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port al.test.portlet.portletinterface.PortletInterfaceTestCase.xml is not a valid XML document. It is possibly corrupted. [junitreport] [Fatal Error] :-1:-1: Premature end of file. [junitreport] The file /home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port al.test.portlet.portletmode.PortletModeTestCase.xml is not a valid XML document. It is possibly corrupted. [junitreport] [Fatal Error] :-1:-1: Premature end of file. [junitreport] The file /home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port al.test.portlet.portletrequest.PortletRequestTestCase.xml is not a valid XML document. It is possibly corrupted. [junitreport] [Fatal Error] :-1:-1: Premature end of file. [junitreport] The file /home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port al.test.portlet.portletsession.PortletSessionTestCase.xml is not a valid XML document. It is possibly corrupted. [junitreport] [Fatal Error] :-1:-1: Premature end of file. [junitreport] The file /home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port al.test.portlet.preferences.PreferencesTestCase.xml is not a valid XML document. It is possibly corrupted. [junitreport] [Fatal Error] :-1:-1: Premature end of file. [junitreport] The file /home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port al.test.portlet.renderresponse.RenderResponseTestCase.xml is not a valid XML document. It is possibly corrupted. -Original Message- From: Julien Viet Sent: Monday, February 20, 2006 4:41 PM To: Rajesh Rajasekaran Cc: QA; [EMAIL PROTECTED]; jboss-development@lists.sourceforge.net; QA; Julien Viet Subject: Re: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors how can we do to improve that (i.e fix the wellformedness) ? Rajesh Rajasekaran wrote: The junit reports (xml) for the portlet tests are not well formed. Hence the portlet test results are not accounted in the HTML reports shown. The common and format tests pass 100%. Please refer the link below for the portlet test reports. http://cruisecontrol.jboss.com/cc/artifacts/jboss-portal-2.4-testsuite/2 0060220170427/jboss-4.0.3SP1-logs/results/testfailures Please let me know if you have the same problem. Thanks Rajesh *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *Sent:* Monday, February 20, 2006 4:07 PM *To:* [EMAIL PROTECTED]; jboss-development@lists.sourceforge.net; QA; Julien Viet; QA *Subject:* jboss-portal-2.4-testsuite Build Completed With Testsuite Errors *Importance:* High View results here - http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.4-testsuit e?log=log20060220170427 *TESTS FAILED* *Ant Error Message: */services/cruisecontrol/work/scripts/build-jboss-portal.xml:67: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:93: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:199: The following error occurred while executing this line:
[JBoss-dev] Re: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors
yes they don't extend TestCase because we only use the
public static Test suite() { }
method as the class itself is not really a test but rather a suite provider.
should we make the portlet test case extends it ?
Ryan Campbell wrote:
I see two things here:
1. The xml reports are empty, causing the XML validation errors. I
guess no one has even looked at these yet?!
2. The Portlet test cases don't extend org.junit.TestCase, they extend
java.lang.Object. That might work in your IDE, but I doubt we should
expect AntRunner to put it up with it.
-Original Message-
From: Rajesh Rajasekaran
Sent: Monday, February 20, 2006 5:22 PM
To: Julien Viet
Cc: QA; [EMAIL PROTECTED]; jboss-development@lists.sourceforge.net; QA
Subject: RE: jboss-portal-2.4-testsuite Build Completed With Testsuite
Errors
I guess portal uses an old version of junit(from 2001). The newer
version might solve the problem.
Anyways these are the errors I get.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.dispatcher.spec.DispatcherTestCase.xml is not a valid
XML document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.portletconfig.PortletConfigTestCase.xml is not a valid
XML document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.portletinterface.PortletInterfaceTestCase.xml is not a
valid XML document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.portletmode.PortletModeTestCase.xml is not a valid XML
document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.portletrequest.PortletRequestTestCase.xml is not a valid
XML document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.portletsession.PortletSessionTestCase.xml is not a valid
XML document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.preferences.PreferencesTestCase.xml is not a valid XML
document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.renderresponse.RenderResponseTestCase.xml is not a valid
XML document. It is possibly corrupted.
-Original Message-
From: Julien Viet
Sent: Monday, February 20, 2006 4:41 PM
To: Rajesh Rajasekaran
Cc: QA; [EMAIL PROTECTED]; jboss-development@lists.sourceforge.net; QA; Julien
Viet
Subject: Re: jboss-portal-2.4-testsuite Build Completed With Testsuite
Errors
how can we do to improve that (i.e fix the wellformedness) ?
Rajesh Rajasekaran wrote:
The junit reports (xml) for the portlet tests are not well formed.
Hence the portlet test results are not accounted in the HTML reports
shown.
The common and format tests pass 100%.
Please refer the link below for the portlet test reports.
http://cruisecontrol.jboss.com/cc/artifacts/jboss-portal-2.4-testsuite/2
0060220170427/jboss-4.0.3SP1-logs/results/testfailures
Please let me know if you have the same problem.
Thanks
Rajesh
*From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
*Sent:* Monday, February 20, 2006 4:07 PM
*To:* [EMAIL PROTECTED]; jboss-development@lists.sourceforge.net; QA; Julien
Viet; QA
*Subject:* jboss-portal-2.4-testsuite Build Completed With Testsuite
Errors
*Importance:* High
View results here -
http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.4-testsuit
e?log=log20060220170427
*TESTS FAILED*
*Ant Error
Message:
*/services/cruisecontrol/work/scripts/build-jboss-portal.xml:67:
The following error occurred while executing this line:
/services/cruisecontrol/work/scripts/build-jboss-portal.xml:93: The
following error occurred while executing this line:
/services/cruisecontrol/work/scripts/build-jboss-portal.xml:199: The
following error occurred while executing this line:
/services/cruisecontrol/work/scripts/build-common-targets.xml:11:
Build
Successful - Tests completed with errors or failures.
*Date of build: *02/20/2006 17:04:27
*Time to build: *1 minute 58 seconds
[JBoss-dev] RE: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors
should we make the portlet test case extends it ?
Well, as Rajesh pointed out it is the junitreport task which blanks the
XML reports, so I was wrong on my point #2. Rajesh is trying to narrow
this down and will followup with what he finds.
-Original Message-
From: Julien Viet
Sent: Monday, February 20, 2006 5:53 PM
To: Ryan Campbell
Cc: Rajesh Rajasekaran; Julien Viet; QA; [EMAIL PROTECTED];
jboss-development@lists.sourceforge.net
Subject: Re: jboss-portal-2.4-testsuite Build Completed With Testsuite
Errors
yes they don't extend TestCase because we only use the
public static Test suite() { }
method as the class itself is not really a test but rather a suite
provider.
should we make the portlet test case extends it ?
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re: jboss-portal-2.4-testsuite Build Completed With Testsuite Errors
thanks,
Junit is so lame :-)
Ryan Campbell wrote:
should we make the portlet test case extends it ?
Well, as Rajesh pointed out it is the junitreport task which blanks the
XML reports, so I was wrong on my point #2. Rajesh is trying to narrow
this down and will followup with what he finds.
-Original Message-
From: Julien Viet
Sent: Monday, February 20, 2006 5:53 PM
To: Ryan Campbell
Cc: Rajesh Rajasekaran; Julien Viet; QA; [EMAIL PROTECTED];
jboss-development@lists.sourceforge.net
Subject: Re: jboss-portal-2.4-testsuite Build Completed With Testsuite
Errors
yes they don't extend TestCase because we only use the
public static Test suite() { }
method as the class itself is not really a test but rather a suite
provider.
should we make the portlet test case extends it ?
--
Julien Viet
JBoss Portal Project Lead
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
