Hi, Yes, there wasn't. This is because of the changes of the website used for web-scrapping in WebResourceSampleTestCase. Do we have to fix this in the released branch?
Thanks On Mon, Jan 27, 2014 at 8:37 AM, Anjana Fernando <[email protected]> wrote: > Hi, > > Chanika, can you check on this. As I remember, we didn't have any > integration test failures when we were releasing, the tests mentioned here > for DSS seems to be tests that require a working Internet connection, maybe > that has something to do with the failures. > > Cheers, > Anjana. > > > On Sun, Jan 26, 2014 at 1:36 PM, Afkham Azeez <[email protected]> wrote: > >> DSS & AS folks, >> You need to urgently attend to this matter. As we know, build failures >> stop the world. This should be resolved by Monday. >> >> Azeez >> >> >> On Sun, Jan 26, 2014 at 1:19 PM, Krishantha Samaraweera < >> [email protected]> wrote: >> >>> Hi Isuruwan, >>> >>> Chunk 05 build failures are due to some backend/UI test failures. Seems >>> like teams have released the products with integration test failures. >>> Fixing those failure are not possible because code cannot be committed . >>> And even skipping failure cases though testNG xml will take lot of effort >>> because need to rewrite testNG xml and include all classes and exclude >>> failure classes (TestNg supports only for class exclusion). >>> >>> Best option available now is to use >>> testFailureIgnore<http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#testFailureIgnore>property. >>> You can set this property with maven build command and ignore >>> test failures to get the build passed. >>> >>> *DSS Backend failures - * >>> >>> build 23-Jan-201 23:45:42 Failed tests: >>> initialize(org.wso2.carbon.dss.samples.test.EventingSampleTestCase) >>> build 23-Jan-2014 23:45:42 >>> selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase): >>> expected:<true> but was:<false> >>> build 23-Jan-2014 23:45:42 >>> selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase): >>> expected:<true> but was:<false> >>> build 23-Jan-2014 23:45:42 >>> selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase): >>> expected:<true> but was:<false> >>> build 23-Jan-2014 23:45:42 >>> selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase): >>> expected:<true> but was:<false> >>> build 23-Jan-2014 23:45:42 >>> selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase): >>> expected:<true> but was:<false> >>> *build 23-Jan-2014 23:45:42 Tests run: 221, Failures: 6, Errors: 0, >>> Skipped: 4* >>> >>> *AS Backend Test failures - * >>> >>> Failed tests: >>> testUpdateStudent(org.wso2.carbon.integration.rest.test.poxsecurity.POXSecurityByUserTestCase): >>> Server returned HTTP response code: 500 for URL: >>> https://localhost:9443/services/StudentService/student/automationStudent >>> build 23-Jan-2014 22:14:05 >>> testGetResourceAfterDelete(org.wso2.carbon.integration.rest.test.poxsecurity.POXSecurityByInvalidUser): >>> User belongs to invalid group was able to get the resource expected [true] >>> but found [false] >>> build 23-Jan-2014 22:14:05 >>> testAddNewStudent(org.wso2.carbon.integration.rest.test.poxsecurity.POXSecurityByAdminTestCase): >>> Server returned HTTP response code: 500 for URL: >>> https://localhost:9443/services/StudentService/students >>> build 23-Jan-2014 22:14:05 >>> testEmailJaggery(jaggery.integration.tests.emailhostobject.EmailHostObjectTestCase): >>> Input stream failure expected object to not be null >>> build 23-Jan-2014 22:14:05 >>> *build 23-Jan-2014 22:14:05 Tests run: 216, Failures: 4, Errors: 0, >>> Skipped: 5* >>> >>> *AS UI test failures -* >>> >>> build 23-Jan-2014 22:20:43 Failed tests: >>> uploadSpringWebApplicationTest(org.wso2.carbon.integration.test.ui.webapp.spring.SpringWebApplicationDeploymentTestCase): >>> Web Application uploading failed expected:<true> but was:<false> >>> build 23-Jan-2014 22:20:43 >>> build 23-Jan-2014 22:20:43 Tests run: 15, Failures: 1, Errors: 0, >>> Skipped: 2 >>> >>> Thanks, >>> Krishantha. >>> >>> >>> On Sun, Jan 26, 2014 at 11:40 AM, Krishantha Samaraweera < >>> [email protected]> wrote: >>> >>>> Hi Isuruwan, >>>> >>>> The actual issue is with APIM 1.6 profile generation. >>>> >>>> I could see the following lines in log. Because of generated build is >>>> unstable, server start-up at integration tests failed. >>>> >>>> build 24-Jan-2014 03:02:03 [INFO] WSO2 API Manager - P2 Profile >>>> Generation .......... FAILURE [4:41.977s] >>>> build 24-Jan-2014 03:02:03 [INFO] WSO2 API Manager - P2 Profile >>>> Generation Parent ... SUCCESS [1.697s] >>>> build 24-Jan-2014 03:02:03 [INFO] WSO2 API Manager - BAM Toolbox >>>> .................... SUCCESS [2.548s] >>>> build 24-Jan-2014 03:02:03 [INFO] WSO2 API Manager - Distribution >>>> ................... SUCCESS [3:20.956s] >>>> build 24-Jan-2014 03:02:03 [INFO] WSO2 API Manager - Distribution >>>> Parent ............ SUCCESS [0.112s] >>>> build 24-Jan-2014 03:02:03 [INFO] WSO2 API Manager - Integration >>>> Test Module ........ FAILURE [7:41.465s] >>>> build 24-Jan-2014 03:02:03 [INFO] WSO2 API Manager - Integration >>>> UI Test Module ..... FAILURE [9:10.559s] >>>> build 24-Jan-2014 03:02:03 [INFO] WSO2 API Manager - Integration >>>> Tests .............. SUCCESS [0.840s] >>>> >>>> Thanks, >>>> >>>> Krishantha. >>>> >>>> >>>> >>>> On Fri, Jan 24, 2014 at 5:59 PM, Isuruwan Herath <[email protected]>wrote: >>>> >>>>> Hi Krishantha, >>>>> >>>>> I executed all chunks with the with the feature to run UI tests >>>>> remotely. Chunk02 was successfully built but there were failures in >>>>> chunk05 >>>>> and chunk06 [1] . Noted the following exception in APIM UI tests in >>>>> chunk06: >>>>> >>>>> error 24-Jan-2014 02:17:51 at >>>>> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) >>>>> error 24-Jan-2014 02:17:51 Caused by: java.lang.RuntimeException: >>>>> Port 9763 is not open >>>>> error 24-Jan-2014 02:17:51 at >>>>> org.wso2.carbon.automation.core.utils.ClientConnectionUtil.waitForPort(ClientConnectionUtil.java:111) >>>>> error 24-Jan-2014 02:17:51 at >>>>> org.wso2.carbon.automation.core.utils.serverutils.ServerUtils.startServerUsingCarbonHome(ServerUtils.java:133) >>>>> error 24-Jan-2014 02:17:51 at >>>>> org.wso2.carbon.automation.core.ServerGroupManager.startServer(ServerGroupManager.java:92) >>>>> error 24-Jan-2014 02:17:51 at >>>>> org.wso2.carbon.automation.core.ServerGroupManager.startServersForBuilder(ServerGroupManager.java:98) >>>>> >>>>> Could this be an infrastructure issue with the remote UI test server and >>>>> bamboo builder? >>>>> >>>>> [1] http://wso2.org/bamboo/browse/TEST001 >>>>> >>>>> >>>>> >>>>> >>>>> Regards! >>>>> >>>>> >>>>> >>>>> On Wed, Jan 22, 2014 at 12:04 PM, Isuruwan Herath >>>>> <[email protected]>wrote: >>>>> >>>>>> Yes, rebuilding the failures did not give the mentioned error again. >>>>>> As the UI tests have been worked around I'm running bamboo plans again >>>>>> from >>>>>> chunk02 and let's see if the p2-profile-gen fails again. Thanks for >>>>>> looking >>>>>> into this. >>>>>> >>>>>> Cheers! >>>>>> Isuruwan >>>>>> >>>>>> >>>>>> On Wed, Jan 22, 2014 at 11:51 AM, Lasantha Fernando < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 21 January 2014 12:55, Isuruwan Herath <[email protected]> wrote: >>>>>>> >>>>>>>> Hi Lasantha, >>>>>>>> >>>>>>>> Following is the error occurred in Bamboo log [1] : >>>>>>>> >>>>>>>> [ERROR] Failed to execute goal >>>>>>>> org.wso2.maven:carbon-p2-plugin:1.5.3:p2-profile-gen >>>>>>>> (p2-profile-generation-for-gateway-manager-profile) on project >>>>>>>> am-p2-profile: P2 publisher return code was 137 -> [Help 1] >>>>>>>> >>>>>>>> Bamboo plan is configured to build from chunk06 folder in branch. >>>>>>>> >>>>>>>> [1] http://wso2.org/bamboo/browse/TEST001-EPC6-1/log >>>>>>>> >>>>>>> >>>>>>> Hi Isuruwan, >>>>>>> >>>>>>> Asked for the logs since thought I might have made a mistake in >>>>>>> creating the tag for chunk-06. I did verify it in a clean repo build. >>>>>>> AFAIK, there were some changes done to the p2-repo after the tag was >>>>>>> created. But no changes were done to the product builds. Guess those >>>>>>> commits also need to go into the tag. >>>>>>> >>>>>>> Anyway, looks like the current build failure in chunk-06 is due to >>>>>>> UI integration tests. >>>>>>> >>>>>>> Thanks, >>>>>>> Lasantha >>>>>>> >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> Regards! >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Tue, Jan 21, 2014 at 11:28 AM, Lasantha Fernando < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Hi Isuruwan, >>>>>>>>> >>>>>>>>> Can you post the error you encountered in building chunk-06? Are >>>>>>>>> you building from the chunk-06 tag? >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Lasantha >>>>>>>>> >>>>>>>>> >>>>>>>>> On 21 January 2014 10:45, Afkham Azeez <[email protected]> wrote: >>>>>>>>> >>>>>>>>>> Krishantha, >>>>>>>>>> If the UI tests cannot be fixed by EOD today, let's disable them >>>>>>>>>> until we find a proper solution. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Tue, Jan 21, 2014 at 10:28 AM, Isuruwan Herath < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> Hi Azeez, >>>>>>>>>>> I created plans and executed all released chunks under Bamboo >>>>>>>>>>> plan TEST 4.2.0. Apart from the failure in 'WSO2 API Manager - >>>>>>>>>>> P2 Profile Generation' (noted yesterday) in chunk06 other failures >>>>>>>>>>> are >>>>>>>>>>> related to UI integration tests (in chunk02, chunk05, chunk06). >>>>>>>>>>> Krishantha >>>>>>>>>>> is working on the failures in UI tests to run them remotely (I see >>>>>>>>>>> chunk02 >>>>>>>>>>> is being built at the moment). If we get that through we can run >>>>>>>>>>> all plans >>>>>>>>>>> once more and confirm all released chunks are clean. >>>>>>>>>>> >>>>>>>>>>> Regards! >>>>>>>>>>> Isuruwan >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Tue, Jan 21, 2014 at 8:53 AM, Afkham Azeez <[email protected]>wrote: >>>>>>>>>>> >>>>>>>>>>>> Isuruwan, >>>>>>>>>>>> $subject please. >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> *Afkham Azeez* >>>>>>>>>>>> Director of Architecture; WSO2, Inc.; http://wso2.com >>>>>>>>>>>> Member; Apache Software Foundation; http://www.apache.org/ >>>>>>>>>>>> * <http://www.apache.org/>* >>>>>>>>>>>> *email: **[email protected]* <[email protected]> >>>>>>>>>>>> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: * >>>>>>>>>>>> *http://blog.afkham.org* <http://blog.afkham.org> >>>>>>>>>>>> *twitter: >>>>>>>>>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>>>>>>>>>>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez >>>>>>>>>>>> <http://lk.linkedin.com/in/afkhamazeez>* >>>>>>>>>>>> >>>>>>>>>>>> *Lean . Enterprise . Middleware* >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Isuruwan Herath >>>>>>>>>>> Technical Lead >>>>>>>>>>> >>>>>>>>>>> Contact: +94 776 273 296 >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> *Afkham Azeez* >>>>>>>>>> Director of Architecture; WSO2, Inc.; http://wso2.com >>>>>>>>>> Member; Apache Software Foundation; http://www.apache.org/ >>>>>>>>>> * <http://www.apache.org/>* >>>>>>>>>> *email: **[email protected]* <[email protected]> >>>>>>>>>> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: * >>>>>>>>>> *http://blog.afkham.org* <http://blog.afkham.org> >>>>>>>>>> *twitter: >>>>>>>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>>>>>>>>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez >>>>>>>>>> <http://lk.linkedin.com/in/afkhamazeez>* >>>>>>>>>> >>>>>>>>>> *Lean . Enterprise . Middleware* >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Dev mailing list >>>>>>>>>> [email protected] >>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> *Lasantha Fernando* >>>>>>>>> Software Engineer - Data Technologies Team >>>>>>>>> WSO2 Inc. http://wso2.com >>>>>>>>> >>>>>>>>> email: [email protected] >>>>>>>>> mobile: (+94) 71 5247551 >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Isuruwan Herath >>>>>>>> Technical Lead >>>>>>>> >>>>>>>> Contact: +94 776 273 296 >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> *Lasantha Fernando* >>>>>>> Software Engineer - Data Technologies Team >>>>>>> WSO2 Inc. http://wso2.com >>>>>>> >>>>>>> email: [email protected] >>>>>>> mobile: (+94) 71 5247551 >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Isuruwan Herath >>>>>> Technical Lead >>>>>> >>>>>> Contact: +94 776 273 296 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Isuruwan Herath >>>>> Technical Lead >>>>> >>>>> Contact: +94 776 273 296 >>>>> >>>> >>>> >>>> >>>> -- >>>> Krishantha Samaraweera >>>> Senior Technical Lead - Test Automation >>>> Mobile: +94 77 7759918 >>>> WSO2, Inc.; http://wso2.com/ >>>> lean . enterprise . middlewear. >>>> >>> >>> >>> >>> -- >>> Krishantha Samaraweera >>> Senior Technical Lead - Test Automation >>> Mobile: +94 77 7759918 >>> WSO2, Inc.; http://wso2.com/ >>> lean . enterprise . middlewear. >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Afkham Azeez* >> Director of Architecture; WSO2, Inc.; http://wso2.com >> Member; Apache Software Foundation; http://www.apache.org/ >> * <http://www.apache.org/>* >> *email: **[email protected]* <[email protected]> >> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: * >> *http://blog.afkham.org* <http://blog.afkham.org> >> *twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >> * linked-in: **http://lk.linkedin.com/in/afkhamazeez >> <http://lk.linkedin.com/in/afkhamazeez>* >> >> *Lean . Enterprise . Middleware* >> > > > > -- > *Anjana Fernando* > Technical Lead > WSO2 Inc. | http://wso2.com > lean . enterprise . middleware > -- Best Regards.. Chanika Geeganage Software Engineer WSO2, Inc.; http://wso2.com
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
