If we look at the current way we have implemented our integration tests we
can't actually be sure Whether this is happening or not.
If we look at products integration test modules it contain many test cases.

So what they do is

1) Start server

2) Run test

3) Shutdown sever.

So within a product integration test phase this happens multiple times.


In Bamboo after each product build we run a script to kill the running
carbon processors. But still if some thing went wrong inside a given
integration test module that will still may leave running carbon processors
which will cause other tests to fail within the module.

So i think we have two options to Fix this properly

1) Have an Abstract Test which all the test classes will extend from which
will cleanup the carbon servers in the pre test condition (Each test case
will do a super call in their local test pre condition ) or some thing like
that.

2) Using testng  and force to run a before test suite action which will
cleanup running carbon processors. IIRC in testng.xml we can have some
thing like that.



thanks,
Charith


On Thu, Apr 5, 2012 at 12:28 AM, Shammi Jayasinghe <[email protected]> wrote:

>
>
> On Thu, Apr 5, 2012 at 12:24 AM, Sameera Jayasoma <[email protected]>wrote:
>
>> Hi Shammi,
>>
>> Can this be a bind exception? There might be some java processes running
>> on the same port.
>>
>
> Hi Sameera,
>  I also suspected that . But could not find any process binded on port
> 9565.
>
> bamboo@db6237242:~/Bamboo-3.4/source-repository/build-dir/WSO2CARBON-CARBONCOREKERNELBUILD-JOB1$
> netstat -tulpn
> (Not all processes could be identified, non-owned process info
>  will not be shown, you would have to be root to see it all.)
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address           Foreign Address
> State       PID/Program name
> tcp        0      0 127.0.0.1:25            0.0.0.0:*
> LISTEN      -
> tcp        0      0 0.0.0.0:1984            0.0.0.0:*
> LISTEN      -
> tcp        0      0 0.0.0.0:5666            0.0.0.0:*
> LISTEN      -
> tcp        0      0 127.0.0.1:3306          0.0.0.0:*
> LISTEN      -
> tcp6       0      0 :::80                   :::*
> LISTEN      -
> tcp6       0      0 :::42642                :::*
> LISTEN      7507/java
> tcp6       0      0 :::8888                 :::*
> LISTEN      23729/java
> tcp6       0      0 ::1:25                  :::*
> LISTEN      -
> tcp6       0      0 :::1984                 :::*
> LISTEN      -
> tcp6       0      0 66.240.237.242:54663    :::*
> LISTEN      23729/java
> udp        0      0 0.0.0.0:44811           0.0.0.0:*
> -
> udp        0      0 0.0.0.0:45088           0.0.0.0:*
> -
> udp        0      0 0.0.0.0:161             0.0.0.0:*
> -
> udp        0      0 0.0.0.0:5353            0.0.0.0:*
> -
> udp6       0      0 :::54268
> :::*                                7507/java
> udp6       0      0 :::54441
> :::*                                -
> udp6       0      0 :::43720
> :::*                                7507/java
> udp6       0      0 :::5353
> :::*                                -
>
> Thanks
> Shammi
>
>>
>> Thanks,
>> Sameera.
>>
>>
>> On Thu, Apr 5, 2012 at 12:16 AM, Shammi Jayasinghe <[email protected]>wrote:
>>
>>> Hi Pradeep,
>>>
>>>    This kernel build is failed due to an integration test failure. There
>>> seems to be a problem in opening the port 9565. I have attached
>>> the sure-fire report of that. Could you please have a look.
>>>
>>> Thanks
>>> Shammi
>>>
>>> On Wed, Apr 4, 2012 at 11:31 PM, Bamboo <[email protected]> wrote:
>>>
>>>>      [image: Failed]  WSO2 
>>>> Carbon<http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON/>›
>>>> Kernel<http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD/>›
>>>> #156<http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD-156/>
>>>> failed
>>>>
>>>> This build was manually triggered by 
>>>> BambooBuilder<http://builder4.us1.wso2.org:8888/bamboo/browse/user/bamboo_builder>
>>>> .
>>>>
>>>> *1/2793* tests failed.
>>>>   Failing 
>>>> Jobs<http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD-156/>
>>>>     Job
>>>> Duration Tests    [image: Failed]  Default 
>>>> Job<http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD-JOB1-156/>
>>>>  (Default
>>>> Stage)  63 minutes  1 of 2793 failed  
>>>> Logs<http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD-JOB1-156/log>|
>>>> Artifacts<http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD-JOB1-156/artifact>
>>>>      Code
>>>> Changes<http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD-156/commit/>
>>>>   View
>>>> all 4 code 
>>>> changes<http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD-156/commit/>
>>>> kasung <http://builder4.us1.wso2.org:8888/bamboo/browse/author/kasung>
>>>> Code reformatting
>>>>
>>>>  124752    
>>>> kasung<http://builder4.us1.wso2.org:8888/bamboo/browse/author/kasung>
>>>> Fixing the issue in data-services. This fix was suggested by PrabathA.
>>>>
>>>>  124748    
>>>> dimuthul<http://builder4.us1.wso2.org:8888/bamboo/browse/author/dimuthul>
>>>> Fixing Carbon 
>>>> CARBON-10640<http://builder4.us1.wso2.org:8888/bamboo/project/jiraRedirect.action?jiraIssueKey=CARBON-10640&bambooProjectKey=WSO2CARBON>
>>>>
>>>>  124733   1 more 
>>>> changes…<http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD-156/commit>
>>>> Tests<http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD-156/test>
>>>>   View
>>>> full test 
>>>> details<http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD-156/test>
>>>>    1
>>>> New Test Failures   Test Job     ServerRestartTestCase
>>>> testServerRestart<http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD-JOB1-156/test/case/7637727>
>>>>   Default
>>>> Job<http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD-JOB1-156/test>
>>>>      View
>>>> Online<http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD-156>
>>>> | Add 
>>>> Comments<http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD-156?commentMode=true>
>>>>
>>>> This message was sent by Atlassian 
>>>> Bamboo<http://builder4.us1.wso2.org:8888/bamboo>
>>>> .
>>>>
>>>> If you wish to stop receiving these emails edit your user 
>>>> profile<http://builder4.us1.wso2.org:8888/bamboo/profile/userNotifications.action>or
>>>>  notify
>>>> your 
>>>> administrator<http://builder4.us1.wso2.org:8888/bamboo/viewAdministrators.action>
>>>> .
>>>>
>>>> _______________________________________________
>>>> Dev mailing list
>>>> [email protected]
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Best Regards,*
>>>
>>> Shammi Jayasinghe*
>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com,
>>> mobile: +94 71 4493085
>>>
>>>
>>>
>>
>>
>> --
>> Sameera Jayasoma
>> Technical Lead and Product Manager, WSO2 Carbon
>>
>> WSO2, Inc. (http://wso2.com)
>> email: [email protected]
>> blog: http://tech.jayasoma.org
>>
>> Lean . Enterprise . Middleware
>>
>
>
>
> --
> Best Regards,*
>
> Shammi Jayasinghe*
> Senior Software Engineer; WSO2, Inc.; http://wso2.com,
> mobile: +94 71 4493085
>
>
>
> _______________________________________________
> Dev mailing list
> [email protected]
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Charith Dhanushka Wickramarachchi
Software Engineer
WSO2 Inc
http://wso2.com/
http://wso2.org/

blog
http://charithwiki.blogspot.com/

twitter
http://twitter.com/charithwiki

Mobile : 0776706568
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to