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: > /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 > > > > 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.jav a > > > > - 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/PortletI nterfaceTestCase.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/Exc eptionsDuringRequestHandlingControllerPortlet.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/Por tletExceptionDuringRequestHandlingPortlet.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/Run timeExceptionDuringRequestHandlingPortlet.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/Una vailableExceptionDuringProcessActionPortlet.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/Una vailableExceptionDuringRenderPortlet.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/FileURLNavigationProvid er.java > > > > sort files when we list a sub dir to have the behavior independant of > the platform > > 1.1 > > > > added > > > > bdaw > > > > portlet/src/resources/test/test-portletinterface-war/WEB-INF/portlet.xml > > > > - JBPORTAL-638 - "portletinterface" test portlet deployment descriptors > > 1.1 > > > > added > > > > bdaw > > > > portlet/src/resources/test/test-portletinterface-war/WEB-INF/web.xml > > > > - JBPORTAL-638 - "portletinterface" test portlet deployment descriptors > > 1.49 > > > > modified > > > > bdaw > > > > portlet/build.xml > > > > - JBPORTAL-638 - added "portletinterface" package and SPEC:4 testcase- > JBPORTAL-671 - PLT.5.2.2.1 - 'Error Conditions on Initialization' test > cases (SPEC:5,6 and 8) > > 1.1 > > > > added > > > > bdaw > > > > portlet/src/main/org/jboss/portal/test/portlet/portletinterface/PortletI nterfaceTestCase.java > > > > - JBPORTAL-638 - added "portletinterface" package and SPEC:4 testcase- > JBPORTAL-671 - PLT.5.2.2.1 - 'Error Conditions on Initialization' test > cases (SPEC:5,6 and 8) > > 1.1 > > > > added > > > > bdaw > > > > portlet/src/main/org/jboss/portal/test/portlet/portletinterface/spec/Exc eptionsOnInitControllerPortlet.java > > > > - JBPORTAL-638 - added "portletinterface" package and SPEC:4 testcase- > JBPORTAL-671 - PLT.5.2.2.1 - 'Error Conditions on Initialization' test > cases (SPEC:5,6 and 8) > > 1.1 > > > > added > > > > bdaw > > > > portlet/src/main/org/jboss/portal/test/portlet/portletinterface/spec/Ini tializeBeforeHandlePortlet.java > > > > - JBPORTAL-638 - added "portletinterface" package and SPEC:4 testcase- > JBPORTAL-671 - PLT.5.2.2.1 - 'Error Conditions on Initialization' test > cases (SPEC:5,6 and 8) > > 1.1 > > > > added > > > > bdaw > > > > portlet/src/main/org/jboss/portal/test/portlet/portletinterface/spec/Por tletExceptionDuringInitPortlet.java > > > > - JBPORTAL-638 - added "portletinterface" package and SPEC:4 testcase- > JBPORTAL-671 - PLT.5.2.2.1 - 'Error Conditions on Initialization' test > cases (SPEC:5,6 and 8) > > 1.1 > > > > added > > > > bdaw > > > > portlet/src/main/org/jboss/portal/test/portlet/portletinterface/spec/Run timeExceptionDuringInitPortlet.java > > > > - JBPORTAL-638 - added "portletinterface" package and SPEC:4 testcase- > JBPORTAL-671 - PLT.5.2.2.1 - 'Error Conditions on Initialization' test > cases (SPEC:5,6 and 8) > > 1.1 > > > > added > > > > bdaw > > > > portlet/src/main/org/jboss/portal/test/portlet/portletinterface/spec/Una vailableExceptionDuringInitPortlet.java > > > > - JBPORTAL-638 - added "portletinterface" package and SPEC:4 testcase- > JBPORTAL-671 - PLT.5.2.2.1 - 'Error Conditions on Initialization' test > cases (SPEC:5,6 and 8) > > 1.11 > > > > modified > > > > julien > > > > wsrp/build.xml > > > > - rename servlet binding removing the trailing * for the wsdl- comment > code that produces class cast exception when the ws endpoints are > instantiated > > 1.4 > > > > modified > > > > julien > > > > wsrp/src/generated/org/jboss/portal/wsrp/core/WSRP_v1_ServiceDescription _PortType.java > > > > - rename servlet binding removing the trailing * for the wsdl- comment > code that produces class cast exception when the ws endpoints are > instantiated > > 1.6 > > > > modified > > > > julien > > > > wsrp/src/main/org/jboss/portal/wsrp/endpoints/ServiceDescriptionEndpoint .java > > > > - rename servlet binding removing the trailing * for the wsdl- comment > code that produces class cast exception when the ws endpoints are > instantiated > > 1.9 > > > > modified > > > > julien > > > > wsrp/src/main/org/jboss/portal/wsrp/proxy/EndPointProxy.java > > > > - rename servlet binding removing the trailing * for the wsdl- comment > code that produces class cast exception when the ws endpoints are > instantiated > > 1.2 > > > > modified > > > > julien > > > > wsrp/src/resources/jboss-wsrp-war/WEB-INF/web.xml > > > > - rename servlet binding removing the trailing * for the wsdl- comment > code that produces class cast exception when the ws endpoints are > instantiated > > > > > > > -- 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=lnk&kid3432&bid#0486&dat1642 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
