[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14597539#comment-14597539
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8579:
--------------------------------------------

GitHub user gauravaradhye opened a pull request:

    https://github.com/apache/cloudstack/pull/511

    CLOUDSTACK-8579: Fix cleanup operation in few test cases

    Cleanup list should be declared before returning from setUpClass() so that 
tearDownClass() works properly.
    
    Currently the test cases are failing with "Class does not have cleanup 
attribute".
    
    Tested with passing LXC as hypervisor and test cases skipped successfully 
without giving any error.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gauravaradhye/cloudstack 8579

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/511.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #511
    
----
commit d7feb1a54027b73cba3e1ffc3d09d97b072335e2
Author: Gaurav Aradhye <[email protected]>
Date:   2015-06-23T11:54:05Z

    CLOUDSTACK-8579: Fix cleanup operation in few test cases

----


> Fix cleanup in few test cases
> -----------------------------
>
>                 Key: CLOUDSTACK-8579
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8579
>             Project: CloudStack
>          Issue Type: Test
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Automation
>    Affects Versions: 4.6.0
>            Reporter: Gaurav Aradhye
>            Assignee: Gaurav Aradhye
>              Labels: automation
>             Fix For: 4.6.0
>
>
> cleanup list should be declared before returning from setUpClass() so that 
> tearDownClass() works properly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to